A package is not yet market success
KF03 · Descriptive case report · 2026-10-05
A checked 24-file package contained articles and ownership files. Which claims follow from that evidence, and which require new observations?
What others can put into practice.
- Define an evidence ladder for each release: package → actual delivery → core function → external visit → attributable revenue.
- Retain failed test assumptions too. An incorrect test can reject a valid narrow route.
- Treat packaged keys as preparation until actual verification is recorded. Do not claim success metrics from internal QA alone.
Question
Where does a local release package’s evidence end?
Method
A retrospective document analysis of the r4 package report for an owned guide portal and four related tools. The analysis ends at the recorded local handoff on 5 October. Later changes are outside this case.
For each claim level, the question was: which check actually ran? Package validation, runtime, browser delivery, ownership verification, indexing and market outcomes were read separately.
Results
The report records a final 24-file package: four factual new articles, an exact IndexNow key and retained existing assets. Unchanged core files and corrected footer links were documented for the four tool packages.
Guards rejected unbound or conflicting manifests, input-bearing origins and incorrect key hosts. An initial QA assertion expected /api/* and rejected the valid narrower /api/upload-test route; it was corrected in a focused continuation.
Both runtime_calls and browser_checks were 0; publication was false. IndexNow ownership files were packaged, but delivery, ownership verification and submission were not established by this report.
Independent visits, ad revenue and per-tool revenue attribution remained explicitly unknown. Existing provider bindings alone do not establish use or payment.
Limits
One local r4 handoff, not a statement about the portal’s present state. Reused earlier core checks are separate from new browser checks. Demand and profitability were not tested.
Sources
Redacted extracts with source fingerprints. Originals remain locally retained.
guides-package Tool guides · r4 package review
r4-package-evidence.json
SHA-256: 13941ecdfe9c5e3541d4f21431fd1b6fb1a3341ca732641a7790e62d43b487f7
{
"observed_at": "2026-10-05",
"passed": true,
"focused_review": {
"initial_runs": 1,
"initial_failure": "QA expected /api/*; valid narrower /api/upload-test rejected by assertion",
"targeted_continuations": 1,
"continuation_scope": "corrected route assertion, remaining guards, Root-requested search/IndexNow artifact integration; no unchanged app suites"
},
"checks": [
"Final 24-file r4: four factual articles plus exact IndexNow key; prior nine articles/ad loader/search/legal/style/policies byte-identical",
"Four final addons: fixed footer links/no private input channel, Birthday exact owner tags, five separate public keys; other 55 core assets unchanged",
"Unbound/mismatched Worker manifest, same/input-bearing origin, wrong key host and wrong search host refused",
"All original sources/input ZIPs/rollback metadata and actual guide ad/search bindings unchanged"
],
"file_count": 24,
"runtime_calls": 0,
"browser_checks": 0,
"publication": false,
"indexnow": "ownership files packaged only; delivery/ownership/submission not established",
"limits": [
"Changed article and addon navigation delivery/browser checks remain Root-owned.",
"Unchanged accepted mobile/template/consent/core evidence reused.",
"Root Upload r3 real HTTP200/confirmed synthetic body and native ETA evidence retained; Worker CPU telemetry unknown.",
"No new independent traffic, indexing, ad creative QA or revenue; no per-tool income allocation."
],
"independent_visits_or_earnings_verified": false,
"per_tool_revenue_allocation": null
}Download JSONEditor: Dirk Ohlmann · Version 1.0 · Prepared on 7 October 2026
Conflict of interest: The operator reports on owned projects. Selection is retrospective; no external peer review or sponsor-directed findings.