Production traceability and evidence index
@{ Release.Traceability.Index20261004 [C:3] [TYPE ADR] [SEMANTICS production,requirements,traceability,evidence]
@BRIEF Navigate normative FR/SC/amendment inventories and their current evidence without treating index coverage as gate closure. @INVARIANT Source-SHA-bound receipts and signed release scope, not inventory presence, determine acceptance.
Scope and authority
This is a navigation and status manifest, not a closure certificate. The current acceptance authority is matrix 043–050, whose recorded base SHA-256 is 865e98e78b1c420a73ab5a6989d56c9f66f52b356e1934ccc7401327fb29dcb9. Apply the latest accepted spec amendments before older traceability prose. For shared runtime changes, use dated owner handoffs and inspect their receipts against the source SHA; implementation prose and a passing selector do not independently close a matrix gate.
Declared dashboard chain: 038–047 and 050 where the release owner declares them applicable. Draft 048/049 applicability is unassessed and requires release-owner disposition. The source worktree is active and contains concurrent changes; the base-matrix hash identifies the reviewed matrix version, not a frozen product source tree. Do not treat any row here as evidence tied to a release SHA.
Current matrix snapshot: 42 gates; 13 CLOSED, 16 PARTIAL, 13 OPEN; overall NO-GO. The five 2026-10-04 case/investigation rows are PARTIAL on bounded v6/v7 selections; operational, deployment and visual-capture conditions remain. This count is the current table reconciliation, not release approval.
The latest retained frontend suite/lint/build results are summarized in 3,585 passing tests across 247 files; the 715-file profile matches at the pre-suite and post-build endpoints. This is not backend, migration deployment identity, browser UI, human, or elapsed-time evidence.
The GO remainder plan groups the exact remaining gates by executable, deployed/runtime, elapsed and external-human proof, with next artifact and owner. Recent bounded diagnostics include backend v4, the red PG/API v3 run and support-module decision, combined backend/PostgreSQL v6, follow-up v7 including the selected molecular case-transition logger, the native UI v2–v7 failure history, and the two-pass native UI v8/v9 receipt. UI passes close only the named external product UI boundary.
The 72-hour soak runbook and seven-day shadow ledger are prepared but NOT STARTED pending root confirmation of an exact deployment bound to a release identity. The analyst study template is intentionally blank; no participant results are claimed.
Per-spec normative inventory pointers
The feature traceability files are the existing row-level inventory starting points. Their requirement rows often map FRs to contracts/tasks/test selectors, but usually do not include a current receipt and source SHA for every row. Completeness across every normative FR, SC, and amendment therefore remains OPEN.
| Spec | Requirement / traceability | Current receipt/status source | Scope note |
|---|---|---|---|
| 038 Scenario Model | spec, traceability, per-requirement crosswalk | matrix, G-SCENARIO-AUTHOR, G-BSL-DERIVED, G-E2E-EVALUATION |
Crosswalk expands each AGSCN-FR/SC and marks requirements lacking a source trace row. |
| 039 Scenario UI | spec, traceability, per-requirement crosswalk | G-EXTERNAL-MCP-ONLY-UI, G-BA-UX-READINESS |
Explicit human-acceptance gates; receipt links distinguish focused/current UI vectors from participant acceptance. |
| 040 Load Testing | spec, traceability | matrix, G-STORAGE-BUDGET, G-DLQ-SOAK |
Preserve sampled vs complete dataset claims. |
| 041 Dataset Lineage | spec, traceability | matrix | Existing FR→contract/verification rows; live fleet acceptance separate. |
| 042 Scenario Registry | spec, traceability | matrix | Traceability states intended mappings may not equal completed acceptance. |
| 043 Scenario Editor | spec, traceability, requirement-level map | G-043-EDITOR-AUTHORITY; matrix references T015b/c, T015d, T019, T021/T022; backend receipt; frontend receipt |
Focused backend proposal/save and frontend boundary/manual-render receipts exist. Neither proves full editor authority, stale/accessibility flows or release acceptance. |
| 047 investigation amendments | normative map; spec, traceability | New SCAN-FR-023..033 and SCAUTO-FR-025..030 rows link exact contracts, selectors and dated owner handoffs. |
Implementation/test claims are identified with limitations. Independent source-identified acceptance and elapsed operational evidence remain open. |
| 044 Scenario Execution | spec, traceability, per-requirement crosswalk | G-SUPERSET-QUERY-OWNERSHIP, G-BROWSER-*, G-E2E-EVALUATION, G-SECURITY-OPS |
Cancellation contract exists; operation-owned query effect remains unproven. |
| 045 Run Monitor | spec, traceability, UI evidence contract, per-requirement crosswalk | G-MONITOR, G-EVIDENCE-TIER, G-BA-UX-READINESS |
Receipt scope and tiering residuals are matrix-defined. |
| 046 Automation | spec, traceability, per-requirement crosswalk | G-SCHEDULER-CORE, G-NOTIFICATIONS, G-DLQ-SOAK, G-USER-SUBSCRIPTIONS |
Actual soak and subscription rollout evidence remain distinct. |
| 047 Analytics | spec, traceability, base FR/SC crosswalk, amendment map, expected-change window plan | G-INVESTIGATION-*, G-CASE-*, G-NOISE-SHADOW-ROLLOUT |
Runtime handoffs are implementation claims pending independent SHA-bound receipts; operational gates require elapsed evidence. |
| 048 RLS (Draft) | spec, traceability | No stand acceptance receipt recorded | Applicability and release disposition unassessed; no automatic include/exclude. |
| 049 IDM (Draft) | spec; no traceability file present | No stand acceptance receipt recorded | Applicability unassessed; IDM-FR-018 needs clarification; release-owner disposition required. |
| 050 MCP | spec, traceability, per-requirement crosswalk, early FR/SC map | G-MCP-*, G-MCP-PARITY, G-EXTERNAL-MCP-ONLY-UI, G-USER-SUBSCRIPTIONS |
FR-001..029 and SC-001..009 now have candidate source/oracle mappings with explicit missing-contract/current-receipt gaps; exhaustiveness review remains open. Frontend suite/build and native UI v8/v9 are separately scoped. |
| Visual capture authority | root-approved design decision | AgentRun owner, persistent server binding, native identity and effective RLS proof | No implementation/acceptance receipt; unsupported without truthful native identity and RLS. |
2026-10-04 amendment-to-oracle index
These rows make the newly added requirements discoverable. Latest receipt describes the current review state, not a gate-status promotion.
The end-to-end remaining work by owner and evidence class is tracked in the GO remainder plan; it keeps executable tests, actual deployed identity, elapsed operation and external human approval distinct.
| Requirement / matrix gate | Normative source | Contract / decision pointer | Oracle or selector required | Latest receipt / status |
|---|---|---|---|---|
Query ownership — G-SUPERSET-QUERY-OWNERSHIP |
044 T042/T045, SCEX-FR-020/027; matrix cancellation amendment | 044 production-chain cancellation contract and LiveExecutionBinding ownership contract |
Independent same-query operation-ID submit/cancel/reconcile vectors; unknown blocks retry/PASS; response bounds | Existing provider fault canary does not prove SQL Lab ownership; matrix OPEN. |
Case source comparison — G-CASE-SOURCE-COMPARISON |
044 / 047 / 037, 2026-10-04 amendment | Frozen source attempt + typed expected/actual + immutable baseline pin | Exact projection equality and authorized expected-image bytes or typed unavailable; hardcoded independent source fixture | PARTIAL: v7 whole-module receipt covers frozen expected/actual, decimal-zero fallback and sibling finding preservation on a matched 2,041-path profile. Exact source-attempt rendering and image-byte authorization/unavailability remain open. See v7 and matrix row. |
Scoped repair — G-CASE-SCOPED-REPAIR |
044 T056–T058 / 047 amendment | Explicit server repair binding and per-case verified resolution | Scoped pass closes addressed case while unrelated global failure remains; context/principal bypass denied | PARTIAL: v7 repeats scoped unrelated-failure, changed-context, and stale/foreign binding vectors. Native requester/RLS capability and deployed repair execution remain open. See v7 receipt and matrix row. |
Episode noise — G-CASE-EPISODE-NOISE |
036 / 038 / 047 amendment | Comparable episode fingerprint; dependent-check causality; expiring accepted exception | 100 repeated observations → one comparable episode and ≤1 case; independent roots remain separate; expiry vector | PARTIAL: v7 passed the bounded repeat/dependency/expiry and critical-escape modules against matched manifests; analytics/episodes.py SHA is c8fc945c767b408f21dfce05ab634b603dc3618b111e09ea319dc71158b898cb. Deployed migration identity, final semantic/index proof, full regression and seven-day shadow remain open. See v7 receipt and matrix row. |
Subscription access and delivery — G-USER-SUBSCRIPTIONS |
046 / 047 / 050 T053 amendment | Own-user subscription/access resolver; recipient/event idempotency; delivery policy | Authorized observer, revoked ACL, one event per recipient, digest/immediate, mute, future-only activation and shadow no-send vectors | PARTIAL: v7 repeats delivery, mute, revocation, dedup and PostgreSQL scheduler vectors. Native UX and actual seven-day shadow remain outstanding. See v7 receipt and matrix row. |
Case baseline review — G-CASE-BASELINE-REVIEW |
037 / 047 amendment | Separate accepted deviation and baseline publication state machine | Accept deviation without publish; immutable linked capture→draft→approval→publication history | PARTIAL: v7 passed the standalone expected-change writer, explicit intent, expiry/ineligibility, stale-case, and one scoped molecular transition log path. Trusted visual capture→candidate→approval→publication/pin lineage remains absent. See v7 receipt and visual-capture next slice. |
Seven-day shadow — G-NOISE-SHADOW-ROLLOUT |
046 / 047 amendment | Shadow measurement and pilot decision record | Actual 7 days, zero user messages, listed counters and triage/VLM pilot evidence | No elapsed operational receipt; OPEN. |
Editor authority — G-043-EDITOR-AUTHORITY |
043 T015b/c,d,T019,T021/T022; SCEDIT-FR-001/002/005/009/010/011 | WorkingDraft server ownership, digest, context authority and fresh authorization | Independent canonical graph round-trip; stale/unsafe zero-write; keyboard conflict flow | Existing implementation tests do not cover complete independent readiness map; OPEN. |
Product agent UI removal — G-EXTERNAL-MCP-ONLY-UI |
039 AGUI-FR-002; 043 SCEDIT-FR-006/T015/T023; 044 boundary; 050 client contract | Shared frontend boundary decision | Route/navigation/DOM/network negative checks plus ordinary manual editor/human review positive checks | CLOSED only for the recorded frontend profile/image and named boundary: full/targeted frontend tests plus stable native UI v8/v9 read-only network passes. Other external-client, security, accessibility, analyst and full-release gates remain distinct. See matrix row and native UI receipt. |
Normative traceability — G-FR-TRACEABILITY-COMPLETENESS |
Matrix 2026-10-04 scope amendment; all release-declared 038–050 FR/SC/amendments | Per-feature traceability maps and this index | One row per normative requirement with contract, source/N/A, independent test oracle and source-SHA receipt; signed 048/049 disposition | Existing bounded review confirms incomplete map (especially 043 and 049); this manifest is a starting index, not exhaustive; OPEN. |
Evidence and status discipline
- Keep matrix status unchanged until a verifier-reviewed receipt is retained and tied to its source SHA. Link command, selector, result, limitations, and source identity together.
- Runtime readiness, feature implementation handoffs, synthetic-fixture results, and passing focused tests are scoped facts. They do not establish external deployment identity, original business-oracle equivalence, elapsed soak duration, analyst participation, or release signoff.
- Human/elapsed gates require actual human or elapsed-time records. Never synthesize those records. Eight FI-0084 edit-dependent rows are N/A on the current stand, not product closure.
- Global gate inventory and exhaustive FR/SC mapping are different deliverables. This file does not claim complete coverage merely by listing the requirements sources.