Packet Capture Plan Builder
Command builders answer how to capture; this answers where, why, and what it would mean. Describe the path and the symptom; a 35-rule original registry designs a phased capture plan: ranked points on named boundaries, expected observations, an interpretation matrix with supports and weakens decided before collection, and sync/authorization discipline. It plans captures - it never ingests them.
Operations & FieldcraftDescribe the path and the symptom; a fixed 35-rule registry designs the capture plan: where to observe, in what order, and what each observation would establish. It plans collection - it never receives captures, and it never diagnoses.
Labels and notes (export only)
Free text here goes ONLY into the exported plan - it never influences the rules.
Pick the path archetype and symptom above (or load the Example) - the plan appears as you choose.
References
- Original capture-planning ruleset (D-18: original by construction)