Reader-Journey Repair Decision Brief

Purpose

This brief gives auto-orch maintainers and sprint decision-makers a bounded, public-safe decision record for the Internal Knowledge reader journey. The sealed authority revision is 2026-08-08, and the current defect inventory concludes no_defect_established; therefore no speculative repository repair is authorized. The brief separates product evidence from unresolved reader, environment, and platform facts, while keeping governance, routing, validator authority, activation, approval, publication, and live-directory controls outside this product-owned decision.

Defect Triage

The current triage result is no defect established. The dependency order is authority boundary, deterministic reader-contract shape and trace coverage, independent reader evidence, then environment or platform-owned facts. No deterministic contract failure is established. No reader-evidence failure is established, although next-run reader evidence remains unknown. No environment failure is established because no owning environment record is supplied. A missing, stale, conflicting, or unsupported fact stays unresolved; it is not a defect, a pass, or permission to infer a platform result. The three authority-listed logical sources are public-safe, and private governance material remains outside this conclusion.

Minimal Repair Paths

The smallest safe path now is reversible no-repair: leave product sources and governed controls unchanged until a later governed result supplies concrete validation feedback. If that result proves a product defect, repair only the earliest failed deterministic prerequisite—such as malformed structure, an unresolved reference, or missing acceptance trace—and retain the failed observation beside the later result. If deterministic checks pass but reader evidence is absent or contradictory, repair the bounded evidence procedure and preserve the discrepancy. If an environment or platform fact is missing, make no product repair and route the gap to its owning authority. Regenerate the projection from source after any permitted repair; never treat generated output as semantic source.

Lee Decisions

This brief asks Lee for no immediate repository mutation. The smallest human decisions that remain open are approval of a later readiness recommendation and authorization of a controlled pilot. Until Lee records an applicable decision, the reversible default is to keep the no-repair conclusion and any later candidate evidence parked and unchanged. Product readiness cannot substitute for approval, pilot authorization, route or identity attestation, validator authority, promotion, publication, scheduling, rollback, a pointer change, or a live-directory write. Any such transition must use its separately governed authority boundary.

Acceptance Checks

The maintainer should be able to verify the sealed authority revision and its three public-safe sources; distinguish deterministic, reader-evidence, and environment categories; and identify that repair_target is currently null. The next governed run should execute every non-exploratory journey once by manifest ID with an exact allowlisted command, recording steps, exit status, observed result, source references, and traces_to. Failed output and later results remain side by side. The product conclusion must remain separate from platform-owned attestations, and no acceptance check may imply Lee's approval or authorize promotion, publication, scheduling, rollback, a pointer, or a live-directory action.