Engagement stage-gates + TPM discipline

[ojfbot]

Question

Which stages does THIS engagement traverse (lead → research → discovery → scoping → prototype → deploy → sustain?), what are each stage's entrance/success criteria as TPMs, and where does /gated-slice shadow-first discipline apply (any automation touching client data ships observe-only first)?

Type

grilling (HITL, /grill-with-docs — hand resulting slice structure to /gated-slice, not this map)

Context

Map: #344. Fleet-native gate discipline ruled IN, literal ISO-15288/Vee framing ruled OUT (operator, 2026-08-01). Two-ledgers rule: gates/TPMs decided here; delivery slices live in the roadmap.

Blocked by

#345 (Engagement northstar — properties define what TPMs measure).

Resolution (filled at close)

—

[ojfbot]

Unblocked by #345 (closed 2026-08-01) — and scope WIDENED by an operator elevation during that session:

In addition to the engagement stage-gates + TPM discipline (entrance/success criteria per arc stage, feeding ns:l1-fieldwork-1#P1), this grill now also rules how the NASA SEH process groups map onto the engagement's self-built components — system design processes top-down, product realization processes bottom-up, technical management processes cross-cutting (SEH Fig 2.1-1, the 17 processes). Intent as stated by the operator: least manual effort, most mechanical automation / auditability / transparency / accountability / accuracy. This serves ns:l1-fieldwork-1#P5 (delivery is mechanized and auditable).

Standing boundary carried from charting: literal ISO-15288/Vee framing for the client-facing stage naming remains ruled out — the SEH application here is to the operator's own build, not the customer conversation.