Files
gcp_solution_architecture_a…/.agents/plans/iter-07-change-requests/steps/step-8.md
Jonathan Boniface f1f6f1b83a feat: load the env file at start-up, trim schema lookups, remove legacy samples
Start-up
- Export the env file's variables for other libraries (the Cloud provider's
  client) into the process environment; the app's own settings and secrets
  are never exported, and a value already in the environment wins.
- Use GOOGLE_GENAI_USE_ENTERPRISE in place of the deprecated
  GOOGLE_GENAI_USE_VERTEXAI.

Target architect
- Look each distinct resource type up once instead of once per setting: in
  the run of 2026-10-07 it made 39 lookups for 8 types and exhausted its
  budget. terraform_schema's find takes several names; budget 30 to 45.
- A cut-off schema outline says so.

Removed, as leftovers of the original pipeline that nothing read
- terraform/ (no longer passed terraform validate), scripts/validate.sh,
  tests/test_package.py and the CI steps that ran on them.
- The sample outputs under docs/ and requirements.yaml.
- CI now pins Terraform 1.14.3, as the container image does.

Plans record the case 01 run: completed at 100% in 18 minutes with no
Revision, against 60 minutes and warnings before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 20:06:58 +01:00

2.8 KiB

Step 8 — Implementation Detail

Done early, on the owner's instruction of 2026-10-07 ("please remove legacy-baseline"). That instruction replaced the gate in DETAIL.md, which had held removal until iterations 6 and 7 met their acceptance criteria. Neither has: no evaluation run has been made on iteration 6, and iteration 7 is not built.

  1. Deleted deliverables/cases/legacy-baseline/: the 68 old Executions, their intent/ history, and the shared as-is/, target/, validation/ and guides/ folders. deliverables/cases/ is now empty until an Execution completes.
  2. Deleted scripts/validate_artifacts.py and tests/test_artifacts.py, which only checked that case's samples. tests/test_package.py keeps its one test of terraform/terraform.tfvars.example.
  3. Removed the artefact-validation step from README.md and VALIDATION.md.

Five of the Execution folders were owned by a rootless-podman user id (110000), left by a container run on 2026-09-02 with the folder mounted. They were removed with podman unshare rm.

Not committed first, against the guardrail in DETAIL.md: the owner did not ask for a commit. The tracked files are recoverable from commit 7ee49ab at their earlier paths (deliverables/as-is/, deliverables/target/, deliverables/validation/, deliverables/guides/, deliverables/executions/, scripts/validate_artifacts.py, tests/test_artifacts.py). The generated intent/ files for that case were never committed and are gone.

Left in place, because the instruction named only legacy-baseline: the same pipeline's other samples, terraform/ at the repository root, docs/requirements.md, docs/architecture.md, docs/source-architecture.md, docs/validation-evidence.md, docs/validation-results.json, docs/publication-verification.md, requirements.yaml, and scripts/validate.sh, which runs Terraform checks on that root terraform/.

Removed later on 2026-10-07, on the owner's instruction to clean up the root terraform/ if it was no longer needed: terraform/ and scripts/validate.sh, with the three CI steps that ran Terraform on that directory. Nothing read it, and it no longer passed terraform validate (duplicate required_providers, outputs naming resources that do not exist). Recoverable from commit 5bb22d9. The docs/ samples and requirements.yaml listed above were then removed too, on the owner's instruction the same day: docs/requirements.md, docs/requirements-spec.md, docs/architecture.md, docs/source-architecture.md, docs/validation-evidence.md, docs/validation-results.json, docs/publication-verification.md and requirements.yaml. Nothing read them; each kind of output they sampled is now produced per Execution by a role in agents/. Their sample workloads were not added as evaluation cases.