Candidate Evidence Navigation Guide

Candidate-only Status

This guide and its companion records are candidate-only evidence for workflow operators and reviewers. They are inspectable product artifacts, not published authority, not approval, and not a release pointer. Candidate-only status does not establish promotion, publication, scheduling, rollback, activation, or a write to a live directory. Keep the package parked until the responsible review and platform-owned decisions are supplied separately.

Find the Evidence

Start with sources/authority.json. Read its revision, its three logical source IDs, and its employee_may_modify value, then match those IDs to the public-safe records in registries/sources.json. Next compare this page's metadata with its entry in registries/pages.json, and open journeys/user_journeys_manifest.json to follow the three acceptance traces. The candidate record at releases/candidate-evidence-navigation.json ties those product artifacts together. The preserved Agent-Orch validator record is platform-owned captured evidence: its exact command, exit status, pass status, and hash must be read from the supplied record rather than replaced by an author assertion or a validator rerun.

Use the source registry for provenance, the page registry for identity, the journey manifest for reader procedure, and the release record for status and boundary facts. A declared command is an allowlist entry, not proof that the command ran. If a fact is absent from its owning record, mark it unresolved; do not fill the gap with plausible prose or private governance material.

Review Handoff

The operator hands off the Markdown page, synchronized page entry, journey manifest, source references, and candidate release record as one inspectable packet. The author records product-side evidence and unresolved gaps. An independent reviewer checks the headings, metadata, source references, journey traces, and candidate-only status on a separate review path. Neither the author's summary nor a product conclusion self-certifies platform execution, human approval, promotion, publication, scheduling, rollback, or a release pointer. Preserve the exact supplied validator evidence alongside any later reader or review record, including failures or unavailable observations.

The handoff is complete for navigation when a reviewer can locate each source, map each AC-1 through AC-3 check to a natural-language journey, and distinguish declared commands from observed results. Completion of this guide does not request or perform a transition; it only makes the candidate evidence easier to inspect and route to the owner of the next decision.

Source and Status Boundaries

The sealed source boundary is the authority for the guide's semantic provenance. sources/authority.json lists source.naming-decision, source.documentation-boundary, and source.platform-delivery-contract; the matching registry records are the available public-safe source metadata. The guide uses no registered claim reference, so it does not add a semantic product claim. The governing repository remains the owner of controls that are outside these product records.

The candidate record describes what was authored and what remains open. The declared inputs establish no prior-version identity or rollback target for this new guide; those facts are recorded as null and unresolved rather than guessed. No publication pointer is created or changed. Candidate evidence can support a bounded product review, but it cannot become published authority, a live directory result, or proof that a platform-owned gate or transition occurred.

Acceptance Checks

• AC-1 — Source and identity trace: The reader opens sources/authority.json, verifies its recorded revision, three source IDs, and employee_may_modify value, matches the IDs to registries/sources.json, and confirms that this page's header and registry entry have the same id, title, visibility, audiences, reading modes, empty claim references, and source references.
• AC-2 — Evidence navigation and review handoff: The reader locates the page, registry, journey manifest, candidate release record, and supplied validator evidence; follows one non-exploratory journey for each acceptance check; and distinguishes a declared allowlisted command from the preserved validator's exact command, exit status, pass status, and evidence hash without claiming a rerun.
• AC-3 — Candidate-only and release facts: The reader confirms that the release record is candidate-only, unpublished, unpromoted, and has no release-pointer or live-directory action; reports prior-version and rollback-target facts as null and unresolved when no authoritative record establishes them; and does not infer approval, publication authority, or a transition from this packet.