docs: specify Epic 250 native qualification gates
docs: specify active capture consumer bridge
docs: record P1 synthetic UI integration
docs: record integrated live-run policy P0 evidence
docs: specify deterministic live-run authorization policy
Add REQ-105 and TEST-107: refuse to package an appliance that carries an Actions runner (#195)
The appliance packager scans the running source VM for an Actions
runner unit or configuration, powers it off itself, and records the
scan in a projectbuddy/ubuntu-vagrant-box@2 receipt
(VITechnologies/projectbuddy#198). Allocate REQ-105 to SYS-REQ-008 and
note the scan in the Component View.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Name the frozen v1 clone profile in REQ-001 and the Component View (#192)
VITechnologies/projectbuddy#194 kept the previous appliance clone profile as
vm/ubuntu-labview/clone-profile.v1.json, which `@1` clone receipts verify
against. It carries the same consumer package identity as
clone-profile.json, so REQ-001 exception (3) and Component View row 18 now
name it alongside clone-profile.json.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Record the lane implementation for REQ-101 to REQ-103 (#185, #167)
Fill in Verification, TestArtifact, CodeRef, and Status for REQ-101,
REQ-102, and REQ-103 from the merged lane work (VITechnologies/projectbuddy#189,
#190, #191). Status becomes "Planned; offline fixture tests pass, no
live proof yet"; live observation still waits for the lane executor.
Apply the operator-approved REQ-103 Fit Criterion (readiness-time scan,
.runner or .credentials marks a runner) and TEST-105 stimulus from
VITechnologies/projectbuddy#167, and align TEST-105's required
observation with the new stimulus.
REQ-001 exception (3) now names package-vagrant-box.py and
clone-profile.json as the files that set the consumer's package
identity; "scripts" becomes "files" since the profile is JSON. The
Component View row is updated to match.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add lane workload requirements and disclose REQ-001's third exception
Stage 0 of VITechnologies/projectbuddy#164 (operator-approved A1-A4,
allocation option (a), three glossary entries):
- REQ-090 to REQ-093 (workload declaration, toolchain contract and probe,
lane evidence record, secret scoping), all Planned.
- TEST-092 to TEST-095 in the planned specification and system contract
test cases.
- SYS-REQ-027 "Consumer-declared lane workloads", allocated to
REQ-090 to REQ-093.
- Glossary: Lane workload, Toolchain contract, Evidence record.
VITechnologies/projectbuddy#167 item 8, option (a):
- REQ-001 lists all three disclosed exceptions, adding the Ubuntu
appliance scripts that enforce one consumer's package identity.
- Component View discloses them on the appliance lifecycle row.
- REQ-001's Verification records a classified re-sweep at develop
5881465; it found violations the #68 sweep missed, so REQ-001 is now
Not met and the residuals are tracked in
VITechnologies/projectbuddy#176.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Split governed specification hubs into linked pages
Restructure the four governed hubs (System Requirements Specification,
Software Requirements Specification, Requirements Traceability Matrix,
Architecture Packet) into index-only hubs plus one page per SYS-REQ,
REQ, and TEST ID and one page per architecture section, so the wiki
reads as a linked graph in Obsidian and on GitHub.
scripts/Assemble-WikiSpec.py (VITechnologies/projectbuddy#171) rebuilds
all four hubs byte-identically from these pages for the standards scan.
Home gains a Structure section describing the layout and link rules.
Refs VITechnologies/projectbuddy#169
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>