Public Home page + per-spec "plans → achievements" step (flagged)

.specify/templates/tasks-template.md

@@ -152,6 +152,7 @@ Examples of foundational tasks (adjust based on your project):
 **Purpose**: Improvements that affect multiple user stories
 
 - [ ] TXXX [P] Documentation updates in docs/
+- [ ] TXXX Home-page currency (plans → achievements): if this spec moves a thesis or stage from planned to demonstrated, update `docs/assay-home.html` so the plan reads as an achievement (objectives/theses state + progress tracker), under banded honesty — nothing shown as done the repository does not contain. See comms plan §9 and the flagged candidate concept §6.12. Skip only if the spec demonstrates no new user-visible capability.
 - [ ] TXXX Code cleanup and refactoring
 - [ ] TXXX Performance optimization across all stories
 - [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/

docs/assay-comms-plan.md

@@ -1,6 +1,6 @@
 # ASSAY — Communications Plan
 
-Status: draft for review · v0.3 · 2026-07-11 (v0.2 adds §6: blog articles with working interactive embeds; v0.3 adds §12: the SME listening loop, and the schema namespace on the Documents page)
+Status: draft for review · v0.4 · 2026-07-12 (v0.2 adds §6: blog articles with working interactive embeds; v0.3 adds §12: the SME listening loop, and the schema namespace on the Documents page; v0.4 wires the per-spec home-page-currency step into §9 — flagged candidate, concept §6.12, pending ratification — and the `docs/assay-home.html` Home page it maintains)
 Authority: ASSAY-DEC-9 (banded honesty — re-derived here as *communications* honesty), ASSAY-DEC-2 (register discipline; the site surfaces the register, never replaces it), ASSAY-DEC-7 (theses as explorations; the site reports thesis *state*, not thesis *products* claimed as shipped).
 
 The vehicle is a **public GitHub Pages site** whose single job is to communicate ASSAY's goals and demonstrate its progress — honestly, always-current, and doctrinally literate — to the audiences who will judge it. The site is not a product page; it is the demonstrator's accountable public face, and it inherits ASSAY's signature discipline: **nothing is shown as done that is not, and nothing assessed is shown as fact.**
@@ -156,6 +156,7 @@ Illustrative, not binding — the embed is chosen per article by whoever closes
 ## 9. Cadence & ownership
 
 - **On every stage gate** (exit criteria met in the build plan): update `status.yml`, publish the stage's research note to the Roadmap index, add an updates-feed entry. Where the stage introduced a new component or a graphically-expressible algorithm, that entry is a full blog article carrying its working embed (§6) — choosing and shipping the embed is part of authoring the article, not a separate task. This ties site currency to the build's own gates — no separate reporting ritual.
+- **On every spec that demonstrates new capability** — the home-page-currency step: a single SPEC can turn a planned capability into a demonstrated one *within* a stage. When it does, revising the public Home page (`docs/assay-home.html`) so the plan reads as an achievement — the objectives/theses state and the progress tracker reflecting what the repository now contains — is part of that spec's definition of "done," under the same banded-honesty guardrail (nothing shown as done the repository does not contain). This extends the stage-gate cadence above to *spec* granularity so the site never lags the build by a whole stage. *(Flagged candidate, concept §6.12 — pending register ratification; wired here provisionally under the same delegated-authority pattern as the DEC-16 floor.)*
 - **On each research note written:** flip `research_published: true`; the note appears in the index.
 - **At the spine-complete gate:** swap the Demo page from wireframes to the live demonstrator; add a milestone entry.
 - **Milestones** continue to fire to `ntfy.sh/iancc2025` (concept §5); the updates feed is the durable written record of the same events.

docs/assay-concept.md

@@ -103,6 +103,7 @@ Target set (peers, batch-propagated):
 9. ~~**G6 — propagation honesty**…~~ — **ratified as ASSAY-DEC-25**: G6 is a standing seam invariant alongside G1–G5; oracle cases in vignette §9.
 10. ~~Whether `assay-findings.md` joins the canonical set…~~ — **ratified as ASSAY-DEC-26**: it joins the canonical set as the sole home of findings; a finding may be cited for what an exploration concluded, never as the origin of a decision.
 11. ~~SME evaluation checkpoints as standing gates…~~ — **ratified as ASSAY-DEC-27**: no thesis concludes without at least one checkpoint having seen it; reactions land in the findings ledger within a day.
+12. **Home-page currency (plans → achievements).** The comms plan ties public-site progress to *stage gates* (§9). But a single SPEC can turn a planned capability into a demonstrated one *within* a stage, and the public home page (`docs/assay-home.html`) should re-render that plan as an achievement when it does — not wait for the whole stage to close. **Candidate:** each build specification carries, as part of its definition of "done," a **home-page-currency step** — assess whether the slice moves a thesis or stage from planned to demonstrated and, if so, update the home page's objectives/progress accordingly, under the same banded-honesty guardrail the site already inherits (nothing shown as done that the repository does not contain; a stage cannot show "building" before its research note is published). This makes progress reporting part of building at *spec* granularity, mirroring the ownership rule the comms plan already states at stage granularity (§9). Wired provisionally into the spec-kit tasks template and comms plan §9 pending this batch's ratification — the same "build against the flagged candidate under delegated authority" pattern by which the DEC-16 confidence→band-width floor and the sparse-channel schema entered on landing. On ratification, batch-propagates to the delivery plan §1 ("How we deliver") and the build/comms cadence. *Flagged candidate — not yet ratified.*
 
 ## 7. Research starting points (ASSAY-DEC-11)