35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
---
|
|
name: enterprise
|
|
depth: Comprehensive
|
|
keywords: []
|
|
description: Regulated enterprise feature, full audit trail
|
|
skeleton: on
|
|
change_control: strict
|
|
---
|
|
|
|
# enterprise scope
|
|
|
|
Comprehensive depth for regulated work that needs the full audit trail.
|
|
Every stage in the graph executes — no shortcuts. Ideation, inception,
|
|
construction, and operation all run end to end, so the artifact chain
|
|
(intent through deployment and feedback) is complete and traceable.
|
|
|
|
Change Control defaults to strict: an input that changes after a human approved or confirmed it reopens that approval, because the audit trail is the point of this scope.
|
|
|
|
## Why every stage
|
|
|
|
Enterprise work carries compliance, security-review, and sign-off
|
|
obligations that the skipped-stage scopes (`mvp`, `poc`, `bugfix`) are
|
|
willing to trade away for speed. Here the cost of an undocumented decision
|
|
is higher than the cost of running the stage, so the scope keeps the whole
|
|
spine: market-research and team-formation up front, the full design pass,
|
|
and the operation stages (observability, incident-response,
|
|
performance-validation) on the back end.
|
|
|
|
## Membership
|
|
|
|
`enterprise` is the only scope that marks every one of the 33 stages
|
|
EXECUTE. It is the reference column for the EXECUTE/SKIP grid — every other
|
|
scope is a subset of this one. There are no keyword triggers; the scope is
|
|
chosen deliberately, not inferred from a description.
|