Case 08 named the customer's stated topology in its design and did not build
it; every Check passed because none asked for it.
- The catalogue marks the 26 fields that bind a design. The agreed scope lists
the ones the customer stated; what was assumed for them does not bind.
- A requirement says what it comes from. A submission of requirements is
refused when one of the customer's own requirements, or a stated binding
field, is named by none, or when the requirement carrying a choice is not a
constraint with a condition. The existing chain then owes it a Check.
- Generated code may use only the providers the bundle pins: a resource or a
required_providers entry of any other is refused before Terraform runs.
- The guide opens with how much of the design the customer stated, how much
was assumed and how much is unknown.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every Execution now begins by agreeing the scope, before requirements.
- A new Phase and Deliverable, produced by a scope analyst with two tools:
scope_read shows what is settled and what is not; scope_set records fields
with where each value came from (the request, the customer's answer, or an
assumption with its reason). Code checks each value against the catalogue.
- With someone present the analyst asks for what is missing; with nobody
present it assumes it, visibly. With no spec it drafts one from the request.
A value the customer stated in the file is changed only by their own answer.
- A submission cannot leave an essential field unknown. Code writes the
completed spec, the data every later Specialist reads, and the information
register, from what was recorded.
- The spec's status follows the Execution: under review, approved, then
locked as a Baseline. A Change request starts from the delivered scope.
- The requirements analyst derives from the agreed scope and no longer asks
for what it settles.
About 80 tests assumed requirements came first; tests/scoped.py runs scoping
ahead of a test's own script, and tests about order and counts are updated.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>