EVIDENCE OUTPUTS
- Fact and hypothesis ledger
- Scope and impact assessment
- Decision history
- Affected-person and Board packages where applicable
P07Protect
ARCHITECTURE PATTERN · SYNTHETIC REFERENCE
Breach fact ledger and communication package
Separate confirmed facts from hypotheses and generate consistent decision and communication evidence.
Engineering control
Engineering pattern
not a legal template
WHEN TO USE
Use once a suspected personal-data incident enters triage.
Start only after the relevant facts, source status and system boundary are understood.
SOURCE / STATUS BOUNDARY
Verify the legal status before implementation.
Engineering controlPattern verification pointers
These IDs are verification pointers to the primary-source ledger. They are not provision mappings, applicability findings or legal conclusions.
SEQUENCE DIAGRAM
Four accountable hand-offs.
- 01Incident lead
opens a timestamped fact ledger
ARTEFACT · incident record - 02Investigators
mark facts, sources and confidence
ARTEFACT · fact entries - 03Decision owner
records notification and mitigation decisions
ARTEFACT · decision record - 04Communications owner
builds audience-specific factual packages
ARTEFACT · approved messages
TYPED JSON FIXTURE
Synthetic by design.
This example contains no real person, provider, incident or system data. It demonstrates record boundaries, not a production schema.
{
"fixture": true,
"schemaVersion": "1.0-demo",
"pattern": "breach-fact-ledger-and-communication-package",
"subjectRef": "synthetic-only",
"payload": {
"incidentRef": "incident_demo_07",
"confidence": "working",
"factState": "unconfirmed"
}
}THREAT CONSIDERATIONS
- Incident system compromise
- Sensitive findings shared too broadly
- Premature attribution
FAILURE MODES
- Chat messages become the only record
- Draft facts are copied as confirmed
- Different audiences receive contradictory incident details
RESEARCH / RADAR CONNECTION
Keep implementation context attached.
Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision.
Read From obligation to evidence: the DPDP implementation stackAutomated legal-text monitoring
Detect official-source changes while keeping legal interpretation human-reviewed.
Supporting automation · Review 2026-09-20Open radar rationaleLOCAL WORKSPACE NOTE
Give this work a next owner.
Nothing is sent anywhere. Avoid names, personal data or confidential incident details.