Active Needs-Lee Authority and Evidence Map

Purpose

This Internal Knowledge map gives Lee and auto-orch operators one bounded view of the two active decisions in the human-question record. Its outcome is practical: a reader can choose the next smallest human decision from preserved evidence without treating product readiness, a reader result, or a candidate record as authority. This page is an advice-lane artifact, not an approval queue. It cannot approve a commissioning lineage, authorize a pilot, promote or publish a release, schedule work, change a pointer, roll anything back, or write a live directory.

Active Needs-Lee Map

The Open section names exactly Human approval and Controlled pilot authorization. The supplied reader manifest requires both journeys to trace to this page's AC-1 through AC-4 checks. The source record lists AC-DS-5 and AC-DS-7 in the operator-independent-boundary journey. Those labels are recorded as affected contract labels below; this page does not reinterpret them or claim that either label grants human or platform authority.

Human approval

Missing human authority: Lee's explicit human-gate decision is missing: after reviewing the fresh commissioning evidence, Lee must decide whether the readiness contract supports the affected separately governed transition. A product-side pass or review recommendation cannot stand in for that decision.
Affected acceptance-contract labels: AC-DS-5 and AC-DS-7, both listed by the source record for the independent-boundary journey. The affected acceptance contract is the readiness-to-transition contract. The active question concerns the boundary between independent product evidence, candidate-only state, and the human decision; it does not assert either source-record label as satisfied.
Preserved evidence: The human-question record identifies fresh run c56754d00fd8 and candidate ds002-c56754d00fd8 as the evidence awaiting the gate. The result review records a product-side pass with no findings, and context and WHERE_AM_I describe the retained candidate-only boundary. No failure artifact for this approval decision is available in the declared product inputs; none is invented here. These links are the available repository-relative decision evidence.
Smallest actionable Lee decision: Review that fresh lineage and record only whether the readiness contract supports the affected next transition, with any resulting authority action left to its separately governed owner. Lee need not decide promotion, publication, scheduling, rollback, pointer mutation, or a live-directory write as part of this product map.
Reversible default: Keep candidate ds002-c56754d00fd8 parked and unchanged as candidate-only evidence. Leave any publication pointer absent and do not promote, publish, schedule, roll back, or write a live directory while the human-gate decision is open.

Controlled pilot authorization

Missing human authority: Lee's explicit authorization for a controlled pilot is missing. The human-question record makes this a later decision, conditional on acceptance of a fresh commissioning lineage; it is not implied by approval review or by product readiness.
Affected acceptance-contract labels: AC-DS-5 and AC-DS-7, the two labels that the source record traces to the independent-boundary journey. The affected acceptance contract is the post-acceptance controlled-pilot transition contract. The labels identify the relevant evidence and transition boundary in the source record, not an authorization to run a pilot. The pilot decision remains Lee's authority.
Preserved evidence: The sprint plan, context snapshot, result review, and milestone record preserve the commissioning lineage, product-side readiness conclusion, and candidate-only status with no publication pointer. No failure artifact for this pilot authorization is available in the declared product inputs; the available decision evidence is linked here instead of being replaced with an invented failure or approval.
Smallest actionable Lee decision: Only after the fresh commissioning lineage has been accepted, decide whether to authorize or decline the narrow controlled pilot. This decision must remain separate from any later promotion, publication, scheduling, rollback, pointer change, or live- directory action, each of which needs its own authority boundary.
Reversible default: No controlled pilot is authorized. Keep the candidate parked and unchanged, preserve its evidence, and leave promotion, publication, scheduling, rollback, pointer mutation, and live-directory writes untouched until Lee records the applicable decision.

Decision Queue

The queue is ordered by dependency, not by product confidence. First, Lee may review c56754d00fd8 and ds002-c56754d00fd8 and decide whether the readiness contract supports the affected human-gate transition. Second, and only after a fresh commissioning lineage is accepted, Lee may decide whether a controlled pilot is authorized. Auto-orch can prepare and preserve evidence for either review, but it cannot collapse the two decisions, infer consent from silence, or turn a product conclusion into approval. Until a decision is recorded, the smallest safe action is no transition: retain candidate-only state and do not promote, publish, schedule, roll back, create or change a pointer, or write a live directory.

Evidence and Authority Boundary

The sealed authority record says the employee may not modify the authority baseline, and the source registry contains the three public-safe sources used by this page. The repository evidence supports product conclusions about the fresh run, readiness review, lineage, and candidate-only status. The preserved validator evidence supplied for this step remains separate platform-owned gate evidence; it is not replaced by this page's prose or by a product command claim. No failure artifact for either active decision is present in the declared product inputs, so this map links the available decision evidence and records that absence explicitly.

Candidate-only means that evidence is retained behind the local publication boundary. It is not human approval, controlled-pilot authorization, promotion, publication, rollback readiness, scheduling authority, pointer creation, or a live-directory result. The governing repository and platform owners retain authority for those transitions and for route, identity, validator, terminal, and approval attestations. This page therefore recommends a reversible parked state until Lee decides; it does not perform or imply any external transition.

Acceptance Checks

AC-1 — Coverage: Every active needs-Lee item in the Open section of questions-for-the-human.md, namely Human approval and Controlled pilot authorization, has one map entry with its own evidence and decision fields.
AC-2 — Authority and contract: Each map entry names the missing human authority and affected contract—readiness-to-transition for Human approval or post-acceptance pilot transition for Controlled pilot authorization—and records the supported AC-DS-5 and/or AC-DS-7 labels without treating them as Lee's authority.
AC-3 — Evidence: Each map entry links preserved repository-relative decision evidence or explicitly records that no failure artifact is available in the declared product inputs; neither entry invents a failed run, approval, platform attestation, or transition result.
AC-4 — Decision and default: Each map entry gives Lee the smallest actionable decision and states a reversible default that keeps the candidate parked and unchanged without promotion, publication, scheduling, rollback, pointer mutation, or live-directory writing.