Concept review round 6: accepted centered-layout and seed-selection amendment

Authority and reviewed baseline

Date: 2026-10-18. Reviewer: Codex. After inspecting the MVP, the project owner explicitly released its stakeholder requirements and requested completion of concept acceptance; see Sources and evidence. This closes the inspection gate from Concept review round 5: centered-layout and seed-picker MVP. Input Git revision is e7a561cbf1e8706c784980eff8d24e299d4a9885 plus the current uncommitted release-preparation and amendment work. No commit, tag or publication is implied.

The reviewed baseline combines the unchanged accepted concept from Concept review round 4: v0.2.0 implementation release with the complete amendment dependency neighborhood assessed in Concept review round 5: centered-layout and seed-picker MVP. The adjacent round-6-inventory.json records current content identities, individual modeled artifacts and the shared method identity. Earlier inventories remain snapshots. Current Needs outside this amendment retain their previous acceptance; historical/deferred decisions are not silently promoted.

Accepted scope

Owner-released stakeholder revisions: Initially collapse traced o... (STV_SHR_003), Start from the project when... (STV_SHR_047), Center parents over their v... (STV_SHR_052), Select a starting object in... (STV_SHR_053).
Reviewed software revisions: Initialize collapsed state (STV_SWR_003), Provide the artificial proj... (STV_SWR_051), Page stakeholder entry links (STV_SWR_052), Center parent boxes with co... (STV_SWR_056), Confirm local interactive s... (STV_SWR_057).
STV_ADR_006: Centered layout and interactive overview is accepted; STV_ADR_005: Optional seed sets and paged project entry is partially superseded for page size, initial project expansion and runtime seed mutability. Its unaffected decisions remain applicable, with reciprocal replacement links.
Affected Architecture View for Software, Internal interfaces and model contract, Implementation concept and handover, Implementation verification plan, Behavioral state machines and its adjacent Draw.io/SVG pair are accepted. Existing owners Exploration state engine (STV_SWE_STATE), Semantic rank layout (STV_SWE_LAYOUT) and Accessible view and viewport (STV_SWE_RENDER) within Browser exploration runtime (STV_SE_BROWSER) remain sufficient.

Review coverage and closure

Structural and semantic review follows the four stakeholder obligations through their software refinements and actual component responsibilities. SWR 003 implements the initial-collapse exception; SWR 051/052 combine project identity, five-entry pages and the existing capacity contract. SWR 056/057 directly refine SHR 052/053 because placement and local selection add no system interface, deployment service or host schema. Author and resolve embedded... (STV_SYS_001), Bound exploration of large ... (STV_SYS_008), Scope state to view roots (STV_SWR_038), Enforce visible occurrence ... (STV_SWR_043), Reject over-limit transitio... (STV_SWR_044) and Respect host-hidden Need ob... (STV_SWR_048) continue to constrain embedding, isolation, capacity, transactional failure and shared identity. No artificial system requirement is needed. Existing system architecture, build interfaces and technology choices retain their previously reviewed scope.

Completeness review covers empty entry/catalog cases, short/final pages, cross-page expansion memory, hidden objects, exact confirmation versus typing, independent views, replacement/overview reset, focus and layout rejection. Centering uses visible lower-level spans, ignores test/same-rank connections, retains shared children and prioritizes nonoverlap. Bounded semantic-rank passes avoid recursive layout of cycles. ELK ordering, collision resolution, test lanes and final obstacle-safe routes agree across ADR, interfaces, plan and runtime. No new dependency, runtime request, license or packaging decision is introduced.

Finding STV_REVIEW_014 (resolved): SWR 057 grouped stale completions with errors requiring a diagnostic. A superseded completion must not overwrite a newer request’s state or diagnostic. Clarified this internal requirement to discard stale results while invalid input/failed layout retains actionable diagnostics. This preserves the released stakeholder intent and matches the state-machine table and request-token contract. Closure: all three now agree.

ADR supersession and current maturity/verification/demo text were reconciled with the owner’s approval; round 5 and historical execution records are retained. Rendered architecture and state-machine SVGs and their embedded pages were inspected during the amendment and rechecked at acceptance. No unresolved concept blocker remains. Numeric performance budgets, occurrence mode, touch, additional platforms and the external-distribution license decision retain their recorded deferrals.

Checks and disposition

Acceptance checks: Sphinx full HTML build with warnings as errors; shared traceability validation; source/published diagram-link validation; strict requirement/executable coverage inventory; publication/diagram browser smoke. All acceptance checks passed: Sphinx returned zero warnings/errors; traceability validated 53 stakeholder, 10 system and 57 software requirements, two system and nine software elements, and five independent problem reports. All three diagram source/export pairs and published targets passed link checks. Strict coverage found 67 requirements and 68 executable cases, no unmapped active requirements and no unknown IDs. Firefox test_documentation_visuals passed (one case, 16 deselected); all three SVG exports and their embedded publication views were inspected. These are acceptance/publication checks, not a new full runtime qualification. Prior focused MVP results remain in Centered parents and interactive seed selection.

The listed requirement revisions and ADR 006 are accepted under explicit owner authority. Ordinary documents/diagrams are accepted at their inventory identities. No verification field is changed by concept acceptance. Full v0.2.0 release qualification, complete criterion review and a new consolidated execution record remain required before claiming a verified release. The failed 0.2.0-candidate-1 is retained unchanged.