Programme · build plan
A roadmap that only lists features is a sales document. This one carries the gates that were agreed before the build, the 5 things the plan will not do, and the boundary it inherits from the organisation security lane. The gates are quoted, not summarised: an unquoted gate is an unpassed gate.
Programme duty set · D-17 obligation instances
0 excluded — No row was excluded: all 12 register rows render with an explicit recipient or a named absence, and no reporting clock lacks one.
0 determinations recorded · recording one requires its basis; “no obligation applies” is recordable, never inferred.
D-17 instance schema v1 · case store not built here · schema owner: polybackend — the Rust security service family the C-P3-A read client consumes (services/security_register.rs); no obligation-case store exists there yet
Risk analysis and information system security policies.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
First applies (DE)
Phase (DE)
Surface
Detection LoomSupply chain security, including supplier relationships.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
First applies (DE)
Phase (DE)
Surface
Claim ReweaverSecurity in network and information systems acquisition, development and maintenance.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
First applies (DE)
Phase (DE)
Surface
Authority RehearsalManufacturers must ensure vulnerabilities in products with digital elements are handled.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
Claim ReweaverProducts must be placed on the market without known exploitable vulnerabilities.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
Claim ReweaverActively exploited vulnerability reporting to the coordinating authority: 24 h early warning, 72 h notification, and a final report no later than 14 days after a corrective or mitigating measure is available.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
No lab surface claims this row.
Severe incident reporting to the coordinating authority: 24 h early warning, 72 h notification, and a final report within one month after the submission of the incident notification.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
No lab surface claims this row.
A digital operational resilience testing programme including TLPT at least every three years.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
Detection LoomAccuracy, robustness and cybersecurity of high-risk AI systems, including resilience to adversarial inputs.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
Authority RehearsalReporting of serious incidents to the market surveillance authorities.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
No lab surface claims this row.
Appropriate technical and organisational measures to ensure security of processing.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
Platform controls censusNotification of a personal data breach to the supervisory authority.
Entity
Applicability
Applies from
Duty holder
Recipient
Channel
Excuse or derogation
Start event
Start basis
Receipt
Correction history
Lab connection
Status note
Surface
No lab surface claims this row.
findings/13 §4 (amended 2026-11-03) — clocks are not the duty set. 10 clocks, rendered outside the count above.
NIS2
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4
CER
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4
DORA
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4
CRA Art. 14(2)
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4 ← findings/04 §3.1; anchored 2026-11-14 by security-frontier findings/09 C24–C27
CRA Art. 14(4)
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4 ← findings/04 §3.1; anchored 2026-11-14 by security-frontier findings/09 C24–C27
GDPR Art. 33
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4 ← findings/04 §3.1; anchored 2026-11-14 by security-frontier findings/09 C24–C27
AI Act Art. 73
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4 ← findings/04 §3.1; anchored 2026-11-14 by security-frontier findings/09 C24–C27
UK Bill
Not in forceStart event
First report
Second report
Final
Excuse or derogation
Status
findings/13 §4
CIRCIA
Not in forceStart event
First report
Second report
Final
Excuse or derogation
Status
findings/13 §4
BSI practice
In forceStart event
First report
Second report
Final
Excuse or derogation
findings/13 §4
Disclosure-and-action harm gate · D-18
No duty officer is seated in this build; every proposed statement or active measure stays withheld.
The gate runs before any external statement or active measure: six elements, one recorded decision, and “withheld” as a first-class outcome rather than an error path.
Sending authority: none — this build has no sending authority, no transport and no notification path
dutyOfficer
No duty officer is seated in this build; every proposed statement or measure is withheld.
recipient · basis
Required non-blank on every request; no production request exists.
attribution.state · attribution.method · attribution.secondMethod
A second method must be a different method; single-method and unattributed are sayable states.
blastRadius.affected · blastRadius.thirdPartyImpact · blastRadius.expiresAt
Third-party impact is required; an active measure requires an expiry.
custody
A named absence satisfies the field; omission does not.
outcome · reason
"withheld" is a recorded outcome, never an error path.
0 decisions recorded; “withheld” is a recorded outcome, never an error path.
Cryptographic boundary register · SF-11.3
This register records declarations. The section owns no observation: no row here is a reading of a live system, and a row stamped declared is the producer's word, not ours. It is not a CBOM and not a posture score — there is no total, no percentage, and no ordering of one row against another except the shelf life a row states itself.
A shelf life of unstated is a gap in the register, not a low priority. Those rows are held out of the ordering and render first, under their own heading, because a row with nothing to order by cannot be ranked against a row that has something — and ranking it last would invent the value the register refuses to state.
Deadline classes transcribed from findings/08-crypto-agility-pqc.md (as-of 2026-11-14); a class whose regime names no date says so. Stated shelf lives: 0 · unstated: 6.
Claim
Deadline class
Shelf life
Claim
Deadline class
Shelf life
Claim
Deadline class
Shelf life
Claim
Deadline class
Shelf life
Claim
Deadline class
Shelf life
Claim
Deadline class
Shelf life
P0 → P4
The five build gates quoted (typecheck count, scoped vitest, knip, lint, copy check exit 0); section-contract 10/10; demo delivered and the script's spoken numbers each found in the fixture corpus.
Dossier round-trip test green with `not_tested` present; census remediation recorded (0 unbacked cards); route manifest = 6; zero unadjudicated copy excusals; the S5 battery authored and green in a dry run.
All twelve S5 arms witnessed; registry lockstep complete; and the orgs S1.3/S1.5 register family folded into main and deployed, with an orgs workspace holding an approved engagement scope.
First backend-connected bench witnessed end-to-end against a real engagement; 404 and both 409s witnessed as typed refusals; no POST, no local digest; the S5 battery re-run including the backend arm.
The bet's own S5 passes; the substrate it needs exists and is named; the O09 boundary test is still green.
Prototype waiver · 2026-11-03The demo window adds four spaces — exposure, capabilities, scenarios and programme — and their routes under a dated owner waiver for the EU-grant prototype. The waiver covers the route count and placement only. Every honesty rule still applies to the new spaces, and the P1 → P2 manifest row is re-baselined to the as-built route set when placement runs. The waiver expires with the demo; the earn-your-route law resumes at P2.
5 refusals
Ownership boundary · O09
Live company security work — the SOC, incident response, and identity and access management — belongs to O09 in the organisation security lane. This laboratory does not collect, does not respond, and does not administer access. Its job is to produce evidence a live system can later be checked against, and to stop where that boundary begins.