EVIDENCE OUTPUTS
- Official-source capture
- Human legal review
- Location-to-system impact set
- Approved change and test record
ARCHITECTURE PATTERN · SYNTHETIC REFERENCE
Connect verified notifications to affected locations, processors, systems and controlled change work.
Engineering pattern
not a legal template
WHEN TO USE
Start only after the relevant facts, source status and system boundary are understood.
SOURCE / STATUS BOUNDARY
These IDs are verification pointers to the primary-source ledger. They are not provision mappings, applicability findings or legal conclusions.
SEQUENCE DIAGRAM
captures an official notification candidate
ARTEFACT · source recordverifies scope, status and effective date
ARTEFACT · review decisionmatches affected locations and providers
ARTEFACT · impact setplan, execute and test required changes
ARTEFACT · closure evidenceTYPED JSON FIXTURE
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": "cross-border-restriction-watch",
"subjectRef": "synthetic-only",
"payload": {
"sourceRef": "official_notification_demo",
"legalReview": "required",
"automatedChange": false
}
}EVIDENCE OUTPUTS
THREAT CONSIDERATIONS
FAILURE MODES
RESEARCH / RADAR CONNECTION
Status should be computed from verified publication metadata and provision groups, while the original source and calculation basis remain visible.
Read A source model for phased legal commencementDetect official-source changes while keeping legal interpretation human-reviewed.
Supporting automation · Review 2026-09-20Open radar rationaleLOCAL WORKSPACE NOTE
Nothing is sent anywhere. Avoid names, personal data or confidential incident details.