Files

T

Jon Chery 0fea29cdbb docs(P12): plan-as-execute + verify (v1.2.2)

---ci---
project: acdl
phase: 12
milestone: v1.2
status: verify
verdict: VERIFIED
requirements:
  covered: [REQ-30]
---/ci---

Phase 12 plan-as-execute + verify. scripts/verify_phase12.sh green (22
assertions). All Wave 1 + Wave 2 tasks complete:
- T-12.1: run_spike_*.sh -> run_platform.sh (D-048, --plan-only flag)
- T-12.2: spike_runner_policy.json expanded (ECS + ECR + ELB + IAM + EC2)
- T-12.3: idempotency documented in bootstrap scripts
- T-12.4: P1-1 redacted (no live AWS key IDs in .ciagent/)
- T-12.5: P1-B fixed (PERSONAS.md platform/registry -> modules-ir/registry.json)
Subagent confirmed run_platform.sh --plan-only runs against real AWS, exit 0.
Ready to ship v1.2.2.

2026-07-21 21:01:51 +00:00

create_iam_user.py

docs(P12): plan-as-execute + verify (v1.2.2)

2026-07-21 21:01:51 +00:00

create_state_backend.py

docs(P12): plan-as-execute + verify (v1.2.2)

2026-07-21 21:01:51 +00:00

README.md

phase: 8, status: plan-as-execute, persona: platform-engineer+lead-developer, task: T-8.5..T-8.7

2026-07-21 19:00:08 +00:00

spike_runner_policy.json

docs(P12): plan-as-execute + verify (v1.2.2)

2026-07-21 21:01:51 +00:00

README.md

ACDL v1.1 Spike — AWS Bootstrap Runbook

Phase 08 bootstraps the AWS substrate for the v1.1 spike. It uses the root account credential for account 581513795199 exactly once, then closes D-034 by having the user manually rotate the root key afterward.

Spike scope (D-039): the spike uses a per-run-rotated IAM user key (acdl-spike-runner), NOT OIDC. Real OIDC federation is deferred to v1.2 (blocked on go-gitea/gitea#36988 — Gitea Actions does not support id-token: write). The acdl-spike-runner user + its key are deleted in v1.2 cleanup when the OIDC role lands.

Steps

Set the bootstrap root key in env (never commit, never echo):

export ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID="<root key>"
export ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY="<root secret>"
export AWS_DEFAULT_REGION="us-east-1"

Create the state backend (S3 bucket + DynamoDB outbox table):
```
python3 terraform/bootstrap/create_state_backend.py
```
Idempotent; writes terraform/bootstrap/.bootstrap_state.json marker.
Create the IAM user + scoped policy + initial key:
```
python3 terraform/bootstrap/create_iam_user.py
```
Prints ACDL_AWS_ACCESS_KEY_ID=<...> + ACDL_AWS_SECRET_ACCESS_KEY=<...> to stdout (capture if you want the initial key; rotate_spike_key.sh creates a fresh one anyway).
Rotate the spike key (creates a new key, deactivates+deletes old, writes the new key to gitignored .env.secrets):
```
bash scripts/rotate_spike_key.sh
```
Optionally uploads to Gitea Actions secrets if ACDL_GITEA_TOKEN is set.
Verify:
```
bash scripts/verify_phase08.sh
```
Asserts: caller identity is acdl-spike-runner (not root); S3 bucket + DynamoDB table + IAM user + scoped policy all exist; .env.secrets + .bootstrap_state.json are gitignored.
MANUAL — D-034 closure: rotate/deactivate the root key in the AWS IAM console (the user does this, not the script). The bootstrap root key has now served its one-shot purpose; the spike uses the rotated acdl-spike-runner key for Phases 09-10.

What the spike uses for Phases 09-10

State backend: S3 bucket acdl-tfstate-581513795199-us-east-1 + DynamoDB table acdl-outbox (one table for both lock + outbox, D-P08-1).
Auth: the rotated acdl-spike-runner key in .env.secrets (gitignored, chmod 600). Re-rotate after each spike run via rotate_spike_key.sh (D-039).

Spike scope vs v1.2 boundary

Concern	Spike (Phase 08)	v1.2
AWS auth	per-run-rotated long-lived key (D-039 waiver)	real OIDC federation (go-gitea/gitea#36988)
IAM	minimal user `acdl-spike-runner` + scoped policy	OIDC role + trust policy (no user, no key)
State backend	S3 + DynamoDB single-region (us-east-1)	multi-region
Secret storage	gitignored `.env.secrets` + optional Gitea secret	Gitea OIDC-issued web-identity token (no secret)