Starting-node requirement amendment
Owner request and requirement amendment 2026-10-18: The project owner requested that a view with no seed ID start at an artificial project-named node linked to stakeholder requirements, and that a list of seed IDs be supported instead of only one. The owner explicitly asked to update requirements first. This record amends the existing concept baseline; it is not a new concept review or approval of the revised requirement wording. The previous missing-seed failure obligation is replaced by project-root mode. Unknown and host-hidden explicitly supplied IDs remain errors. Single-seed behavior remains supported. Collapsed initialization, model replacement, visibility exclusions and the 200-visible-node limit are retained. The project entry node is artificial and is not another stakeholder/architecture Need. The project owner explicitly reviewed and accepted the stakeholder amendment on 2026-10-18 in this conversation: “i have reviewd the new stakeholder req. and accept them. please update the status accrodingyl”. Acceptance covers Initially collapse traced o... (STV_SHR_003), Preserve objects reached th... (STV_SHR_025), Require a valid starting ID (STV_SHR_026), Start from the project when... (STV_SHR_047) and Select multiple starting ob... (STV_SHR_048). Their status is accepted. That stakeholder decision did not accept downstream concept changes. The subsequent owner-authorized concept-creation and delegated review are now complete; see Concept review - round 3: starting nodes for the accepted revisions. Previous acceptance and content identities remain historical in Concept review - round 1 and Concept review - round 2. Verification remains not_assessed. Affected requirement objects requirements-stakeholder.rst: Initially collapse traced o... (STV_SHR_003), Preserve objects reached th... (STV_SHR_025), Require a valid starting ID (STV_SHR_026), Start from the project when... (STV_SHR_047), Select multiple starting ob... (STV_SHR_048). requirements-system.rst: Author and resolve embedded... (STV_SYS_001). requirements-software.rst: Register the RST entry point (STV_SWR_001), Initialize collapsed state (STV_SWR_003), Collapse relationship groups (STV_SWR_007), Compute seed-rooted visibility (STV_SWR_025), Report invalid invocation s... (STV_SWR_026), Provide the artificial proj... (STV_SWR_051), Normalize replacement mappings (STV_SWR_014), Enforce visible occurrence ... (STV_SWR_043), Page stakeholder entry links (STV_SWR_052). Project-root pagination decision 2026-10-18: Asked whether projects with more than 199 stakeholder requirements should page root links or reject oversized expansion. The owner explicitly selected “Page the project-root links (Recommended)”. This supplies the paging scope clarification in Start from the project when... (STV_SHR_047); ordinary authored trace groups keep their all-or-nothing capacity rule. Fixed page size 50 and independent page exploration are internal design choices in STV_ADR_005: Optional seed sets and paged project entry. Downstream concept refinement 2026-10-18: After the assistant proposed concept-creation followed by concept-review, the owner instructed “thats right. go for it!”. This authorizes the concept workflow and delegated acceptance of substantively reviewed clean concept artifacts. It does not authorize runtime verification claims or a Git commit. Concept review - round 3: starting nodes records review scope and evidence. Reconciled optional/list syntax, project-name source, model stakeholder roles, synthetic identity/presentation, multi-root visibility, root pages and capacity validation across requirements, interfaces, architecture and plans. Added Page stakeholder entry links (STV_SWR_052) and accepted STV_ADR_005: Optional seed sets and paged project entry, partially superseding STV_ADR_003: Transactional exploration and semantic rank layout. Product implementation remains pending. |