Requirement traceability index

Copy Markdown

This index maps every normative section of parent specification #17 to one canonical owner and an eventual acceptance seam. Foundation means issue #18 establishes executable evidence; Future names the seam a later tracer bullet must complete. The machine-readable source is traceability.json.

Issue #25 covers Shared task API, Pi RPC lifecycle, Browser Client interaction, and both adapter rows through shared cancellation HTTP scenarios, the accepted-abort transcript, native tests, and packaged cross-adapter conformance. Issue #26 extends those rows with confirmed in-process session reset, retained-state rejection, recovery-only process replacement, and shared reset scenarios/transcripts. Issue #27 adds shared progress/failure transcripts, human-readable activity, bounded UTF-8 output with visible truncation, cancelled extension dialogs, safe protocol failure recovery, and packaged Rails/Phoenix semantic comparison. Issue #28 adds bounded task and abort deadlines, TERM-to-KILL owned-process cleanup, honest identity replacement, safe startup/exit handling, and equivalent native fake-Pi recovery/exhaustion scenarios. Issue #29 completes Rails checkout-scoped continuity with reload/fork-safe persistent clients, verified concurrent broker election, idle-only grace, and multi-process replacement/crash/cleanup coverage. Issue #30 adds rapid/stable polling, bounded network recovery, read-after-ambiguous-mutation reconciliation, single-host Turbo/LiveView lifecycle handling, conservative stale-mark removal, and current-browser cross-context/navigation acceptance. Issue #31 fixes the five-setting server-owned configuration contract, native development fail-closed activation, canonical direct spawn with inherited environment, precise startup validation, and safe unavailable-executable behavior across both adapters. Issue #32 completes exact normalized host/peer enforcement, native session CSRF with stable responses, safe logging, absent permissive CORS, persistent remote HTTP warnings, and trusted-network/proxy documentation across both adapters. Issue #33 makes Phoenix host integration discoverable or explicitly selectable, generated through one checksummed seam, dependency-free outside development, atomically updatable, collision-safe, annotation-aware, and reversibly uninstallable with packaged clean-host evidence. Issue #34 gives Rails the corresponding atomic checksummed generator, conventional or explicit ERB layout and mount selection, native development-only helper/configuration seams, mutation refusal, idempotent update, all-or-nothing inverse, and built-gem clean-host evidence. Issue #35 completes the taskbar-owned Corner composer with lifecycle semantics, native accessible controls, one live region, keyboard/focus paths, Shadow DOM isolation, narrow/200% reflow, reduced motion, and equivalent packaged-bundle DOM/current-browser evidence. Issue #36 proves the built Phoenix package and public installer in Recollect before removing its application-local runtime, API, assets, configuration, fake peer, and tests, with no provisional compatibility seam.

Issue #38 makes the complete Rails boundary matrix executable from built artifacts in clean generated applications, with a fast pull-request subset, supported Puma topology rows, synchronized MRI/Linux claims, and per-row JSON evidence. Issue #39 completes the corresponding Phoenix matrix from 1.7 through 1.8 at fixed Elixir floors and newest Elixir/OTP, using clean conventional apps, isolated built-Hex installation, controller-HEEx/LiveView evidence, and synchronized standard BEAM/Linux claims. Issue #40 completes artifact-isolated Chromium, Firefox, and WebKit example acceptance, taskbar-owned automated accessibility and lifecycle checks, and deterministic browser evidence. Issue #41 enforces protected-main source identity, lockstep versions, deterministic artifact bytes, strict package contents, clean artifact-installed acceptance, honest human-evidence prerequisites, checksums, and an immutable provenance handoff before publication. Issue #42 adds protected OIDC/credential publication, ordered registry reconciliation, public-byte and clean-install verification, durable resumable checkpoints, partial roll-forward, and tag/announcement gates exercised entirely with deterministic fakes in ordinary CI.

Normative sectionOwnerEventual acceptance seamStatus
Problem StatementRoot toolingClean-checkout root verification and packaged-adapter acceptanceFoundation
SolutionRoot toolingCoordinated Rails and Phoenix package artifact inspectionFoundation
User StoriesConformance ContractVersioned contract scenarios mapped to adapter and browser acceptanceFuture
Product and distributionRoot toolingSelf-contained gem and Hex package built at one root versionFoundation
Ownership boundariesRoot toolingMachine-readable dependency graph and negative coupling checksFoundation
Shared task APIConformance ContractIdentical black-box HTTP scenarios against both packaged adaptersAdapter slices
Pi RPC lifecycleConformance ContractTranscript replay through the deterministic fake Pi peerFoundation
Normalized browser task contextConformance ContractValid and invalid context fixtures parsed independently by both adaptersAdapter slices
Source-hint contractConformance ContractCross-adapter source classification fixtures plus native attribution testsAdapter slices
Bounds, truncation, and normalizationConformance ContractGolden bounded-context fixtures compared across native validatorsAdapter slices
Browser Client interactionBrowser ClientBrowser-owned DOM and current-browser cross-tab/navigation tests plus packaged example flowsAdapter slices
Security and configurationConformance ContractFramework-native access, CSRF, activation, and startup validation testsAdapter slices
Rails AdapterRails AdapterBuilt-gem clean-application integration and broker topology testsRails slice
Phoenix AdapterPhoenix AdapterBuilt-Hex clean-application integration and supervision testsPhoenix slice
Documentation and examplesRoot toolingDocumentation checks and examples installed only from built artifactsFuture
Versioning and coordinated releaseRoot toolingVersion drift, immutable artifact, checksum, and registry reconciliation gatesFoundation
Implementation sequence and change controlRoot toolingTraceability and clean vertical-slice gates before dependent workFoundation
Test philosophy and primary seamConformance ContractBehavior exercised at packaged adapter interfacesFoundation
Shared Conformance ContractConformance ContractSchema, fixture, scenario, transcript, and golden validationFoundation
Browser ClientBrowser ClientFast DOM plus artifact-isolated Chromium, Firefox, and WebKit lifecycle, keyboard, focus, cross-tab, Turbo/LiveView navigation, reflow, reduced-motion, and axe example flowsAdapter slices
AccessibilityBrowser ClientTaskbar-owned automated lifecycle/axe/keyboard/reflow evidence in both artifactsAdapter slices
Rails-native integrationRails AdapterRails installer, engine, CSRF, attribution, and broker process testsRails slice
Phoenix-native integrationPhoenix AdapterPhoenix installer, Plug, CSRF, attribution, and OTP isolation testsPhoenix slice
Compatibility matrixRoot toolingPublished matrix synchronized to clean generated application CI rowsAdapter slices
Examples, artifacts, documentation, and releaseRoot toolingPackaged example, artifact content, documentation, and release rehearsal gatesFuture
Out of ScopeConformance ContractContract and architecture review rejects accidental unsupported interfacesFoundation