Concept review - round 3: starting nodes
Assessed Needs and semantic paths
Stakeholder scope:
Embed a traceability view (STV_SHR_001), Select the starting object (STV_SHR_002), Initially collapse traced o... (STV_SHR_003), Collapse opened traces (STV_SHR_007), Use a replaceable input dat... (STV_SHR_014), Preserve objects reached th... (STV_SHR_025), Require a valid starting ID (STV_SHR_026), Operate the view using the ... (STV_SHR_034), Explore a bounded view of a... (STV_SHR_043), Explain expansions blocked ... (STV_SHR_044), Reuse the host project's mo... (STV_SHR_045), Start from the project when... (STV_SHR_047), Select multiple starting ob... (STV_SHR_048).
System refinements:
Author and resolve embedded... (STV_SYS_001), Integrate the host data model (STV_SYS_002), Preserve semantic layout (STV_SYS_005), Bound exploration of large ... (STV_SYS_008).
Software refinements:
Register the RST entry point (STV_SWR_001), Initialize collapsed state (STV_SWR_003), Collapse relationship groups (STV_SWR_007), Normalize replacement mappings (STV_SWR_014), Compute seed-rooted visibility (STV_SWR_025), Report invalid invocation s... (STV_SWR_026), Enforce visible occurrence ... (STV_SWR_043), Provide the artificial proj... (STV_SWR_051), Page stakeholder entry links (STV_SWR_052).
Changed software responsibilities:
Extension lifecycle and dir... (STV_SWE_DIRECTIVE), Host model normalization (STV_SWE_MODEL), Graph adapter and indexes (STV_SWE_GRAPH), Exploration state engine (STV_SWE_STATE), Semantic rank layout (STV_SWE_LAYOUT), Accessible view and viewport (STV_SWE_RENDER), Hover, persistent details a... (STV_SWE_INSPECT).
Containment and unchanged collaborating boundaries:
Sphinx build integration (STV_SE_BUILD), Browser exploration runtime (STV_SE_BROWSER), Static bundle emission (STV_SWE_BUNDLE), Rendered detail extraction (STV_SWE_DETAIL_BUILD).
SYS 001 refines SHR 047/048 through optional/list invocation, source-located validation and project entry metadata within BUILD. SWR 001/026 own directive parsing/validation in DIRECTIVE; SWR 051 owns project metadata and synthetic entry behavior in GRAPH/STATE/RENDER, covering its actual system parent’s build allocation through GRAPH. SWR 014 refines model replacement under SYS 002 and MODEL, rather than hard-coding stakeholder type names. Existing SWR 003/007/025 channel software-local initialization/collapse obligations directly from SHR 003/007/025 to STATE; multiple roots do not require synthetic system requirements. SWR 043 extends SYS 008 capacity validation across DIRECTIVE and STATE. SWR 052 mixes software-local SHR 047 paging with the SYS 008 capacity constraint and is allocated to STATE/RENDER within the browser boundary. Each named parent/child, allocation and containment was read for meaning.
SHR 047 is covered by SYS 001 and SWR 051/052; SHR 048 by SYS 001 and SWR 001/003/025/026. Existing hidden-data, identity, semantic level, keyboard, offline and capacity constraints remain applicable. The synthetic root is not a Need, so Need-only ID/status/detail/link rules are not fabricated for it. Paging applies solely to virtual root-entry links; it does not weaken ordinary authored relationship expansion or create a new canonical relation type.
Findings and correction evidence
STV_REVIEW_010 - Project entry overflow
Category: capacity/scope. Owner: project owner. State: resolved. Evidence: one root plus more than 199 stakeholder entries cannot fit the accepted 200-node cap. Rejecting the root group would prevent project-wide entry navigation. The owner chose paging over rejection. Correction: clarify SHR 047, add SWR 052 and define 50-entry pages with page-local exploration and atomic cap/layout commit. Closure: all stakeholder IDs remain accessible across pages; the root counts toward the cap and normal trace groups remain atomic. The 0/1/50/51/199/200/201 fixtures are specified for implementation verification.
STV_REVIEW_011 - Single-root contracts and historical decision conflicts
Category: cross-artifact consistency/identity. Owner: delegated reviewer. State: resolved. Evidence: required single-ID syntax, one-root reachability and omitted-ID failure remained in interfaces/implementation and the clarification register; arbitrary synthetic IDs could collide with host Needs or accidentally receive original-object/detail/status semantics. Correction: optional positional list, deduplication, explicit-seed validation, tagged identity, project name and stakeholder-role contract, separate root band, project-page commands and real-Need-only inspection. Updated component responsibilities and verification fixtures. Closure: re-read the complete parse-to-render path, error behavior, page restoration and trace identities. ADR 005 partially supersedes ADR 003, with reciprocal links; the older decision body and prior acceptance are retained. Other boundary, bundle and dependency decisions remain unchanged.
Reviewed artifacts and outcome
Accepted revised SYS 001 and SWR 001/003/007/014/025/026/043/051, new SWR 052, and changed DIRECTIVE/MODEL/GRAPH/STATE/LAYOUT/RENDER/INSPECT responsibilities. Unchanged Need acceptance is retained. All 48 stakeholder, 10 system and 52 software requirements plus two system/nine software elements are accepted. ADR 005 is accepted under the recorded delegation; ADR 003 is partially superseded, preserving its unaffected design and historical acceptance.
The affected author, model, graph/state, rendering, capacity and verification contracts were substantively reviewed in Internal interfaces and model contract, Implementation concept and handover, Architecture View for Software, Software elements, Implementation verification plan and STV_ADR_005: Optional seed sets and paged project entry. The existing diagram components and all connections still match the design: initialization metadata follows existing MODEL/GRAPH/BUNDLE paths and commands stay within STATE/LAYOUT/RENDER/INSPECT. No diagram geometry or source link changed; prior visual evidence applies to identical bytes. The current SVGs were visually inspected again; no routing defect was found.
Checks and limitations
Installed Docutils argument parsing was exercised for omitted, single, multiple and repeated whitespace-separated arguments: four feasibility cases passed. This tests the chosen host parser facility, not an implemented STV directive. No dependency/version selection changed. Sphinx warnings-as-errors, shared graph/evidence validation with CSV output, published diagram links and source whitespace checks passed after the final status changes.
Runtime implementation and browser/state/geometry/packaging verification remain pending; all verification_state values remain not_assessed. The tests in the verification plan are planned checks. Project licensing, measured performance budgets, later occurrence mode and broader platforms retain their explicit deferrals. No concept blocker remains in this amendment’s reviewed scope.
Content identities
The following identify the accepted/retained artifact snapshot for this round. The record itself is excluded from self-referential hashing. Files omitted from the focused inventory retain earlier review evidence; central maturity and amendment documents record workflow history rather than product behavior.
Artifact |
SHA-256 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|