# S00 Contract Ledger Template
Status: Template Purpose: classify backend readiness for each UI screen in v2 rewire
Classification values
Use exactly one status value per row:
EXISTS_COMPAT: endpoint exists and contract already matches target behavior.EXISTS_ADAPT: endpoint exists but requires request/response/schema/semantic adaptation.MISSING_NEW: no suitable endpoint exists; new contract required.
Required columns
| Domain | Screen/Page | Canonical source refs | Current route/page | Current endpoint candidate(s) | Status | Owner module | Auth scope impact | Schema delta summary | Decision/risk notes | Action ticket |
|---|---|---|---|---|---|---|---|---|---|---|
<Dashboard/Release Control/etc> | <screen> | <source-of-truth section + authority-matrix row + pack section> | <current path> | <service + path> | <EXISTS_COMPAT/EXISTS_ADAPT/MISSING_NEW> | <src module> | <none/new/changed> | <1-2 lines> | <risk + mitigation> | <ticket id> |
Validation checklist
- [ ] Every active-authority screen from
authority-matrix.mdhas a row. - [ ] No row has empty
Status. - [ ] Every
MISSING_NEWrow includes a concrete proposed endpoint in notes. - [ ] Every
EXISTS_ADAPTrow identifies schema or semantic delta. - [ ] Every row lists owner module and auth scope impact.
Owner module reference set
Use these module names consistently:
ReleaseOrchestratorPolicyEvidenceLockerAttestorSignerIntegrationsScannerOrchestratorSchedulerAuthorityWeb
Optional extension columns
Add only if needed:
Data freshness contractDeterminism/offline constraintsTelemetry eventsDeprecation/redirect dependency