feat: a stated choice must reach a requirement, and only pinned providers (iteration 9 step 3)
Some checks failed
validation / verify (push) Failing after 11s
Some checks failed
validation / verify (push) Failing after 11s
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>
This commit is contained in:
@@ -78,3 +78,61 @@ def scoped_ledger(**options: Any): # type: ignore[no-untyped-def]
|
||||
if ledger.phase_status(PhaseId.SCOPING) is PhaseStatus.AWAITING_APPROVAL:
|
||||
ledger.approve(PhaseId.SCOPING, actor="user")
|
||||
return ledger
|
||||
|
||||
|
||||
def carrying(sources: list[str]) -> dict[str, list]:
|
||||
"""Scripted turns for the Specialists along the Requirements chain, in which one
|
||||
more requirement, NFR-2, carries what the customer stated (`sources`), and a
|
||||
Check, K-3, holds the design to it."""
|
||||
import json
|
||||
|
||||
from app.adk.fake_runtime import SAMPLE_DATA, Call
|
||||
|
||||
def submission(kind: DeliverableKind, **files: str) -> Call:
|
||||
call = sample_submission(kind)
|
||||
return Call(
|
||||
call.tool,
|
||||
{**call.args, "attachments": {**call.args["attachments"], **files}},
|
||||
)
|
||||
|
||||
requirements = json.loads(SAMPLE_DATA["requirements.json"])
|
||||
requirements.append(
|
||||
{
|
||||
"id": "NFR-2",
|
||||
"kind": "non_functional",
|
||||
"text": "The design honours what the customer stated.",
|
||||
"conditions": ["Each stated choice is configured as stated."],
|
||||
"from": sources,
|
||||
}
|
||||
)
|
||||
components = json.loads(SAMPLE_DATA["components.json"])
|
||||
components[0]["requirements"].append("NFR-2")
|
||||
graph = json.loads(SAMPLE_DATA["target-architecture.json"])
|
||||
graph["checks"].append(
|
||||
{
|
||||
"id": "K-3",
|
||||
"applies_to": "E-1",
|
||||
"source": "NFR-2",
|
||||
"statement": "the stated choices are configured",
|
||||
}
|
||||
)
|
||||
implementation = json.loads(SAMPLE_DATA["implementation.json"])
|
||||
implementation.append(
|
||||
{"check": "K-3", "file": "terraform/main.tf", "address": "example.run"}
|
||||
)
|
||||
verdicts = json.loads(SAMPLE_DATA["verdicts.json"])
|
||||
verdicts["checks"].append(
|
||||
{"check": "K-3", "verdict": "pass", "evidence": "Configured as stated."}
|
||||
)
|
||||
K = DeliverableKind
|
||||
files = {
|
||||
K.REQUIREMENTS: {"requirements.json": json.dumps(requirements)},
|
||||
K.TECHNICAL_DECOMPOSITION: {"components.json": json.dumps(components)},
|
||||
K.TARGET_ARCHITECTURE: {"target-architecture.json": json.dumps(graph)},
|
||||
K.DEPLOYMENT_GUIDANCE: {"implementation.json": json.dumps(implementation)},
|
||||
K.VALIDATION_RESULTS: {"verdicts.json": json.dumps(verdicts)},
|
||||
}
|
||||
return {
|
||||
DEPENDENCY_GRAPH[kind].specialist: [[submission(kind, **attached)]]
|
||||
for kind, attached in files.items()
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user