Parent: #1400 · Labels: enhancement, area/docs (auto, docs/**) · Size: S–M · Depends on: GP4 (the JSON-contract (index.json + series/*.json) shape + URL form must exist to document); the consensus-model explainer and the TG⇄GP cross-link can draft earlier.

Goal. Make the consensus model, the interim's relationship to the live TestGrid stack, and the recipe-quality cross-link a single documented source of truth: publish the public docs page (consensus-model explainer + how to read the dashboard), add a light cross-link in 010 describing GP and TG as siblings, and wire the RQ1 Evidence-link cross-reference.

Scope.

• Public docs page (docs/user/): what the interim corroboration dashboard is; how to read it (CSP-first navigation → catalog overview → consensus grid → source dot-strip by class → per-source drilldown); the consensus-model explainer (CONFIRMED/SINGLE/CONTESTED/FAILING/UNTESTED; distinct-signer counting; what CONTESTED means and why it is surfaced; source classes); and — stated honestly, tied to ADR-007 — what community/partner corroboration proves (provenance: who signed and what they assert) and does not prove (cluster-verified correctness), including the sybil/allowlist posture and the author-declared-tab caveat (intent/platform are cluster-unobservable, match.go:70-71).
• TG ⇄ GP sibling cross-link (NOT a deferral re-scope). Add a short paragraph to docs/design/010-aicr-testgrid.md stating that GP (Epic: GP — Interim corroboration dashboard on GitHub Pages #1400) is the interim static GitHub Pages surface and TG (Epic: TG — Deploy & operate the AICR TestGrid instance #1263) is the live stack, and that both share the same bucket, the same verified source-keyed evidence, and the same recipe→coordinate mapping (TG6) — GP's GCS layout + JSON contract are forward-compatible inputs to TG's workers/API/UI, not a throwaway. Do not mark any TG child deferred or pull-triggered — TG proceeds in parallel. Do not contradict the locked CSP-first taxonomy or the single shared mapping function. Flag the one concrete overlap for the two work streams to deconflict directly (not in the doc): GP3's bucket + write-only publish SA vs TG1's — share one bucket or stand up two on purpose; this issue only records that the decision is owned outside the doc.
• Epic: Recipe health tracking (ADR-009 V1) — enumeration, structural soundness, public matrix #1224 / RQ1 cross-link. Document that the offline structural matrix (docs/user/recipe-health.md, Epic: Recipe health tracking (ADR-009 V1) — enumeration, structural soundness, public matrix #1224/ADR-009, published 2026-06-11) is the structural sibling and this dashboard is the live corroboration sibling, sharing the metadata.name/criteria join key. State that the recipe-quality epic's RQ1 (RQ1 — recipe-health ⇄ TestGrid Evidence deep-link #1283) Evidence deep-link resolves to this GH Pages dashboard coordinate (a stable Pages URL per recipe). 012's coordinate-based URL scheme is host-agnostic by design (k8s is kept out-of-path precisely so the link is host-stable), so a Pages URL is a clean instantiation of that scheme, not an override. The contract stays link-only, never duplicate the matrix and advisory, never a gate. If GP4's index.json lands before TG4a's presence endpoint, note it as an available interim coordinate-presence source for RQ2 — a sequencing option, not a forced re-point of 012.
• Honor doc conventions: auto-anchors (no TOCs), promote bold labels sparingly, anchor-link hygiene (lychee runs in fern-docs-ci.yaml on docs/** PRs). Register the new page in the Fern nav (fern/docs.yml + versioned navs).

Out of scope. The full #1263 re-scope — marking TG3/TG4a/TG4b/TG7 + the TG1 host cluster as deferred/pull-triggered — is dropped: TG is being built in parallel, and build-both-vs-defer is a separate strategic decision, not a docs edit. Forcing the RQ2 presence-source re-point in 012 (RQ2 keeps its existing TG4a dependency; GP4's index.json is offered only as an interim option). Editing recipe-health.md itself (RQ1 owns that). Implementing RQ2's link-integrity bot or the generator/ingest (GP4/GP2). Authoring the mapping function (TG6 owns it).

Key files. New docs/user/ dashboard page (register in fern/docs.yml + fern/versions/*.yml); docs/design/010-aicr-testgrid.md (the short TG⇄GP sibling cross-link only — no deferral edits); cross-reference docs/user/recipe-health.md (#1224, published); ADR-007 trust-model anchor; doc-CI reference .github/workflows/fern-docs-ci.yaml; the JSON-contract shape from GP4 (index.json + series/*.json).

Tests. Docs build clean under fern-docs-ci (lychee anchor-link check passes); the consensus-model explainer's terminology matches GP4's index.json state names (a small fixture/golden so docs and code cannot drift).

Acceptance. The public dashboard docs page is live and Fern-registered, explaining the consensus model and honestly stating what community/partner corroboration proves; docs/design/010-aicr-testgrid.md carries a short TG⇄GP sibling cross-link (shared bucket/evidence/mapping; GP interim, TG live) without marking any TG child deferred and without contradicting the locked taxonomy/mapping; the #1224/RQ1 cross-link is documented as link-only + advisory and resolves to the GH Pages coordinate URL; make qualify and fern-docs-ci pass.

Child of #1400 · staged from docs/design/013-interim-evidence-dashboard.md (GP6).