Mission hours workstreams
MH-02 · Scope architecture, data, delivery, and controls
Can the engineer turn ambiguity into a reversible system boundary with explicit authority, data, provider, cost, and operating choices?
- Elaboration
- Outcome contract, authority envelope, and system context Architecture decisions, provider adapter, and threat model Acceptance, kill, escalation, and rollback criteria Minimum authored hours: 20.
- Source record
- Mission Hours and Field Entrustment FDE-MH/0.1, workstream MH-02
Related terms
A definition here is not a claim about any person, engagement, or outcome.