Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-19.md
Jonathan Boniface 5bb22d984e
Some checks failed
validation / verify (push) Failing after 8s
fixed multile issues
2026-10-07 17:33:36 +01:00

1.3 KiB

Step 19 — Implementation Detail

Built on 2026-10-07.

  1. An implementation.json entry may be {"check": "K-7", "unimplementable": "<what the resource type lacks>"} in place of file and address. It accounts for the Check; an empty reason does not.
  2. unimplementable_checks reads those entries. The router reads them as soon as deployment guidance is submitted, and a new playbook group, "the code cannot meet a Check", sits before "validation decided" and "a Phase is complete". Its action reopens the Target architecture with each Check's id and reason. That returns the code to draft, so the group stops applying.
  3. A model Orchestrator is given the same list as unimplementable_checks in its context, and agents/orchestrator.md has the step.
  4. The validator is told to confirm with terraform_schema before failing a Check for a missing setting, and to give not verifiable when the resource type has no such setting. Not verifiable already routes to the Target architecture.

Past the Revision limit the reopen is refused as any other is: the user decides, or a pre-approved Execution ends with warnings.

Tests: tests/execution/test_requirements_chain.py (two) and tests/execution/test_router.py, "a Check the code cannot meet goes back to the graph unvalidated".