Case 08: a plan of 9 work packages and 15 activities, 7.2 weeks against a
10-week window, with the customer's carrier circuit on the critical path. The
stated topology was built this time. The owner keeps the estimates as they
are: one experienced engineer, no contingency.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>