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>
2.7 KiB
Step 3 — Implementation Detail
Built on 2026-10-11. Not run with real models.
What a stated choice now has to reach
Case 08 showed a stated topology named in a design and not built, with every Check passed. A stated choice was an instruction; nothing held a design to it.
- The catalogue marks the fields that bind a design (
binds: true, 26 of them): regions and residency, availability and recovery targets, compliance frameworks and classification, encryption, audit logging, every networking field, identity, environments, and required and forbidden products. - The agreed scope lists the binding fields the customer stated, as
bindinginscope.json. A field assumed for them is not among them: an assumption is not the customer's decision. - A requirement says what it comes from, in
from: the customer's own requirement ids and the scope fields it carries. - A submission of requirements is refused (
_carries_the_scopeinapp/workflows/chain.py) when:- one of the customer's own requirements is named by no requirement;
- a binding field is named by no requirement;
- a requirement that carries a binding field is not non-functional, or has no entry in
conditions.
- From there the existing chain does the rest. A non-functional requirement's conditions each need a Check on the Target architecture, and validation gives each Check a verdict. So a stated choice now reaches a Check, in code, at every link.
What this does not prove: that the condition the analyst writes says what the customer meant, or that the Check the architect writes verifies it. It guarantees a stated choice cannot be silently dropped; whether it is honoured well is still judged by the validator.
Readiness in the guide
The packager is told to open the executive summary with what the design rests on: how much the customer stated, how much was assumed, how much is unknown. An instruction, not a check.
Also closed, from the same run
- Only the pinned providers.
check_providersinapp/tools/local.pyrefuses, before Terraform runs, a resource or data source of a provider the bundle does not pin, and arequired_providersentry for one. The target architect is told that something outside the Cloud provider's own provider is not an Element. A module's own providers are untouched: they are declared inside the module. - The scope statement names only the customer's exclusions.
Not done: intent.exclusions are free text, so nothing in code checks that an excluded thing was not built. The Specialists are told; in case 08 they complied.
Tests: tests/execution/test_requirements_chain.py (6 more), tests/tools/test_local.py (5 more).