User Requirements Specification (URS)¶
Document reference: GFTCL-URS-001 · Framework: GAMP 5 Category 5 · EU Annex 11 Verified by: PQ — Performance Qualification
FortressAI Research Institute · Norwich, Connecticut Patents: USPTO 19/460,960 · USPTO 19/096,071 — © 2026 Richard Gillespie
This specification states what the GaiaFTCL vQbit Quantum VM must do, in operator/regulator terms, independent of implementation. Each requirement is testable and traced in the Requirements Traceability Matrix.
Requirement classes¶
URS-Fxx functional · URS-Dxx data integrity · URS-Sxx security ·
URS-Cxx compliance · URS-Pxx performance.
Functional requirements¶
| ID | Requirement | Trace |
|---|---|---|
| URS-F01 | The system shall run the M⁸ = S⁴ × C⁴ quantum substrate natively on Apple Silicon, with no external runtime dependency to start. | FS-01, IQ |
| URS-F02 | The substrate shall operate autonomously through Franklin's heartbeat within operator-defined bounded authority, without per-operation operator approval. | FS-02, OQ |
| URS-F03 | The system shall expose an operator CLI for inspection and manual override of the sovereign state machine. | FS-03, CLI Reference |
| URS-F04 | The system shall compose the 19 C⁴-rail algorithms plus QC-020/QC-021 inside the vQbit VM. | FS-04, MQ |
| URS-F05 | The system shall hold a self-custody local wallet (QFOT + Euro stablecoin) and refuse to expose the private key through any interface. | FS-05, Wallet PQ Proof |
| URS-F06 | The system shall demonstrate post-quantum readiness: Shor recovery against classical keys and proven safety after PQ migration. | FS-06, Wallet PQ Proof |
Data-integrity requirements¶
| ID | Requirement | Trace |
|---|---|---|
| URS-D01 | All records shall be append-only; update and delete shall be refused at the database level. | FS-D01, Data Integrity |
| URS-D02 | Every record shall carry a canonical witness and SHA-256 witness hash enabling bit-exact re-verification. | FS-D02 |
| URS-D03 | Every record shall carry a federation cosignature quintet attributable to its signing cell. | FS-D03 |
| URS-D04 | Substrate arithmetic shall be exact-rational; floating-point value amounts shall be refused. | FS-D04 |
| URS-D05 | Sessions shall be bit-exact replayable from sealed anchors. | FS-D05, PQ |
Security requirements¶
| ID | Requirement | Trace |
|---|---|---|
| URS-S01 | Private keys shall never be agent-generated, displayed, logged, or emitted to the mesh. | FS-S01, Security |
| URS-S02 | The production binary shall contain no testnet/regtest/simulation path. | FS-S02 |
| URS-S03 | Operator authority shall be bounded by configuration files the operator controls. | FS-S03, Config Spec |
Compliance requirements¶
| ID | Requirement | Trace |
|---|---|---|
| URS-C01 | The system shall self-qualify (IQ→OQ→PQ→MQ) and seal signed receipts re-verifiable by a regulator. | Qualification Catalog |
| URS-C02 | The system shall enforce a constitutional floor (C-007…C-010) per measurement. | FS-C02, SDS §6 |
| URS-C03 | The system shall maintain an audit trail meeting 21 CFR Part 11 / EU Annex 11 expectations. | Part 11 |
Performance requirements¶
| ID | Requirement | Trace |
|---|---|---|
| URS-P01 | Per-algorithm capacity shall scale to host resources while preserving measurement invariants. | FS-P01, SDS §5 |
| URS-P02 | The live qualification gate (18–19 in-app checks) shall pass (CALORIE) before a release ships. | PQ |
Federation-cosigned
This page's source is sealed in the GaiaFTCL federation manifest — page SHA-256 acea534363e4c856…, manifest witness a090592e0609adc8…, signed 2026-06-02T18:58:22Z by cell gaiaftcl-mac-cell. Verify with gaiaftcl wiki sign --all and compare wiki-all-signatures.json.