This is a format reference, not a customer case study. It exists to show the public shape of DGS outputs without claiming a real-world outcome, exposing a customer mission, or disclosing protected internals.
A DGS output may be a bounded operating-truth case, a campaign synthesis across prosecuted theaters, or a pilot-ready implementation package. The public form should make scope and proof boundaries visible.
- Problem frame and admissible evidence.
- Selected theater or bounded case boundary.
- Surface reconstruction and failure track.
- Governing break, ownerless zone, and missing decision.
- First intervention or campaign intervention sequence.
- Pilot roles, status fields, pass/hold rules, and metrics when implementation is requested.
- Proof boundaries, non-claims, and validation path.
- Next decision or stop condition.
The format should help the reader understand how a hard problem is being structured, what scope has actually been prosecuted, what can be piloted now, and what would be required to advance, invalidate, or widen the route.