For an organisation that must report significant incidents to an authority (NIS2, GDPR personal-data breaches, DORA, or a regime of its own), OpsCommand keeps the clocks, drafts each report from the incident record, and keeps the evidence of what was sent and when. The plan's item is U-16 (owner/UPGRADES.md); the obligations are rows of the compliance register (compliance/REGISTER.md, U-25).
OpsCommand decides nothing here and states no law for the organisation:
- The regime is the organisation's. It adopts the regimes that apply to it, names the authority it reports to and the legal basis as it applies to it, and states each stage's deadline. Nothing is adopted by default.
- Reference stages only where the owner's plan gives them (U-16). The organisation checks each against the law as transposed where it operates, and keeps or changes it:
| Regime | Stage | Reference deadline, from awareness | |---|---|---| | NIS2 significant incident | Early warning | 24 hours | | | Incident notification | 72 hours | | | Final report | one month | | GDPR personal data breach | Breach notification | 72 hours | | DORA major ICT-related incident | Initial notification, intermediate report, final report | none: the financial entity states them |
- Whether an incident is reportable is a person's decision, by someone with the permission
regulatory.report(IT operations directors and executive management by default), with a reason and the moment the organisation became aware. AI never makes it.
The clocks
Deciding starts one report per stage, each due at the moment of awareness plus the stage's deadline. The deadline is fixed when the decision is made: a later change to the regime does not move it. Each report is due, overdue, sent in time, sent late, or not needed (its decision withdrawn). The decision and each report sent appear on the incident's timeline.
Drafts from the record (draft@1)
A draft holds the facts as recorded: the organisation, the regime, its authority and basis; the incident's reference, title, description, category, severity, status, services, affected users, workaround and resolution, when it was detected, when the organisation became aware and when it was resolved; its status changes and its communications to reporters or the public (internal notes are left out); the reason for the decision; and the earlier reports under the same decision with when they were sent and their seals. It lists what the record cannot say (for example the contact person, whether the cause is suspected to be malicious, cross-border impact), which the person writes before sending.
OpsCommand does not send anything to an authority. The person sends the report in the way the authority requires (its portal, e-mail) and records it.
Evidence of sending
A report sent is recorded once: when it was sent, to whom, how, the authority's reference, the content as sent, and its SHA-256 seal, with who recorded it. It is never changed. A decision is withdrawn, with a reason, only while nothing under it has been sent; withdrawn, it is kept.
The register for a regulator or auditor (register@1)
Administration → Regulation lists every decision whose moment of awareness falls in a period, with each report's deadline, state and evidence, sealed by SHA-256 (the seal covers the facts, not how late a report is when read). It downloads as CSV (one row per report, the last line naming the method, period and seal) or JSON.
Where
- Database: migration
0052_regulatory(ops.regimes,ops.regulatory_cases,ops.regulatory_reports,ops.regime_template,ops.save_regime,ops.open_regulatory_case,ops.record_report_sent,ops.withdraw_regulatory_case; permissionregulatory.report). Every row is in the audit chain. - API:
GET/PUT …/regulatory/regimes[/{code}];GET/POST …/incidents/{incident}/regulatory;POST …/regulatory/cases/{id}/withdraw;GET …/regulatory/reports/{id}/draft;POST …/regulatory/reports/{id}/sent;GET …/regulatory/register?from=&to=&format=csv|json. - Web: Administration → Regulation; the Regulatory reports card on an incident.