Skip to content

History / Software Requirements Specification

Revisions

  • Specify grant-bound Remmina console and mirror

    @svelderrainruiz svelderrainruiz committed Nov 12, 2026
  • docs: add native trial resource requirements

    @svelderrainruiz svelderrainruiz committed Nov 12, 2026
  • docs: specify Epic 250 native qualification gates

    @svelderrainruiz svelderrainruiz committed Nov 12, 2026
  • docs: specify active capture consumer bridge

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: record P1 synthetic UI integration

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: specify one-shot synthetic UI choice

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: specify Windows synthetic UI evaluation

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: record integrated live-run policy P0 evidence

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: specify deterministic live-run authorization policy

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: record integrated offline review planner evidence

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: specify offline bounded review planning

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • docs: record integrated refusal diagnostics and bounded L2 refusal

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Specify minimized phase-level model refusal observations

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Record integrated CPU execution and refused live validation outcome

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Specify approved CPU-only model execution policy

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Record integrated Ollama hardening contracts and qualification limits

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Record integrated inference budget and privacy verification

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Record integrated aggregation verification

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Record merged Ollama model identity verification

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Specify Ollama inference safeguards and split baseline obligations

    @svelderrainruiz svelderrainruiz committed Nov 11, 2026
  • Specify source-derived configuration and precise implementation traceability

    @svelderrainruiz svelderrainruiz committed Nov 10, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 10, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 10, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 10, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 9, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 9, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 9, 2026
  • 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>

    @svelderrainruiz svelderrainruiz committed Nov 9, 2026
  • Add governed system requirements specification Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

    @svelderrainruiz svelderrainruiz committed Nov 8, 2026
  • Specify Docker-bracketed release conveyor Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

    @svelderrainruiz svelderrainruiz committed Nov 8, 2026