# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:28:05Z", "synthesisSha256": "374843e9c247e28137cdc3e7252c233e2c1ef90b471a33c4046fb52400c63e05", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-019", "registryId": "vr.wm-act-019", "name": "Incident / Emergency", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.INC" ], "tags": [ "incident", "emergency", "act.inc" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-019-incident-emergency/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-019", "model": { "registry_id": "vr.wm-act-019", "model_id": "WM-ACT-019", "name": "Incident / Emergency", "entry_kind": "entity", "purpose": "Represent one authority-declared operational or emergency incident with revisioned severity, impact, containment, restoration, resolution and review assertions.", "scope_statement": "A persistent incident record rooted in an evidenced declaration by a competent operator or authority. Reports can be linked while qualification is pending; a pending report is not silently promoted to a declared incident. A declaration may later be retracted. The record persists through reassessment, handover, partial recovery, closure and reopening.", "in_scope": [ "Qualified incident identity, declaration basis, classification and ownership", "Revisioned severity, impact, extent, evidence and incident state assessments", "Incident-specific response objectives, task references, warning references and transition decisions", "Closure, residual obligations, review findings and controlled record continuity" ], "out_of_scope": [ "Raw occurrence and measurement masters, persistent problem management and defect remediation", "Executing response processes or tasks, dispatching resources, issuing warnings or transmitting messages", "Independent cyber or AI incident qualification, clinical treatment, legal emergency powers and tactical procedures", "Whole-of-society disaster risk management, hazard prediction and long-term reconstruction programmes", "Runtime conformance, automated emergency decisions and generic audit or retention execution services" ], "boundary_notes": [ { "neighbor": "WM-ACT-015", "distinction": "Occurrence evidence supports a declaration but keeps its own occurrence identity and lifecycle.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "WM-MAT-008", "distinction": "Observation and measurement records remain external masters; local impact assessments reference values, method, uncertainty and time.", "source_refs": [ "SRC-003", "SRC-006" ] }, { "neighbor": "WM-KNW-014", "distinction": "Persistent problems and cause claims are referenced, not solved or assigned a new problem lifecycle here.", "source_refs": [ "SRC-005", "SRC-006" ] }, { "neighbor": "WM-SFT-014", "distinction": "Software defects may be implicated; incident restoration does not prove defect remediation.", "source_refs": [ "SRC-005" ] }, { "neighbor": "WM-ACT-006", "distinction": "Containment, restoration and remediation tasks retain task execution and assignment ownership; only incident-specific links and assessments are local.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "WM-ACT-027", "distinction": "Warning and communication interactions own message content, delivery and cancellation; incident records only reference them.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-ACT-020", "distinction": "Cyber incident qualification can correlate with the same emergency but remains independently governed. No forced identity equivalence or cybersecurity workflow inheritance.", "source_refs": [ "SRC-005" ] }, { "neighbor": "WM-AI-010", "distinction": "Incoming AI incident report linkage does not give this model ownership of reporting taxonomy or reporting duties.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-ACT-042", "distinction": "Incident response process definitions and execution are external context; this model records incident state and references response evidence only.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "Hazard, disaster and sustained situation", "distinction": "An emergency designation is profile-specific; reported harm, threatened harm and slow onset may support an incident declaration. A hazard or long-running situation alone is not automatically an incident record.", "source_refs": [ "SRC-003", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "National Incident Management System, Third Edition", "organization": "Federal Emergency Management Agency", "url": "https://training.fema.gov/EMIWeb/IS/IS700b/Handouts/National_Incident_Management%20System_Third%20Edition_October_2017.pdf", "version_or_date": "October 2017", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Selected management characteristics, command transfer, objectives, documentation and coordination concepts. US framework, not universal authority or tactical instructions." }, { "id": "SRC-002", "title": "Common Alerting Protocol Version 1.2", "organization": "OASIS", "url": "https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html", "version_or_date": "OASIS Standard, 2010-07-01", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Sections 3.2.1-3.2.4 distinguish alert identity, incident references, distribution scope, timing and warning assessment fields. Alignment only; this model does not own warning transmission." }, { "id": "SRC-003", "title": "Sendai Framework terminology: Disaster", "organization": "United Nations Office for Disaster Risk Reduction", "url": "https://www.undrr.org/terminology/disaster", "version_or_date": "2017 terminology; page accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Disaster, emergency and impact are not interchangeable; slow onset and multiple impact domains prevent a discrete-onset-only boundary." }, { "id": "SRC-004", "title": "Emergency response framework, Edition 2.1", "organization": "World Health Organization", "url": "https://www.who.int/publications/i/item/9789240058064", "version_or_date": "2024-02-12, Edition 2.1", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Publication overview supports assessment, grading and response as distinct concerns in the issuing institution. Full linked PDF retrieval failed; no detailed grading thresholds are admitted." }, { "id": "SRC-005", "title": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile", "organization": "National Institute of Standards and Technology", "url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf", "version_or_date": "SP 800-61 Revision 3, April 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Selected RS.MA and RC.RP concepts inform operational comparison: qualification, priority, recovery evidence and closure criteria. Cyber-specific qualification and execution stay in the sibling model." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Sections 3.1-3.3 and term definitions support attribution, derivation and revision links. Provenance is not truth or authority certification." }, { "id": "SRC-007", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002, RFC 3339", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Section 5.6 supports timestamp representation. Distinct incident, observation and ingestion times are an authored model design; no event ordering is inferred from clock values alone." }, { "id": "SRC-008", "title": "Guidance for after action review (AAR)", "organization": "World Health Organization", "url": "https://www.who.int/publications/i/item/WHO-WHE-CPI-2019.4", "version_or_date": "2019-04-01, WHO/WHE/CPI/2019.4", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:26:26Z", "relevance": "Publication overview supports structured review and continuous improvement in a public-health context. No universal mandatory review schedule or operational implementation is inferred." } ], "structure": { "bundles": [ { "id": "bundle-identity", "name": "Identity and declaration", "description": "Identify the declared incident and qualify its class and basis.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-identity", "name": "Incident identity", "description": "Bind identity to its accountable namespace. Similar location or timing is insufficient for merging incidents.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-identity", "name": "Stable qualified record", "description": "Bind identity to its accountable namespace. Similar location or timing is insufficient for merging incidents.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-identity-1", "text": "Which master namespace and incident identifier distinguish this record from reports and other incidents?", "kind": "identity", "answer_data": [ "master_namespace, incident_id, aliases, reconciliation_status", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-identity-2", "text": "Which correlated, duplicate, split or merged incident records exist, and who approved each link?", "kind": "relationship", "answer_data": [ "related_incident_ref, relation_type, approval_ref, supersession_rule", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-identity-3", "text": "Which declaration and source revisions establish the identity being reviewed?", "kind": "provenance", "answer_data": [ "declaration_ref, source_revision, custodian_ref, record_revision", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-identity-1", "name": "Incident identity answer group 1", "description": "Candidate nested fields: master_namespace, incident_id, aliases, reconciliation_status. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-identity-2", "name": "Incident identity answer group 2", "description": "Candidate nested fields: related_incident_ref, relation_type, approval_ref, supersession_rule. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-identity-3", "name": "Incident identity answer group 3", "description": "Candidate nested fields: declaration_ref, source_revision, custodian_ref, record_revision. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Incident identity register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-qualification", "name": "Declaration and classification", "description": "Record the responsible declaration and profile-specific qualification. Actual, exercise, test, suspected and retracted assertions must not be conflated. Emergency and disaster are not universal severity grades.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-qualification", "name": "Evidenced qualification", "description": "Record the responsible declaration and profile-specific qualification. Actual, exercise, test, suspected and retracted assertions must not be conflated. Emergency and disaster are not universal severity grades.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-qualification-1", "text": "Which competent role declared this incident, under which policy or jurisdiction and effective interval?", "kind": "authority", "answer_data": [ "declarer_ref, mandate_ref, profile_version, effective_interval", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-qualification-2", "text": "Which incident class and emergency designation apply, and which assertions remain unconfirmed or exercise-only?", "kind": "classification", "answer_data": [ "class_code, scheme_version, designation, reality_status, qualification_status", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-qualification-3", "text": "What evidence supports rejection or retraction of the declaration without erasing the original report?", "kind": "exception", "answer_data": [ "assessment_ref, disposition, reason, superseded_assertion_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-qualification-1", "name": "Declaration and classification answer group 1", "description": "Candidate nested fields: declarer_ref, mandate_ref, profile_version, effective_interval. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "data-qualification-2", "name": "Declaration and classification answer group 2", "description": "Candidate nested fields: class_code, scheme_version, designation, reality_status, qualification_status. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "data-qualification-3", "name": "Declaration and classification answer group 3", "description": "Candidate nested fields: assessment_ref, disposition, reason, superseded_assertion_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-qualification", "name": "Declaration and classification register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-situation", "name": "Evidence and extent", "description": "Describe what supports the incident and where and when effects apply.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-evidence", "name": "Reports and evidence", "description": "Link occurrence and observation masters; distinguish claims, observations, estimates and disputed information. A digest preserves integrity, not truth.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-evidence", "name": "Attributed evidence links", "description": "Link occurrence and observation masters; distinguish claims, observations, estimates and disputed information. A digest preserves integrity, not truth.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-evidence-1", "text": "Which reports and occurrence or observation records support each incident assertion?", "kind": "evidence", "answer_data": [ "assertion_id, report_ref, occurrence_ref, observation_ref, evidence_role", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-evidence-2", "text": "Which reports are stale, contradictory or unverified, and what assessment remains pending?", "kind": "quality", "answer_data": [ "quality_status, freshness_limit, contradiction_ref, review_owner", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-evidence-3", "text": "Which evidence payloads require a restricted view or an external protected reference?", "kind": "privacy", "answer_data": [ "sensitivity, purpose, access_policy_ref, redaction_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-evidence-1", "name": "Reports and evidence answer group 1", "description": "Candidate nested fields: assertion_id, report_ref, occurrence_ref, observation_ref, evidence_role. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-evidence-2", "name": "Reports and evidence answer group 2", "description": "Candidate nested fields: quality_status, freshness_limit, contradiction_ref, review_owner. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-evidence-3", "name": "Reports and evidence answer group 3", "description": "Candidate nested fields: sensitivity, purpose, access_policy_ref, redaction_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-evidence", "name": "Reports and evidence register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-extent", "name": "Time and affected extent", "description": "Keep origin, affected footprint and warning area distinct. Unknown onset, intervals and changing extent are valid; nonspatial service impact does not require invented coordinates.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "findings": [ { "id": "finding-extent", "name": "Qualified extent snapshot", "description": "Keep origin, affected footprint and warning area distinct. Unknown onset, intervals and changing extent are valid; nonspatial service impact does not require invented coordinates.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "q-extent-1", "text": "What onset interval, report time, declaration time and observation time are supported, with what precision?", "kind": "temporal", "answer_data": [ "onset_interval, reported_at, declared_at, observed_at, ingested_at, precision, timezone", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-extent-2", "text": "Which affected areas or nonspatial service boundaries apply to this assessment revision?", "kind": "spatial", "answer_data": [ "area_ref, geometry_ref, coordinate_reference_system, service_scope_ref, valid_interval", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-extent-3", "text": "What location uncertainty or disclosure restriction limits the use of this extent?", "kind": "constraint", "answer_data": [ "uncertainty, method_ref, restricted_location_policy, unknown_reason", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-extent-1", "name": "Time and affected extent answer group 1", "description": "Candidate nested fields: onset_interval, reported_at, declared_at, observed_at, ingested_at, precision, timezone. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "data-extent-2", "name": "Time and affected extent answer group 2", "description": "Candidate nested fields: area_ref, geometry_ref, coordinate_reference_system, service_scope_ref, valid_interval. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "data-extent-3", "name": "Time and affected extent answer group 3", "description": "Candidate nested fields: uncertainty, method_ref, restricted_location_policy, unknown_reason. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-extent", "name": "Time and affected extent register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assessment", "name": "Severity and impact", "description": "Preserve distinct graded judgements and attributed consequences.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-severity", "name": "Severity and priority", "description": "Retain scheme and assessor with each grade. Severity, urgency, certainty and resource priority are different assessments; no universal numeric scale is imposed.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-severity", "name": "Revisioned grading", "description": "Retain scheme and assessor with each grade. Severity, urgency, certainty and resource priority are different assessments; no universal numeric scale is imposed.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-severity-1", "text": "Which scale, grade and assessor support the current severity assessment?", "kind": "measurement", "answer_data": [ "scale_ref, scale_version, grade, assessor_ref, assessed_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-severity-2", "text": "How does the recorded response priority differ from severity, urgency and confidence?", "kind": "decision", "answer_data": [ "priority, urgency, confidence, decision_ref, rationale", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-severity-3", "text": "Which reassessment changed the grade or priority, and which earlier value does it supersede?", "kind": "lifecycle", "answer_data": [ "previous_assessment_ref, new_assessment_ref, trigger_ref, effective_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-severity-1", "name": "Severity and priority answer group 1", "description": "Candidate nested fields: scale_ref, scale_version, grade, assessor_ref, assessed_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "data-severity-2", "name": "Severity and priority answer group 2", "description": "Candidate nested fields: priority, urgency, confidence, decision_ref, rationale. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "data-severity-3", "name": "Severity and priority answer group 3", "description": "Candidate nested fields: previous_assessment_ref, new_assessment_ref, trigger_ref, effective_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-severity", "name": "Severity and priority register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-impact", "name": "Impact and attribution", "description": "Represent attributable effects on people, environment, assets and services through references and assessments. Preserve estimates, uncertainty and counting basis; absence of a report is not zero impact.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-impact", "name": "Evidence-qualified consequences", "description": "Represent attributable effects on people, environment, assets and services through references and assessments. Preserve estimates, uncertainty and counting basis; absence of a report is not zero impact.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-impact-1", "text": "Which affected entities or services are linked to this incident, with what attribution basis?", "kind": "composition", "answer_data": [ "subject_ref, impact_kind, attribution_evidence_ref, confidence", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-impact-2", "text": "What quantity, unit, measurement reference and uncertainty support each impact estimate?", "kind": "measurement", "answer_data": [ "quantity, unit, measurement_ref, assessed_at, uncertainty, estimate_status", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-impact-3", "text": "How are overlapping reports, revised totals and unknown impact distinguished from zero harm?", "kind": "validation", "answer_data": [ "population_scope, aggregation_method_ref, overlap_rule, revision_ref, unknown_reason", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-impact-1", "name": "Impact and attribution answer group 1", "description": "Candidate nested fields: subject_ref, impact_kind, attribution_evidence_ref, confidence. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-impact-2", "name": "Impact and attribution answer group 2", "description": "Candidate nested fields: quantity, unit, measurement_ref, assessed_at, uncertainty, estimate_status. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-impact-3", "name": "Impact and attribution answer group 3", "description": "Candidate nested fields: population_scope, aggregation_method_ref, overlap_rule, revision_ref, unknown_reason. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-impact", "name": "Impact and attribution register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-coordination", "name": "Authority and objectives", "description": "Maintain accountable responsibility and references to response work.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-authority", "name": "Responsibility and handover", "description": "Maintain incident-specific responsibility and handover evidence. Joint coordination does not eliminate each participant mandate; possession of an incident record grants no command authority.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-authority", "name": "Effective responsibility record", "description": "Maintain incident-specific responsibility and handover evidence. Joint coordination does not eliminate each participant mandate; possession of an incident record grants no command authority.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-authority-1", "text": "Which accountable incident custodian and responsible authority apply to the current scope?", "kind": "ownership", "answer_data": [ "custodian_ref, authority_ref, scope, mandate_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-authority-2", "text": "How are joint responsibilities, limits and unresolved authority conflicts recorded?", "kind": "authority", "answer_data": [ "responsibility_matrix_ref, jurisdiction_scope, delegation_ref, conflict_status", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-authority-3", "text": "Which accepted handover changed responsibility, and when did it take effect?", "kind": "event", "answer_data": [ "handover_ref, outgoing_role, incoming_role, accepted_at, effective_at, unresolved_items", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-authority-1", "name": "Responsibility and handover answer group 1", "description": "Candidate nested fields: custodian_ref, authority_ref, scope, mandate_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-authority-2", "name": "Responsibility and handover answer group 2", "description": "Candidate nested fields: responsibility_matrix_ref, jurisdiction_scope, delegation_ref, conflict_status. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-authority-3", "name": "Responsibility and handover answer group 3", "description": "Candidate nested fields: handover_ref, outgoing_role, incoming_role, accepted_at, effective_at, unresolved_items. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-authority", "name": "Responsibility and handover register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-objectives", "name": "Objectives and response links", "description": "Record incident objectives and references to authorized plans and tasks. Task state may inform an incident assessment but does not execute response or prove objectives achieved.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "finding-objectives", "name": "Bounded response context", "description": "Record incident objectives and references to authorized plans and tasks. Task state may inform an incident assessment but does not execute response or prove objectives achieved.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "q-objectives-1", "text": "Which authorized incident objectives and acceptance criteria apply for this operational period?", "kind": "requirement", "answer_data": [ "objective_ref, acceptance_criteria, approver_ref, operational_period", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-objectives-2", "text": "Which response process and task masters support each objective?", "kind": "relationship", "answer_data": [ "process_ref, task_ref, objective_ref, dependency, binding_version", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-objectives-3", "text": "Which recorded resource limitations or policy constraints block an objective or require escalation?", "kind": "constraint", "answer_data": [ "constraint_ref, resource_status_ref, blocked_objective_ref, escalation_decision_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-objectives-1", "name": "Objectives and response links answer group 1", "description": "Candidate nested fields: objective_ref, acceptance_criteria, approver_ref, operational_period. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-objectives-2", "name": "Objectives and response links answer group 2", "description": "Candidate nested fields: process_ref, task_ref, objective_ref, dependency, binding_version. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-objectives-3", "name": "Objectives and response links answer group 3", "description": "Candidate nested fields: constraint_ref, resource_status_ref, blocked_objective_ref, escalation_decision_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-objectives", "name": "Objectives and response links register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-progress", "name": "Communication and progress", "description": "Link warning evidence and assess scoped containment and restoration.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-communication", "name": "Warning and communication references", "description": "Retain only incident links to separately mastered warnings and communication interactions. CAP incident references differ from message identifiers, and restricted messages are not public feed entries.", "source_refs": [ "SRC-002", "SRC-001" ], "findings": [ { "id": "finding-communication", "name": "Qualified communication context", "description": "Retain only incident links to separately mastered warnings and communication interactions. CAP incident references differ from message identifiers, and restricted messages are not public feed entries.", "source_refs": [ "SRC-002", "SRC-001" ], "questions": [ { "id": "q-communication-1", "text": "Which warning or communication records refer to this incident and which audiences are authorized?", "kind": "relationship", "answer_data": [ "message_ref, communication_ref, audience_scope, authorization_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-communication-2", "text": "Which externally evidenced update, cancellation or expiry applies to each warning reference?", "kind": "state", "answer_data": [ "message_revision, update_ref, cancellation_ref, expires_at, status_observed_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-communication-3", "text": "What mapping preserves message identity, incident links, distribution scope and language without asserting delivery?", "kind": "interoperability", "answer_data": [ "mapping_version, sender_namespace, message_id, incident_binding, scope, language, loss_report", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-communication-1", "name": "Warning and communication references answer group 1", "description": "Candidate nested fields: message_ref, communication_ref, audience_scope, authorization_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-001" ] }, { "id": "data-communication-2", "name": "Warning and communication references answer group 2", "description": "Candidate nested fields: message_revision, update_ref, cancellation_ref, expires_at, status_observed_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-001" ] }, { "id": "data-communication-3", "name": "Warning and communication references answer group 3", "description": "Candidate nested fields: mapping_version, sender_namespace, message_id, incident_binding, scope, language, loss_report. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-001" ] } ], "artifacts": [ { "id": "artifact-communication", "name": "Warning and communication references register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-002", "SRC-001" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-transitions", "name": "Containment and restoration", "description": "Represent containment and restoration as separately scoped incident assertions. Partial restoration, renewed impact and overlapping phases are permitted. External task completion alone is not recovery evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-transitions", "name": "Evidence-backed progress assessments", "description": "Represent containment and restoration as separately scoped incident assertions. Partial restoration, renewed impact and overlapping phases are permitted. External task completion alone is not recovery evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-transitions-1", "text": "Which part of the incident is assessed as contained, restored or still affected?", "kind": "state", "answer_data": [ "scope_ref, containment_assessment, restoration_assessment, residual_impact, assessment_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-transitions-2", "text": "Which external observations and acceptance records support a restoration claim?", "kind": "evidence", "answer_data": [ "observation_ref, acceptance_ref, criterion_ref, assessor_ref, assessed_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-transitions-3", "text": "What renewed impact or conflicting evidence requires reassessment without overwriting the earlier transition?", "kind": "exception", "answer_data": [ "trigger_ref, disputed_transition_ref, reassessment_status, responsible_role", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-transitions-1", "name": "Containment and restoration answer group 1", "description": "Candidate nested fields: scope_ref, containment_assessment, restoration_assessment, residual_impact, assessment_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-transitions-2", "name": "Containment and restoration answer group 2", "description": "Candidate nested fields: observation_ref, acceptance_ref, criterion_ref, assessor_ref, assessed_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-transitions-3", "name": "Containment and restoration answer group 3", "description": "Candidate nested fields: trigger_ref, disputed_transition_ref, reassessment_status, responsible_role. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-transitions", "name": "Containment and restoration register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-resolution", "name": "Resolution and learning", "description": "Track closure revisions, residual obligations and review conclusions.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-resolution", "name": "Resolution and reopening", "description": "Record authorized closure or reopening decisions by revision. Closure need not mean zero harm, complete remediation or finished review. A retracted declaration is distinct from a resolved real incident.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-resolution", "name": "Qualified closure decisions", "description": "Record authorized closure or reopening decisions by revision. Closure need not mean zero harm, complete remediation or finished review. A retracted declaration is distinct from a resolved real incident.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-resolution-1", "text": "Which evidence and responsible decision support the claimed incident resolution?", "kind": "decision", "answer_data": [ "decision_ref, authority_ref, resolution_criteria, supporting_evidence, outcome", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-resolution-2", "text": "Which closure, retraction or reopening revision is current, and what triggered that change?", "kind": "lifecycle", "answer_data": [ "disposition, revision, supersedes_ref, trigger_ref, effective_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-resolution-3", "text": "Which residual risks and outstanding obligations have an acknowledged owner after closure?", "kind": "requirement", "answer_data": [ "residual_risk_ref, obligation_ref, accountable_role, acceptance_ref, due_rule_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-resolution-1", "name": "Resolution and reopening answer group 1", "description": "Candidate nested fields: decision_ref, authority_ref, resolution_criteria, supporting_evidence, outcome. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-resolution-2", "name": "Resolution and reopening answer group 2", "description": "Candidate nested fields: disposition, revision, supersedes_ref, trigger_ref, effective_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-resolution-3", "name": "Resolution and reopening answer group 3", "description": "Candidate nested fields: residual_risk_ref, obligation_ref, accountable_role, acceptance_ref, due_rule_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-resolution", "name": "Resolution and reopening register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-review", "name": "Learning and follow-up", "description": "Keep incident-specific review findings, limitations and recommendations. Action execution and persistent cause analysis remain external; a completed review is not evidence that every action succeeded.", "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-review", "name": "Review conclusions and action references", "description": "Keep incident-specific review findings, limitations and recommendations. Action execution and persistent cause analysis remain external; a completed review is not evidence that every action succeeded.", "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-review-1", "text": "Which review examined this incident and what scope, participants and evidence did it use?", "kind": "process", "answer_data": [ "review_ref, review_scope, participant_roles, evidence_refs, reviewed_at", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-review-2", "text": "Which review conclusions are supported, disputed or limited by missing evidence?", "kind": "quality", "answer_data": [ "finding_ref, support_ref, dissent_ref, limitation, confidence", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-review-3", "text": "Which improvement task or problem records address each recommendation, with what completion evidence?", "kind": "relationship", "answer_data": [ "recommendation_ref, task_ref, problem_ref, accountable_role, completion_evidence_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-review-1", "name": "Learning and follow-up answer group 1", "description": "Candidate nested fields: review_ref, review_scope, participant_roles, evidence_refs, reviewed_at. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ] }, { "id": "data-review-2", "name": "Learning and follow-up answer group 2", "description": "Candidate nested fields: finding_ref, support_ref, dissent_ref, limitation, confidence. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ] }, { "id": "data-review-3", "name": "Learning and follow-up answer group 3", "description": "Candidate nested fields: recommendation_ref, task_ref, problem_ref, accountable_role, completion_evidence_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-review", "name": "Learning and follow-up register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-008", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Stewardship and acceptance", "description": "Control record continuity and expose profile and exchange limitations.", "rationale": "Authored research grouping informed by cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-continuity", "name": "Record stewardship", "description": "Apply adopting-Dimension policies to incident-local records. Preserve traceable correction without mandating indefinite personal-data retention; disposition does not close the real incident or delete target masters.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-continuity", "name": "Controlled continuity and disposition", "description": "Apply adopting-Dimension policies to incident-local records. Preserve traceable correction without mandating indefinite personal-data retention; disposition does not close the real incident or delete target masters.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "q-continuity-1", "text": "Which recipient and purpose authorize access to each incident view or artifact?", "kind": "access", "answer_data": [ "recipient_role, purpose, permitted_scope, policy_ref, exception_basis", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-continuity-2", "text": "Which retention schedule, preservation hold and approved disposition apply to local incident payloads?", "kind": "retention", "answer_data": [ "schedule_ref, trigger, hold_ref, disposition_ref, responsible_custodian", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-continuity-3", "text": "What minimal evidence records corrections, redactions or disposal while avoiding retained sensitive payloads?", "kind": "provenance", "answer_data": [ "change_ref, actor_role, basis_ref, prior_revision, digest, tombstone_ref", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-continuity-1", "name": "Record stewardship answer group 1", "description": "Candidate nested fields: recipient_role, purpose, permitted_scope, policy_ref, exception_basis. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-continuity-2", "name": "Record stewardship answer group 2", "description": "Candidate nested fields: schedule_ref, trigger, hold_ref, disposition_ref, responsible_custodian. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-continuity-3", "name": "Record stewardship answer group 3", "description": "Candidate nested fields: change_ref, actor_role, basis_ref, prior_revision, digest, tombstone_ref. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-continuity", "name": "Record stewardship register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-acceptance", "name": "Exchange and acceptance", "description": "Treat standards as conceptual alignments. Local schema validity cannot certify emergency readiness, statutory compliance, message delivery or executable conformance.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-acceptance", "name": "Profile and conformance limits", "description": "Treat standards as conceptual alignments. Local schema validity cannot certify emergency readiness, statutory compliance, message delivery or executable conformance.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-acceptance-1", "text": "Which pinned target profile and neighbor bindings can represent this incident without losing qualifiers?", "kind": "interoperability", "answer_data": [ "profile_id, profile_version, neighbor_binding, supported_fields, loss_report", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-acceptance-2", "text": "Which acceptance fixtures test conflicting reports, partial restoration, reopening and restricted warnings?", "kind": "validation", "answer_data": [ "fixture_refs, expected_results, schema_version, test_report, unresolved_failures", "Assertion status, source revision and explicit unknown or not-applicable reason" ] }, { "id": "q-acceptance-3", "text": "Which publication or operational use must be refused because review, authority or disclosure evidence is missing?", "kind": "security", "answer_data": [ "missing_gate, refusal_reason, escalation_role, permitted_local_action", "Assertion status, source revision and explicit unknown or not-applicable reason" ] } ], "data_elements": [ { "id": "data-acceptance-1", "name": "Exchange and acceptance answer group 1", "description": "Candidate nested fields: profile_id, profile_version, neighbor_binding, supported_fields, loss_report. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "data-acceptance-2", "name": "Exchange and acceptance answer group 2", "description": "Candidate nested fields: fixture_refs, expected_results, schema_version, test_report, unresolved_failures. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "data-acceptance-3", "name": "Exchange and acceptance answer group 3", "description": "Candidate nested fields: missing_gate, refusal_reason, escalation_role, permitted_local_action. Nested schema and cardinality constraints require adopter profile validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-acceptance", "name": "Exchange and acceptance register", "description": "Incident-local versioned assessment or reference index; externally mastered evidence is linked, not re-owned.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision; otherwise a governed global identifier or local UUID with reconciliation status. Use opaque incident key and immutable entry sequence; no personal data in names.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-incident", "name": "Resolve an incident reference", "description": "Proposed local operation, not implemented. Resolve qualified identity conservatively; return ambiguity rather than merge by geography or time.", "inputs": [ "master namespace", "incident identifier", "authorized purpose" ], "outputs": [ "resolved reference or ambiguity report" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "No master identity change" ], "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "record-declaration", "name": "Record an existing declaration", "description": "Proposed local operation, not implemented. Record evidence of a competent declaration or retraction; do not declare an emergency or confer legal powers.", "inputs": [ "declaration evidence", "mandate and profile references", "expected revision" ], "outputs": [ "declaration index revision or refusal" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "Append qualification and provenance only" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "revise-assessment", "name": "Record an incident assessment revision", "description": "Proposed local operation, not implemented. Attach supported severity, impact, extent or progress assessment with its author and scope; do not calculate hazard forecasts or execute response.", "inputs": [ "assessment evidence and scale", "scope and time qualifiers", "expected revision" ], "outputs": [ "assessment revision or refusal" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "Preserve supersession and unresolved contradictory evidence" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "link-response-record", "name": "Link an external response record", "description": "Proposed local operation, not implemented. Bind existing task, warning or response evidence to an incident objective or assertion. Neither dispatch work nor send or cancel a warning.", "inputs": [ "incident objective or assertion", "external master reference and revision", "authorization and expected revision" ], "outputs": [ "validated local linkage or refusal" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "Append relationship provenance without changing the target master" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "record-resolution", "name": "Record closure or reopening evidence", "description": "Proposed local operation, not implemented. Record an authorized incident decision, criteria and residual obligations; do not independently resolve the incident or accept risk.", "inputs": [ "decision and authority evidence", "criteria and residual obligation references", "expected revision" ], "outputs": [ "resolution revision or refusal" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "Append the evidenced disposition; preserve earlier closures and their scope" ], "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "export-incident-view", "name": "Prepare an authorized incident view", "description": "Proposed local operation, not implemented. Build a local recipient-scoped projection retaining uncertainty and mapping losses; no transmission and no presumption that aggregate data is anonymous.", "inputs": [ "recipient authorization", "incident revision", "target profile and redaction policy" ], "outputs": [ "local view with loss report or refusal" ], "preconditions": [ "Role, purpose, incident scope and evidence permissions verified", "Authority or required profile gaps cause refusal", "Mutations require expected revision and idempotency key; stale or conflicting input is rejected" ], "effects": [ "Create a local projection and access evidence under retention policy" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "composition": [ { "target": "WM-ACT-015", "relation": "REFERENCE", "purpose": "Occurrence evidence supports a declaration but keeps its own occurrence identity and lifecycle. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-MAT-008", "relation": "REFERENCE", "purpose": "Observation and measurement records remain external masters; local impact assessments reference values, method, uncertainty and time. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-KNW-014", "relation": "REFERENCE", "purpose": "Persistent problems and cause claims are referenced, not solved or assigned a new problem lifecycle here. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "target": "WM-SFT-014", "relation": "REFERENCE", "purpose": "Software defects may be implicated; incident restoration does not prove defect remediation. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-ACT-006", "relation": "REFERENCE", "purpose": "Containment, restoration and remediation tasks retain task execution and assignment ownership; only incident-specific links and assessments are local. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-ACT-027", "relation": "REFERENCE", "purpose": "Warning and communication interactions own message content, delivery and cancellation; incident records only reference them. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-ACT-020", "relation": "REFERENCE", "purpose": "Cyber incident qualification can correlate with the same emergency but remains independently governed. No forced identity equivalence or cybersecurity workflow inheritance. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-AI-010", "relation": "REFERENCE", "purpose": "Incoming AI incident report linkage does not give this model ownership of reporting taxonomy or reporting duties. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "WM-ACT-042", "relation": "REFERENCE", "purpose": "Incident response process definitions and execution are external context; this model records incident state and references response evidence only. Candidate model binding must be pinned before integration.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "NIMS 2017", "relation": "ALIGN", "purpose": "Conceptual incident coordination vocabulary; US applicability requires review.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "CAP 1.2", "relation": "ALIGN", "purpose": "Warning reference mapping only; no message producer or consumer conformance.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "PROV-O 2013", "relation": "ALIGN", "purpose": "Conceptual assertion attribution and revision links, not truth certification.", "required": false, "source_refs": [ "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable incident custodian and competent operator or authority, with evidenced mandate", "Applicable jurisdiction and incident profile, classification scheme and revision policy", "Master namespace, permitted recipient scopes, retention schedule and escalation roles" ], "namespace_guidance": "Use an authority-qualified opaque incident ID; dates, locations and person names do not establish identity.", "registry_links": [ "vr.wm-act-019", "Pin candidate neighbor versions before operational integration" ] }, "canon_and_patch": { "canonicalization_rules": [ "Keep declaration, assessment and external evidence identities distinct. Never normalize an unknown value to zero or a suspected incident to confirmed.", "Treat source assertions and local assessments separately; retain effective intervals, uncertainty and disputes." ], "patch_rules": [ "Use expected revision, idempotency key, actor, reason and evidence for local mutation.", "Correct by supersession; erasure and redaction follow an approved retention or privacy rule with minimal lawful change evidence." ], "compatibility_rules": [ "Version adopter profiles and field mappings; refuse projections that lose mandatory authority, scope, time or sensitivity qualifiers." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed global identifier or stable record URI", "Local UUID with reconciliation status" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit UTC offset or Z. Keep onset, event, report, declaration, observation and ingestion times separate. Preserve intervals, precision, unknown onset and clock uncertainty; do not manufacture exact instants from dates.", "serial_naming_rule": "Opaque incident key, artifact type and stable sequence or revision; no victim, responder or precise sensitive-location names in filenames.", "integrity_rule": "Keep digest algorithm, source revision and transformation provenance where available; integrity and provenance do not prove truth, command authority or delivery." }, "policies": [ "This is a noncanonical reviewable draft under the single-provider waiver; independent external review is absent.", "Standards and public-authority examples do not establish universal jurisdictional rules, emergency powers or mandatory severity thresholds.", "Local functions record existing evidence only. Declaration, dispatch, public warning, clinical intervention and acceptance of residual risk remain with authorized external roles and systems.", "Dangerous incident subjects remain at policy level; no weapon, detention, controlled-item or hazardous-response operational instructions are specified.", "Minimize personal data and sensitive infrastructure detail. Do not assume that pseudonyms or aggregate statistics eliminate reidentification risk." ], "crud": { "read": [ "Authorize recipient and purpose, resolve target permissions, and return only a scoped view with uncertainty qualifiers." ], "create": [ "Require master namespace, incident key, custodian and declaration evidence. Keep reports awaiting qualification in a distinct linked intake state; creation alone cannot establish a real declaration." ], "update": [ "Append sourced assessment or decision revisions against the expected version; preserve disputes and reference ownership." ], "delete": [ "Adopting-Dimension records policy governs retention, preservation holds and authorized deletion of incident-local payloads and copies; the authorized storage service executes disposition. Retain only minimal lawful tombstones or change evidence, not perpetual personal payloads.", "Local record deletion neither resolves the real incident nor deletes occurrence, measurement, task, warning or other target masters." ] }, "roles": [ { "name": "Incident custodian", "responsibilities": [ "Maintain identity, reference continuity and permitted local records." ] }, { "name": "Competent incident authority", "responsibilities": [ "Supply evidenced declarations, responsibility decisions and resolution approvals within its mandate." ] }, { "name": "Authorized assessor", "responsibilities": [ "Record scoped assessments with uncertainty and supporting evidence." ] }, { "name": "Response liaison", "responsibilities": [ "Reconcile references and handover evidence without acquiring task execution authority." ] }, { "name": "Records and access officer", "responsibilities": [ "Approve recipient views, exceptions, retention, holds and disposition." ] }, { "name": "Review facilitator", "responsibilities": [ "Document supported lessons, dissent and improvement references." ] } ], "access": { "default_rule": "Deny incident-content access unless recipient, purpose and scope are authorized; possession of a public warning grants no access to the incident file.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A policy-authorized emergency exception must name its basis, scope, accountable role and expiry, with subsequent review. Urgency is not a blanket bypass.", "Public views need explicit release approval and minimization, including reidentification review for aggregated impact." ], "audit_requirements": [ "Reference access and change evidence for reads, exports, corrections and disposition with actor, purpose, revision and result. Audit services and their lifecycle remain external; retain only policy-permitted local pointers." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and owner authority and access policies", "spec.yaml and visible publication holds", "Pinned adopter profile and permitted external evidence revisions" ] } }, "coverage": { "claim": "Source-grounded proposed structure for a persistent authority-declared incident record, using bounded emergency-management, public-health and operational cybersecurity examples. Separate local no-tools self-audit completed. Independent review, source/version checks, adopter policy review and executable conformance remain holds. This is a noncanonical reviewable draft, not an operational emergency system.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Qualified incident identity differs from report, occurrence and message identity." }, { "dimension": "lifecycle", "status": "covered", "notes": "Declaration, reassessment, handover, partial progress, closure, retraction and reopening." }, { "dimension": "relationships", "status": "covered", "notes": "Each registry edge retains target ownership; incoming defect and AI links do not transfer ownership." }, { "dimension": "temporal", "status": "covered", "notes": "Distinct time roles, precision and uncertain onset." }, { "dimension": "provenance", "status": "covered", "notes": "Revisioned assertions with attribution, derivation and disputed evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based incident custody and evidenced responsibility." }, { "dimension": "validation", "status": "gap", "notes": "Research gates do not replace instance schemas, acceptance fixtures or operational readiness review." }, { "dimension": "access", "status": "covered", "notes": "Recipient-scoped records and explicit exceptions." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Adopter policy controls local disposition and minimal continuity evidence." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments require pinned mappings and loss tests." }, { "dimension": "direct properties", "status": "covered", "notes": "Class, scope, grade and state are incident properties. Physical quantities are impact assessments referencing measurement masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Declaration and evidence qualify the incident; raw reports remain distinguishable." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Six proposed local operations with refusal preconditions; false declaration, premature closure and disclosure are explicit hazards." }, { "dimension": "context and evidence", "status": "covered", "notes": "Jurisdiction, standards scope, operational period and external evidence constrain assertions." } ], "known_omissions": [ "Independent external review remains absent; a local Codex no-tools self-audit is not a second provider.", "Direct HTTP checks are not attempted under the owner-reported sandbox block. Browser access does not prove current versions, availability, licensing or applicability.", "Full WHO ERF text was not retrieved; only publication overview claims are admitted. ISO 22320 and EDXL leads from legacy material are not admitted as verified standards evidence.", "Executable nested instance schemas, CAP mappings, neighbor bindings and adversarial acceptance fixtures are not implemented.", "Local legal powers, reportability, mandatory time limits, privacy and records rules need qualified jurisdiction and sector profiles.", "Clinical, hazardous-material, armed-response and other specialist response tactics, mass-casualty operations and long-term reconstruction are outside this policy-level model." ], "conflicts": [], "regional_assumptions": [ "NIMS is a US framework, WHO sources are public-health institutional examples, and NIST is cybersecurity guidance; none defines universal emergency authority.", "The model permits prolonged or slow-onset emergencies when an authority declares an incident; the source terminology does not make every hazard or situation an incident." ], "adversarial_checks": [ "Reject legacy occurrence inheritance and target-owned response execution.", "Reject one immutable closure record, confirmed impact from unverified totals, and recovery inferred from task completion.", "Reject message cancellation as incident resolution and blanket public disclosure of alerts or incident evidence.", "Reject source access or research schema validity as current-law, runtime or operational conformance certification." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root persists across declarations, assessments, handovers, closure revisions and reopening. The current registry purpose and outgoing occurrence reference support a declared incident record, while raw occurrence, measurement, task, communication, problem and cyber qualification lifecycles remain separately mastered. The registry standalone-mm value does not itself classify the subject kind." }, "decisions": [ { "concept": "Persistent incident identity", "disposition": "accepted", "rationale": "Namespace-qualified identity, declaration evidence and conservative correlation preserve one governed incident record without equating it to a report or raw occurrence." }, { "concept": "Legacy occurrence inheritance", "disposition": "rejected", "rationale": "The current WM-ACT-015 reference contract takes precedence. The source and supplement are migration leads, and their inheritance or conformance claims are not ratified." }, { "concept": "Qualification and slow onset", "disposition": "qualified", "rationale": "A competent declaration remains the boundary. Suspected reports, exercise assertions and retractions retain explicit status, and prolonged or uncertain onset does not automatically exclude a declared incident." }, { "concept": "Evidence and affected extent", "disposition": "accepted", "rationale": "External observations and occurrences keep their masters. Local assertions retain uncertainty, disputes, precision and scope without inventing geography for a nonspatial service incident." }, { "concept": "Severity and priority", "disposition": "separated", "rationale": "Scheme-qualified severity, urgency, confidence and response priority are different assessments. WHO overview evidence cannot supply unreviewed grading thresholds or a universal scale mapping." }, { "concept": "Impact and measurement ownership", "disposition": "qualified", "rationale": "Local impact attribution may reference measured quantities, but measurement method and record identity stay external. Unknown counts and overlapping reports cannot be normalized to zero or confirmed totals." }, { "concept": "Authority and response execution", "disposition": "separated", "rationale": "Responsibility, handover evidence and incident objectives do not transfer task execution or dispatch ownership. Joint coordination does not erase participant mandates or authorize an agent to command resources." }, { "concept": "Warnings and public disclosure", "disposition": "legacy blanket rule rejected", "rationale": "The model carries references and observed status only. Restricted and private warning scopes defeat the legacy open-feed assumption; message identity, cancellation and delivery stay externally governed." }, { "concept": "Containment restoration and closure", "disposition": "separated", "rationale": "Scoped progress assessments can overlap and remain partial. Task completion does not establish restoration, and closure does not imply zero residual harm, defect remediation or completed review." }, { "concept": "Single closure and review completion", "disposition": "replaced by revisioned decisions", "rationale": "Closure, retraction and reopening use provenance and supersession. Review findings link to external problem and improvement tasks without claiming those tasks have completed." }, { "concept": "Proposed local operations", "disposition": "accepted as unimplemented design", "rationale": "All six functions record, resolve, link or project local evidence with authority, access and revision gates. None declares an emergency, sends a warning, executes a task or accepts residual risk." }, { "concept": "Record continuity and access", "disposition": "accepted with adopter dependency", "rationale": "Policy-based retention and scoped disposal reconcile correction history with minimal lawful evidence. Public messages and aggregated views do not automatically authorize access to protected incident content." }, { "concept": "Source and conformance claims", "disposition": "limited and held", "rationale": "Selected official source content supports bounded concepts, not universal requirements. Direct HTTP was not attempted, WHO full-text coverage is limited, and optional field groups do not implement instance or protocol conformance." }, { "concept": "Independent review and provider admission", "disposition": "waived and held", "rationale": "Claude and Grok have zero attempts and no admitted results for this run. This frozen local Codex no-tools self-audit is a separate assessment phase, not an independent external provider review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Source and version verification is incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction: zero measured HTTP 200 responses, not eight failed URLs. Selected browser content was reviewed; the WHO ERF full-text retrieval failed and the AAR handbook was not retrieved. Current versions, licensing and applicability remain unverified. The coordinator must run check_sources.py outside the sandbox and complete claim review.", "Jurisdiction and sector profiles require qualified review of declaration authority, emergency powers, reporting duties, severity scales, privacy, retention, disclosure and residual-risk acceptance before operational use. Source institutions are examples, not model owners or universal authority.", "Nested instance schemas, state-transition rules, pinned neighbor bindings, CAP and provenance mappings, executable conformance and adversarial acceptance fixtures remain incomplete. Local package generation does not establish operational readiness, runtime capability, legal compliance or remote availability.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify current primary-source versions, full-text scope, licensing and applicability, then restore independent external review before canonical promotion.", "Develop jurisdiction and sector profiles with qualified incident authorities, including non-cyber operational incidents, slow onset, contested declarations and responsibility handover.", "Implement and test nested schemas and mappings against duplicate reports, contradictory impact, partial restoration, reopening, restricted warnings, failed references and lawful disposal." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 6 } }