Deconfliction Plan Generator
When to Use
When designing or revising deconfliction, use the system-provided plan/roe.json and any current CONOPS and contact plan as context.
Workflow
- Preserve confirmed decisions from an existing plan. Use the same
engagement_nameas RoE. - Record approved source IPs, user-agent markers, tool hashes, or testing windows in
identifiers. Each entry needstypeandvalue; put context indescription. Do not invent infrastructure or claim a marker is configured when it is only proposed. - Set
notification_procedurefor the active phases authorized by RoE. Use the confirmed SOC contact from the contact plan when one exists. An absent contact or endpoint does not authorize contacting a third party. - Populate
deconfliction_codeonly with an operator-confirmed code; otherwise retain its empty default. Identify missing material coordination decisions. - Validate
plan/deconfliction.jsonagainstDeconflictionPlan. Deconfliction identifiers never expand scope or override abort triggers. Bundle publication follows the selected planning workflow.
Document schema (derived from the validator's model)
plan/deconfliction.json must validate against DeconflictionPlan. Fields not listed here are not part of the model and are ignored by the validator.
| field | type | required | allowed values / nested keys |
|---|---|---|---|
engagement_name |
str | yes | |
identifiers |
list[DeconflictionEntry] | no | each object: type, value, description |
notification_procedure |
str | no | |
soc_contact |
str | no | |
deconfliction_code |
str | no |
DeconflictionEntry object:
| field | type | required | allowed values |
|---|---|---|---|
type |
str | yes | |
value |
str | yes | |
description |
str | no |
