Specify Ollama inference safeguards and split baseline obligations
Specify exact PPL artifact file in source config contract
Specify source-derived configuration and precise implementation traceability
REQ-107, TEST-109: lane guest access channel; cite B2 (PR #213) New REQ-107 (reach a lane guest only through its run's key-bound channel) and TEST-109, linked from the SRS, RTM, planned test cases and SYS-REQ-027. REQ-091, REQ-093 and REQ-106 cite the workload placement code. Status stays Planned: offline tests pass, no live proof yet. REQ-104 and TEST-106 remain reserved for #181. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
REQ-103: cite the lane channel's runner-unit check (PR #212) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
REQ-106: cite the lane guest supervisor (PR #205) CodeRef adds scripts/lane/supervisor.py; Status stays Planned because the host side of the lane executor is not implemented. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
REQ-106, REQ-090: cite the lane output disk (PR #203) CodeRefs add scripts/lane/output_disk.py (format and guest launcher) and scripts/lane/outputs.py (host reader), merged as develop 86f3b3a. Status stays Planned until the executor exists. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
REQ-106, REQ-090: cite the lane-workload@2 code merged in VITechnologies/projectbuddy#201 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add REQ-106/TEST-108: lane build phase runs with network link off Specify the lane network split chosen as N2 on VITechnologies/projectbuddy#182: fetch steps run with the link on and no secrets; build steps run with secrets and the link off until power-off. Outputs return on a per-run disk read after poweroff (completion channel C1), because any guest process can write a VirtualBox guest property. Update REQ-090 (per-phase argument vectors and timeouts; CodeRef now cites scripts/lane/declaration.py), REQ-092 (per-phase evidence), REQ-093 (build-phase-only secrets), SYS-REQ-027 allocation, and SRS/RTM/test lists. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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 lifecycle requirements REQ-101 to REQ-103 (#166, #165) Adds three planned requirements under SYS-REQ-027, approved by the operator on 2026-11-09: - REQ-101 / TEST-103: each lane run uses a disposable instance of a base image whose digest matches its receipt (#166 Draft A). - REQ-102 / TEST-104: lane teardown is bound to the verified VM UUID and an allow-listed state, and reports removal only after observing absence (#166 Draft B). - REQ-103 / TEST-105: a lane guest has no GitHub Actions runner configured or registered, checked at packaging and clone time (#165 Draft C). IDs follow approval order. Updates the SRS, RTM, planned test-case hubs, and SYS-REQ-027 traceability. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tighten REQ-091 and TEST-093 with Stage 1 results (#164, #168) T1: allow a package manager's own version probe (for example npm --version) while forbidding any install, update, or download, in REQ-091's Fit Criterion and TEST-093's required observation. T2: record in REQ-091's rationale that Stage 1 rebuilt the published VSIX byte for byte with Node 22.15.0, 22.23.4, and 24.19.0, so only the probe can reveal toolchain drift for that workload. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Record the approval gate implementation for SYS-REQ-028 and REQ-094 to REQ-100 The gate merged in VITechnologies/projectbuddy#180 (Phase 1 of #179). CodeRef and TestArtifact now name the modules and offline fixture tests; status stays Planned until the Phase 3 live proof. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add human-approved automation request requirements (#177) SYS-REQ-028, REQ-094 to REQ-100, and planned tests TEST-096 to TEST-102 specify the protected-environment approval gate. Adds glossary terms and the ADR-0007 index entry (proposed in #178). 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>
Add .gitignore for per-user Obsidian state Keep the shared vault settings tracked (.obsidian/app.json for wiki-form links, .obsidian/core-plugins.json for graph and backlinks) and allow .obsidian/graph.json for shared graph color groups. Ignore every other .obsidian file, Obsidian's .trash/ (whose pages the assembler skips and would not flag as duplicates), and OS metadata. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Home, RTM: point to the scan's assembled table view Signed-in GitHub users can review the rebuilt Requirements Traceability Matrix, with rows linked back to these pages, in each standards scan run summary (VITechnologies/projectbuddy#174). The RTM hub no longer claims to render the table itself. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Home: note that the standards scan enforces the link rules The scan now runs Assemble-WikiSpec.py with --strict --max-page-bytes 16384 (VITechnologies/projectbuddy#172), so tell wiki editors that breaking a link convention or the page cap fails the scan. 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>
Add governed system requirements specification Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Specify Docker-bracketed release conveyor Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add REQ-039: release gate requires VM-creation + runner-registration proof Per ADR-0006 (revised after 3-model consensus review). Planned until #110 (Windows register-runner live-proof) completes and the gate's actual release.yml implementation lands.
Promote REQ-038 to Verified (live): Ubuntu register-runner real workflow_dispatch proof Real workflow_dispatch proof against a genuine, freshly-built disposable VM (register-runner-proof-ubuntu-20261107, upstream run 42403330593) -- the registered runner independently confirmed online via gh api with exactly the expected labels, not merely the phase's own exit code. Three real bugs found and fixed during this live-dispatch process: (1) missing SSH_ASKPASS setup (every ssh/scp call failed with Permission denied), (2) gh api --jq doesn't support jq's own --arg flag, (3) a re-registration ordering bug (config.sh remove requires the systemd service to be stopped/uninstalled first). Each merged as its own PR (#107, #108, #109). Disposable test runner deregistered and the temporary RUNNER_REGISTRATION_PAT secret removed immediately after.
Add REQ-038: Ubuntu register-runner phase parity with Windows Implementation merged via VITechnologies/projectbuddy#106 (issue #105). Marked 'implementation complete; live verification pending' until a real workflow_dispatch produces a runner independently confirmed online via gh api (dispatch in progress: a fresh disposable VM build, upstream run 42400820191, is running specifically for this purpose). - SRS REQ-038 added - RTM row added - Architecture Packet Component View row added (install-actions-runner.sh, complete-runner-registration.sh)
Promote REQ-037 to Active: Decode-LbaCapture.py implemented and verified - scripts/Decode-LbaCapture.py implemented per #102, 23 synthetic-fixture pytest tests (99% line coverage), real verification run against the genuine run-1794072448721 capture (reproduces the 31.724 MB/s peak-write finding at frame 432, reports zero false anomalies on this healthy capture per ADR-0005's Addendum correction) - Architecture Packet: Container View row for 'Agent diagnostics' no longer 'planned'; added matching Component View row - RTM REQ-037 row updated to Verified (live)
Correct REQ-037: dhashHex/screen null is structurally expected, not an anomaly Matches ADR-0005's own Addendum, written after inspecting the real labview-benchmark-actor source (local clone at the matching v1.4.14 version): the live 'Capture LabVIEW Launch' command never computes a perceptual hash or emits screen dimensions, so null dhashHex/screen is normal for every real capture it produces, not a settle/completeness signal. Corrected anomaly flags: capture-status.json state of failed/capturing (not stopped), dualPacket.outcome != authoritative, and inconsistent (not uniform) dhashHex population across one capture.
Add ADR-0005: agentic decoding of labview-benchmark-actor capture output - REQ-037 (Planned): dedicated read-only decoding tool for labview-benchmark-actor capture output, agent/operator diagnostic use only, schema-pinned to labview-benchmark-actor/launch-capture@1 - RTM row for REQ-037, tracked via #102 - Architecture Packet: ADR-0005 index entry + planned Container View row for 'Agent diagnostics' Grounded in this session's real capture analysis (run-1794072448721): found the MCP viewer tools show fixed demo data regardless of new captures, no upstream 'latest capture' pointer exists, resources.disk is a flat array (richer per-disk/per-frame data lives in the top-level frames[] array instead), and all 631 frames had a null dhashHex.
Correct REQ-018/REQ-032: no separate LabVIEW activation exists on Ubuntu/Linux Real workflow_dispatch proof (#62, run 42394542555) found this engine's Ubuntu-LabVIEW appliance has no separate human-interactive LabVIEW activation step at all -- NI's Linux LabVIEW distribution's authenticated package-repository access is itself the licensing gate. VIPM activation (automated via vipm activate --direct-vipm-io) is the only activation the complete-activation phase performs or needs. REQ-018's and REQ-032's prior verification relied solely on complete-activation.sh's own usage text claiming a prior manual LabVIEW activation precondition -- an unverified assumption carried over from the Windows family, never actually true for Linux, now corrected with real receipt evidence (perpetual, valid VIPM activation; a passing LabVIEW known-answer probe) rather than code review alone. Refs VITechnologies/projectbuddy#62