Deferred from M1 — ECS prod cutover (re-activated)

2026-06-06 framing note: This doc was originally a generic "deferred work" tracker, but its sole live entry is the re-activated ECS / Fargate agent deployment work, now tracked as P0 via #701. For broader infrastructure status see mvp-launch-checklist.md §Infrastructure & Hosting. Other M1 deferrals, if any are added in the future, should follow the same shape below.

Tracks work that was scoped into M1 PRDs but explicitly deferred per post-PRD decisions. Each item lists the originating PRD, the deferral decision, and the in-repo location of any inert reference assets that were retained.

Re-activating any of these items should:

1. Update the PRD entry from DEFERRED back to its previous state (or open a new M2/M3 PRD).
2. Restore CI gates (if: false → removed) on any associated workflows.
3. Move inert assets out of their *.deferred/ location back into the primary path expected by the workflow / docs.

ECS / Fargate agent deployment — still deferred from M1 (re-activation 2026-05-25 announced but not executed)

Originating PRD: agent/tasks/prd-humanwork-agent-m1-closure.md US-021 through US-026.

Original deferral: Paul, 2026-05-06 — M1 ships on Railway only.

Status (last reviewed 2026-06-03): Effectively still deferred. On 2026-05-25 this item was announced as promoted to P0 launch-blocker (#701) on the rationale "Railway is fine for vibe-coded development; it is not production-grade for a paying customer." However, none of the re-enable checklist steps below were executed, and the workflow gates were in fact re-applied on 2026-05-26 by commit 879390207 (fix(ci): gate deferred ECR/ECS workflows with if: false). The doc previously said "RE-ACTIVATED 2026-05-25" but the repo state shows the deferral is still in force. Either the activation needs to drive the checklist or this item should be marked deferred again until #701 actually starts moving. As of 2026-06-03, no follow-up activity on #701.

Tracking issue: humanity-org/humanwork#701 (P0 if active, but see status above).

Re-enable checklist (none of these have been executed; complete them to make re-activation real):

• Restore CI gates: remove if: false from .github/workflows/agent-ecr-push.yml (currently still gated, line 62).
• Restore .github/workflows/agent-ecs-deploy.yml to a push-triggered (or workflow_run) gate once dev/staging promotion shape is finalized. Currently workflow_dispatch-only + if: false on the job.
• Move agent/deploy/ecs.deferred/ → agent/deploy/ecs/ and verify Terraform / IaC references resolve. Currently still under ecs.deferred/.
• Update agent/deploy/README.md deferral banners to "ACTIVE — see #701" (currently still display **DEFERRED from M1 (issue #238)**).
• Reactivate PRD US-021–US-026 in agent/tasks/prd-humanwork-agent-m1-closure.md (currently still **DEFERRED (M2)**).
• Verify AWS_ECR_ROLE_ARN + AWS_ACCOUNT_ID secrets are configured in the GH org/repo.

Note on related ECS infra: A separate ECS pipeline shipped for the RAG service (commits 9a7a6980b, cc720e5d6, 68e371325 — issues #1521/#1527/#1541, workflow rag-deploy.yml). That proves ECS infra exists in the repo; the agent's own ECS path remains gated off and is what this entry tracks.

---

Original-deferral notes (kept for historical context):

What changed:

• agent/deploy/ecs/ → agent/deploy/ecs.deferred/ (inert reference, no CI consumer expected to remain).
• PRD US-021–US-026 status set to DEFERRED (M2) with rationale inline.
• agent/deploy/README.md sections covering US-021 through US-026 carry deferral banners.

Workflow gates:

• .github/workflows/agent-ecr-push.yml triggers on every push to main and currently fails fast on missing AWS_ECR_ROLE_ARN secret. Gated if: false on 2026-05-26 (commit 879390207).
• .github/workflows/agent-ecs-deploy.yml is workflow_dispatch-only, also gated if: false on the job.

What remains in-place:

• Railway dev preview parity (US-027 — active, on M1's critical path).
• agent/deploy/docker-compose.per-org.yml (active, used for local dogfood Org bring-up).

Re-enable checklist (use the same checklist as above when #701 actually moves):