Analyze ESM Artifacts

Objective

Extract capability requirements per architectural domain from the ESM output artifacts (user journey, screen flows, .feature files, IA guidelines). This structured requirements list feeds all subsequent DTA activities (DTA-02 through DTA-17, and Activities 200/201).

Process

1. Read User Journey

• Extract domain entities (e.g., User, Playbook, Workflow, Activity, Skill)
• Identify interaction patterns (CRUD, search, import/export, real-time updates)
• Note personas and roles that imply auth/authorization requirements
• Flag integration points (external systems, APIs, data sources)

2. Read Screen Flows

• Identify UI complexity per screen type:
• Simple: static content, read-only views
• Moderate: forms, tables, filters, pagination
• Complex: graphs, drag-and-drop, real-time, rich text editors
• Count screen types to estimate frontend effort
• Note navigation patterns (breadcrumbs, tabs, modals, wizards)

3. Read Feature Files (.feature)

• Extract required capabilities from scenario steps:
• CRUD operations per entity
• Search and filter requirements
• Authentication and authorization scenarios
• Error handling and edge cases
• Data validation rules
• Map scenarios to capability domains (GUI_FORM, API_CRUD, AUTH_SESSION, etc.)

4. Read IA Guidelines

• Extract design system requirements (component library, theming)
• Note accessibility requirements (ARIA, keyboard navigation)
• Identify responsive/multi-device needs

5. Compile Requirements per Domain

Produce a structured list mapping ESM findings to the 16 core architectural domains plus the 2 optional ones (AI Agent Architecture, MCP Architecture):

Domain: Application Blocks (DTA-02)
  - 5 bounded contexts identified: Auth, Methodology, Planning, MCP, Web UI
  - Dependency: Methodology → Planning (planning reads methodology)

Domain: Integration & API Design (DTA-03)
  - MCP stdio interface required (read-only)
  - Web UI HTTP interface required (full CRUD)
  - No external 3rd party integrations identified

Domain: Code Organization (DTA-04)
  - Monorepo structure implied (single Django project)
  - 3 layers visible: models, services, views

Domain: Data Architecture (DTA-05)
  - 6 entities with relationships (graph-like)
  - Version tracking required
  - Import/export functionality needed

... (continue for all 16 domains, plus AI Agent Architecture and MCP Architecture if applicable)

This structured requirements document is the single shared input every domain activity below reads. Nothing in Step 6 depends on any domain activity's own decision — that's what makes the fan-out below safe.

6. Dispatch Domain Decision Workers (parallel)

Apply rule do-fan-out-independent-work. The item list is every remaining DTA domain activity: Activities 43 through 58 (Application Blocks through Documentation Strategy), plus Activity 201 (Define MCP Architecture) and Activity 200 (Define AI Agent Architecture) when applicable to this project.

• Footprint, per item: reads only the Step 5 requirements document (and scans Playbook Skills, as each domain activity's own guidance already directs). Writes only its own decision block for inclusion in SAO.md. No domain activity's guidance references another domain's decision — confirmed by direct reading of Application Blocks (43), Infrastructure (50), CI/CD Pipeline (51), and Security (55) — so the conflict map here is empty by construction: dispatch all of them in one wave.
• Do not wait for one domain activity to finish before starting the next. There is no ordering requirement between them.
• Convergence: Activity 59 (Write SAO.md) is the single convergence point. It now includes an explicit cross-domain consistency check (see that activity's own guidance) — do not treat any individual domain worker's output as final until that check has run, since a domain decision made in isolation (e.g. a compute model choice) can constrain a decision another worker made independently (e.g. a CI/CD deploy target, or a blue/green mechanism).
• Collect every domain worker's decision block and skill-coverage report before proceeding to Activity 59.

Deliverables

• ✅ Domain entities extracted from user journey
• ✅ UI complexity assessed from screen flows
• ✅ Capability domains mapped from .feature files
• ✅ Structured requirements list produced for all 16 core architectural domains (and AI Agent / MCP Architecture, if applicable)
• ✅ Domain decision workers dispatched in parallel for Activities 43-58 and, if applicable, 200/201
• ✅ Ready to proceed to Activity 59 (Write SAO.md) once all domain workers report back

Inputs

Read these before starting this activity. They are produced earlier in the playbook and are authoritative — raise a drift event instead of deviating.

• User Journey (Document, Required) — produced by Define User Journey (#36).
• IA Guidelines (Document, Required) — produced by Define Information Architecture (#37).