WO-0001 — v4 deployment spec (Edward-v4)

WO-0001 — v4 deployment spec (Edward-v4)

Order: WO-0001 (STM EA Agent) Date: 2026-05-31 Supersedes: the v1 output/deployment-manifest.md (March 2026 — v1.0.0, 16-skill, Confluence). That doc is kept for audit but is no longer the deployment of record. Decision: TFD-0029

What ships (v4)

The talent is the lean v4 Edward (production-lines/digital-talent/talents/agent-ea-v2/), whose back half is the proven production-lines/agent-ea/ engine. Not the v1 16-skill set.

Skill chain (8 stages)

# Stage Tool Kind
1–4 CAPTURE / REVUE / RÉPONSE / INTRANT /ea:exigences-* + human LLM + human
5 EXTRACT (+ seed D1, Model gate) /ea:leanix-catalog-extract → seed.mjs LLM + script
6 DATA export-datajs.mjs script
7 PUBLISH publish.mjs <manifest> (renderer-adapter) script
8 HANDOVER /ea:publish-jct + d1-export.mjs LLM + script

Retired vs v1: diagram-generate, livrable-assembler, commun-publication (Confluence) — absorbed by the engine. Publication = render(data, format), default html; Confluence is an off-by-default adapter, not shipped.

Output contract

Macroscope A-code page set (HTML) + live JCT/Cloudflare URL + d1-export handover bundle ({client}.sqlite + CSV for client self-run). Zero per-client HTML hand-editing (proven — see v4-parity-result.md).

Packaging inputs

  • Manifest: production-lines/agent-ea/pipeline/examples/stm.manifest.template.json (placeholders until a real STM DAE is processed through stages 5–6).
  • Templates/CSS: production-lines/agent-ea/templates/macroscope/.

Gates before handover (decision 2A)

Gate Status
Phase 4 parity (talent == engine, no hand-editing) ✅ PASSED (v4-parity-result.md)
OneDrive backup taken ✅ onedrive-backup-record.md
Phase 7 live redeploy (B's lean v2 → OneDrive copy, keep client DATA) ⏳ pending — separate backed-up session
Real STM DAE processed + STM manifest filled ⏳ pending STM data
Demo env re-validation (v2-revalidation-checklist.md) ⏳ pending

Remaining for a real STM handover

  1. Phase 7 — re-deploy the lean v2 skill set + CLAUDE.md onto OneDrive - STM\agent-ea, dropping retired v1 skills, keeping clients/ + demandes-ae/ DATA. Backup first.
  2. Process a real STM DAE through stages 5–6, fill stm.manifest.template.json, run publish.mjs.
  3. Run /deploy-checklist stm --run against the v4 talent.
  4. Work the v2-revalidation-checklist.md (models ✅ already; namespaced commands ✅; demo data + smoke test pending).
  5. Then the handover session (output/handover-agenda.md, already updated to v2) → signature → billing.