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

2.1 KiB

Step 17 — Implementation Detail

Built on 2026-10-07. app/tools/workspace.py keeps a working copy in the Deliverable's working memory, which the Execution already checkpoints and returns on every attempt.

Files (working["files"]), for the Deliverable whose working_copy is its own kind (deployment guidance):

  1. write_file, edit_file (replaces the one place old matches, and refuses when it matches none or several), read_file (one file, or the list) and delete_file.
  2. terraform_fmt, terraform_validate and terraform_plan run on the Terraform files in the working copy and take no files argument. terraform_fmt formats in place and returns the names it changed. Files passed anyway are written to the working copy first, so a model that ignores the instruction still works.
  3. submit_deliverable attaches the working copy; a file passed as an attachment replaces its copy. The submitted files become the working copy, so a Revision starts from them, and the task context lists them under working_copy.

The validator's working_copy is deployment guidance: its tools are given a fresh copy of the submitted files on every attempt, it has no write tools, and nothing from the copy is attached to its Deliverable.

Graph (working["graph"]), for the Target architecture:

  1. graph_put adds items or replaces those with the same id, graph_remove removes by id, graph_read returns the graph. The submitted graph becomes the working graph.
  2. submit_deliverable attaches the working graph when no target-architecture.json is passed.
  3. render_tables writes the Elements, Relationships, Checks and not-applicable tables from the graph, and the engine appends them to the content on submission. The contract's sections are now Design rationale alone. This closes the duplicate output iteration 6 left: the architect no longer writes the graph twice.

Unmeasured: no evaluation has run, so the fall in requests, tokens and time is expected, not shown. The mechanism is what is tested.

Tests: tests/execution/test_working_copy.py (21), including an Execution in which the validator validates the submitted code with no files passed.