agent-ea v2 — Edward (Enterprise Architect)

agent-ea v2 — Edward (Enterprise Architect)

Status: Build in progress (REQ-CONS-008, started 2026-05-14) Service line: Enterprise Architecture Predecessor: C:/Projects/agent-ea (v1, frozen — Confluence/drawio output) ⚙️ Comment ça marche: how-it-works.html — the v4 8-stage chain (/ea-hlsd), interactive (clic un nœud → détail ; Mode admin → code source)

What this is

Source-of-truth dev location for agent-ea v2 ("Edward"), the digital talent that delivers the EA service line.

v2 is a forward port of the v1 /ea-hlsd skill chain with two structural changes:

  1. Output is the Macroscope page set on JCT, not Confluence. v1 produced out/confluence-{slug}.md for paste-into-Confluence. v2 produces the Macroscope A100–A270 page set plus a D1 handover bundle and self-publishes to {client}.jacksoncreektech.ca.
  2. Catalog is a factory skill; data + publish are deterministic engine scripts. v1 had its own ea-qualite-validation + ea-commun-diagramme. v2 delegates extraction to /ea:leanix-catalog-extract (LeanIX v4 English schema, seeded into D1), then runs the production-lines/agent-ea/ engine scripts export-datajs.mjs (D1 → data.js) and publish.mjs (Macroscope pages) — deterministic Node, no model.

Layout

agent-ea-v2/
├── README.md                  ← this file
├── CLAUDE.md                  ← agent configuration (workspace rules, conventions)
├── role.md                    ← what Edward does (factory-level role spec)
├── agent.md                   ← Claude Code agent definition
├── MODEL-CONFIG.md            ← model IDs + sweep script
├── .claude/
│   └── commands/
│       ├── ea-hlsd.md                  ← orchestrator (v2)
│       ├── ea-exigences-note.md        ← capture
│       ├── ea-exigences-note-revue.md  ← Q&R revue
│       ├── ea-exigences-intrant.md     ← intake doc assembly
│       ├── ea-publish-jct.md           ← NEW (replaces ea-commun-publication)
│       └── templates/                  ← drawio gabarits retained for look-feel
│   (stages 6 DATA + 7 PUBLISH are deterministic Node scripts in
│    production-lines/agent-ea/pipeline/, not skills — see that engine's README)
├── content-in/
│   └── (FR conventions, validation references)
└── deployment/
    └── (packaging artifacts when shipping to a client)

v1 → v2 chain mapping

Stage v1 skill v2 disposition
1. CAPTURE ea-exigences-note Port (FR canadien, minor cleanup)
2. REVUE ea-exigences-note-revue Port (interview Q&R extraction unchanged)
3. RÉPONSE (human) (human)
4. INTRANT ea-exigences-intrant Port, align with v4 schema (English-ready columns)
5. EXTRACT ea-qualite-validation + ea-archi-catalogue + ea-archi-extraction Replace with /ea:leanix-catalog-extract (factory skill, v4) → node seed.mjs seeds D1
6. DATA ea-commun-diagramme Replace with node export-datajs.mjs (deterministic Node script, D1 → data.js)
7. PUBLISH ea-changement-solution Replace with node publish.mjs (deterministic Node script, Macroscope A100–A270 pages)
8. HANDOVER ea-commun-publication Rewrite as ea-publish-jct (self-publish to JCT, JSM comment-back) + node d1-export.mjs (handover bundle)
Optional 9-11 ea-changement-couts, ea-changement-feuilleroute, ea-qualite-cra Defer (port later)
Alternative ea-archi-orientation Port later (Macroscope option comparison)

See process/v2-port-plan.md in REQ-CONS-008 for full detail.

Pipeline (v2)

1. CAPTURE          /ea2:exigences-note          → notes/note_{slug}_*.md
2. REVUE            /ea2:exigences-note-revue    → notes/note-{slug}-q&r_*.md
3. RÉPONSE          (human)                       → Q&R filled
4. INTRANT          /ea2:exigences-intrant       → intrants/intrant-{slug}_*.md
5. EXTRACT          /ea:leanix-catalog-extract   → {slug}-objects.csv + {slug}-relations.csv (v4) → node seed.mjs (D1)
6. DATA             node export-datajs.mjs        → data.js (D1 → data.js, deterministic)
7. PUBLISH          node publish.mjs              → Macroscope A100–A270 page set (deterministic)
8. HANDOVER         /ea2:publish-jct + node d1-export.mjs → {client}.jacksoncreektech.ca + {client}.sqlite/CSV bundle

Orchestrator: /ea2:hlsd {slug} runs all 8 stages with state detection, quality gates, and resume-from-last-completed.

Open

  • Skill namespace /ea2: vs /ea: — TBD (see decision in process/v2-port-plan.md)
  • agent-ea v2 regen state — once Edward (the agent definition) is regenerated, this folder is the canonical source

See also

  • REQ-CONS-008 — Edward self-publishing
  • REQ-CONS-010 — JSM ↔ EA integration
  • company/services/enterprise-architecture.md — service line spec
  • TFD-017 — JCT portail architecture