This is the development record, published as it was written. It is amended by revision, including where the work went wrong. Nothing here has been rewritten for the web.
Record header
created_at: 2026-09-24T06:21:06+00:00
format: perspicuity-work/1
id: ae-2026-09-24-bounded-report-claims
record_status: open
revision: 2
skill_version: 0.8.1
updated: 2026-09-24
updated_at: 2026-09-24T06:21:06+00:00
work_status: active
Make report claims match the observed results
Current position
Mode: Run. Parent: RECORD.md, revision 7. Principal and decider: David. Work owner: Avery. Ask: apply the reviewed website copy and release the necessary report corrections. Objectives: clear business explanations, accurate results and useful next actions. Decision: inherited from David's September 24 instruction to go live with the reviewed copy. Reconsider if: a correction requires changing fetching, storage or publication policy. Work scope: public copy, report counts, browser status and existing starter-file access. Done when: CI passes and the released pages, status flow and new reports match their claims. Ship to: David through the website and the commissioning task. Work: copy and report corrections pass all 156 tests and required CI. Outcome: live delivery pending; reader benefit unmeasured. Needs from you: nothing. Next: Avery / stage and verify the production release / this run.
Frame and Decide
The preceding copy audit found that unknown core results counted as passes, draft files were described as exact fixes, and the browser refreshed a report address before a report existed. The inspected deployment serves finished reports statically and forwards API paths to the application.
Decided by: Avery under COPY-LIVE-TOOLS. Keep the existing routes and report storage. Serve browser progress at the existing status endpoint through content negotiation, then redirect to the static report when complete. Expose existing starter files with relative links and clear draft warnings. This is smaller than changing the proxy or adding a browser script. Reconsider if: verification shows that the current routes cannot support this flow safely.
Act
Grant COPY-LIVE-TOOLS. For: Avery. Granted by: the commissioning task under David's September 24 release instruction. Serves: the objectives above. Intent: deliver the reviewed copy with truthful report behaviour. Includes: bounded source and copy changes, meaningful tests, commits, backup, deployment and live verification on the existing eligibility service. Excludes: proxy configuration changes, other hosts, publication of private reports, fetching-policy changes, external messages and further delegation. Tolerances: none set. Escalate if: scope or policy changes. Return to: this record and the commissioning task. Accepted by: the commissioning task. Done when and Ship to: stated above.
Pickup plan: reproduce counting and status defects with offline tests, apply copy and bounded fixes, run CI, stage an immutable release, preserve the previous release and service units, switch the eligibility services, and verify public delivery.
Review
Registered checks: count only actual passes; distinguish queued, running, failed and complete browser states; escape status details; keep JSON API behaviour; link only existing starter paths; retain the claim boundary; run all required CI; verify production homepage, rubric, corpus, form and new self-check report. Historical reports remain dated snapshots.
Changes
Revision 1 registers the release grant and checks before source edits. No new product, data or publication policy is selected.
Revision 2 records the completed implementation before release. The failing tests reproduced an unreadable-robots report claiming eight passes when seven checks passed, and browser progress returning JSON instead of a usable waiting page. Counting now uses actual statuses. Browser progress stays on the status endpoint until the report exists. Failed jobs show a recovery page without internal diagnostics. Existing starter files have relative download links and draft warnings.
The homepage, metadata, machine summary, rubric explanations and corpus introduction now use bounded claims. Fetching and publication policy are unchanged. All 156 tests pass. Required CI also passes the standard-library guard, byte compilation, record and actor checks, rubric freshness, site build, corpus consistency and script guard. An existing corpus test expected the retired “day one” phrase; its assertion now checks the explicit date. The source diff passes whitespace checks.
How this record connects
It builds on or points to: RECORD.
It is referenced by: Make small suppliers eligible to AI agents.