Milestone 4.E.4 — Phase 4 Findings Register & Sign-offCopy Anchor Link

Status: planned/specification — sign-off consumes immutable P6-bootstrap, P6-slice-certification, E1, E2, and E3 evidence. Outcome: Phase 4 closes with zero open P0 findings and owned, time-bounded residual P1/P2 risk. Track: Track E — Release Readiness & Phase Exit Dependencies: all P/D evidence; E1; E2; E3; and disposition of the complete F4-001–F4-037 register, including the specific F4-035 surface-separation evidence. E4 is the final sign-off node. Estimated effort: 1 week Gate: G4 phase exit

Scope and deliverablesCopy Anchor Link

Publish a release certificate containing commit and image/artifact digests, schema/fixture versions, environment, topology, P6-bootstrap manifest, P6-slice-certification outputs, required checks, and E1–E3 bundle IDs. Disposition every F4 finding as implemented-with-evidence or residual-risk with evidence, owner, due/review date, mitigation, and rollback plan. Archive ADRs, runbooks, known limitations, evidence freshness, and residual-risk amendments.

F4 evidence rulesCopy Anchor Link

F4-001 requires P0 topology closure; F4-002/F4-006 require P1 mounted server-side identity, org, permission, and step-up evidence; F4-003/F4-021–027 require P2 read/publication evidence; F4-004/F4-008/F4-019/F4-024 require P3 lifecycle, deletion, and hostile-content evidence; F4-005 requires P4 bounded reads and estimate/actual separation; F4-011/F4-032 require P5 deployment/recovery evidence; F4-007/F4-033 require P6-slice-certification/E2 SSE and resilience evidence; F4-012/F4-028–030/F4-034 require P6-bootstrap/P6-slice-certification/E1 contract, runtime parsing, browser, accessibility, performance, and required-check artifacts; F4-035 requires D0 surface-separation evidence and explicit E4 disposition; F4-036/F4-037 require explicit runtime-profile, shared-limiter, and outage evidence in P0/P1.

Verification and non-functional gateCopy Anchor Link

An independent reviewer confirms every row links to an immutable artifact or signed residual acceptance. No open P0 is permitted. Every P1/P2 has an owner and date, or an explicit accepted exception with compensating controls and review date. Release certification does not auto-enable features; post-sign-off regression opens a new finding.

Findings addressedCopy Anchor Link

F4-001 through F4-037 (closure registry for Phase 4 exit).

Exit checklistCopy Anchor Link

• P6-bootstrap manifest and required-check inventory, plus applicable P6-slice-certification artifacts, are complete and match branch protection.
• E1 operator E2E, E2 resilience/recovery, and E3 promotion/rollback bundles are linked.
• Docs/static-shell smoke is separately labeled from operator E2E.
• F4-001–F4-037 are implemented-with-evidence or signed as residual-risk.
• Zero open P0 findings is independently verified.
• Known limitations, runbooks, and P1/P2 review dates are published.