1. Getting Started & Architecture Philosophy
The Enterprise Architecture Standard Operating Procedure (SOP) is an engagement-adaptive operating model governing how business strategy is turned into resilient, evidence-backed operational outcomes without introducing rigid toolchain bloat.
Turning uncertainty into evidence-backed outcomesβnothing skipped, nothing handed back half-built:
| Tower # | Stage Name | Core Operational Question |
|---|---|---|
| 01 | Understand | What problem are we really solving, and what does success look like? |
| 02 | Architect | Design the solution and its boundaries before anything is built. |
| 03 | Define | Agree scope, what's in, what's out, and how we'll know it worked. |
| 04 | Deliver | Build the smallest useful version and prove that it works. |
| 05 | Handover | You and your team own it, fully documented, end to end. |
- Problem-First System Thinking: Put the why and what before the how. Technology choices serve business capabilities, never vice versa.
- Engagement Agnosticism & Scalability: Adapt governance depth and artifact formats dynamically to the specific customer engagement mandate.
- Technology Agnosticism: Evaluate traditional microservices, COTS/SaaS, and AI systems objectively based on ROI and business value.
- Strategic Vendor Decoupling: Establish provider-agnostic abstraction layers to prevent lock-in and preserve strategic optionality.
- Governance Through Enablement: Empower client teams with clear guardrails, reusable patterns, and auditable decision frameworks rather than acting as a rigid bottleneck.
Master SOP Classification: RESTRICTED / HIGHLY CONFIDENTIAL β Enterprise Architecture Operating Model.
Public Portfolio View: PUBLIC β Alexandre Franco Enterprise Architecture Portfolio.
2. The 5 Customer Engagement Stages
Establishes the strategic foundation by framing the core problem, defining Desired State intent, and auditing the Current State baseline.
Core Question: "What problem are we really solving, where is the customer today, what does the desired state look like, and what are the critical gaps?"
- Customer Strategy & Problem Definition: Deconstruct root business drivers and quantify success metrics.
- Current State Baseline Audit: Map existing applications (LeanIX/TOGAF inventory), data flows, and technical debt.
- Desired State Intent: Map required business capabilities, performance targets, and regulatory boundaries.
- Domain Diagnostic & Gap Analysis: Run the 10-Domain Architecture Requirements Framework (130+ questions).
Do not proceed to Stage 02 until business strategy, baseline audit findings, and capability gaps are validated by client executive and technical leadership.
Transforms Stage 01 gap analysis into a technology-agnostic, decoupled target architecture specification.
Core Question: "How do we structure target boundaries and technology choices so the customer's enterprise remains resilient, decoupled, and fit-for-purpose?"
- Options Evaluation: Score trade-offs across Microservices/API-first, Event-Driven, COTS/SaaS, and AI/Agentic options.
- C4 Architecture Modeling: Level 1 System Context, Level 2 Container, and Level 3 Component diagrams.
- Strategic Vendor Decoupling: Wrap databases (Repository interfaces), messaging (CloudEvents/Protobuf), and SaaS/AI calls behind provider-neutral wrappers.
All target cloud, SaaS, or AI model integrations must rely on explicit interface contracts. Direct coupling to proprietary SDKs requires an approved ADR.
Converts target designs into auditable decision records, risk priorities, and enablement governance guardrails.
Core Question: "How do we ensure safety, regulatory compliance, and auditable architectural decisions across the client organization?"
- Architecture Decision Records (ADRs): Document context, decisions, trade-offs, and consequences in
docs/adr/. - Risk & NFR Priority Matrix: Enforce strict P0 (Blocker), P1 (High SLA), P2 (Medium), and P3 (Nice to have) priorities.
- ARB Charter & AI Guardrails: Set review cadence, escalation paths, and dual-layer AI safety controls (probabilistic + deterministic validation).
Governance rules must enable delivery autonomy. Clear escalation paths and P0βP3 boundaries must be agreed upon by architects and delivery leads.
Translates target blueprints and governance into actionable transformation roadmaps and execution quality gates.
Core Question: "How do we translate target architecture into an executable roadmap and steer delivery teams to success?"
- 30/60/90 Transformation Roadmap: 30d Foundation & Spikes, 60d Core Capability Delivery, 90d Scaling & Hardening.
- Delivery Principles: Contract-first delivery, scope discipline, and vendor abstraction enforcement.
- Adaptive Quality Gates: Strategic compliance reviews for executive mandates; automated pipeline checks for repo-driven teams.
Delivery roadmaps must account for client team capability and operational limits. Never hand off a blueprint without a 30/60/90 roadmap.
Verifies business impact against baseline strategy, completes operational readiness reviews, and transfers self-sufficiency to the client.
Core Question: "How do we verify value realization, ensure operational readiness, and empower client ownership?"
- Value Realisation Audit: Benchmark actual operational performance against Stage 01 baseline metrics.
- Operational Readiness Review (ORR): Validate DR protocols, backup systems, security controls, and support team readiness.
- Empowered Handover: Deliver Executive Impact Brief, package architectural repository/runbooks, and train client teams.
Handover is complete only when client leadership confirms value realization and internal teams demonstrate full operational self-sufficiency.
3. Diagnostic & Assessment Accelerators
A workshop-driven diagnostic tool evaluating over 130 structural questions across 7 core EA principles to map Current State baselines and Desired State gaps in Stage 01:
| Domain | Question Count | Focus & Structural Coverage |
|---|---|---|
| 1. User Personas & Access | 12 Questions | Identity federation, access tiers, RBAC, user role requirements. |
| 2. Data Sources & Integration | 15 Questions | Data silos, data lineage, event streams, API contract boundaries. |
| 3. Reporting & Analytics | 15 Questions | Reporting gaps, executive analytics, operational dashboards. |
| 4. AI & Advanced Tech Strategy | 16 Questions | Justifying advanced automation vs traditional software patterns. |
| 5. Performance & Scalability | 12 Questions | Throughput bottlenecks, concurrency limits, latency SLAs. |
| 6. Security & Compliance | 15 Questions | Compliance gaps, encryption, PII masking, regulatory mandates. |
| 7. Observability & Operations | 15 Questions | Distributed tracing, centralized logging, operational alerting. |
| 8. Cost & Budget | 10 Questions | Baseline run costs, cloud infrastructure, licensing TCO envelopes. |
| 9. Extensibility & Maintainability | 12 Questions | Monolithic coupling vs modular abstractions and vendor decoupling. |
| 10. Deployment & Infrastructure | 15 Questions | Hosting constraints, multi-cloud, containerization, hybrid delivery. |
A quantitative evaluation matrix used in Stages 02 & 03 to score candidate technology options, SaaS platforms, and vendor solutions across weighted criteria:
- Functional Fit: Alignment with business strategy and target capability requirements.
- Technical & Architectural Quality: Scalability, determinism, modularity, and vendor decoupling.
- Security & NFR Compliance: Data encryption, RBAC, SLA performance, and regulatory compliance.
- Operational & TCO Impact: Implementation complexity, licensing overhead, and ongoing maintenance run cost.
Mandatory design policy governing AI-native and agentic deployments in Stage 02:
- Single Responsibility Principle: Each AI agent must have a distinct, well-defined operational scope.
- Autonomous Guardrails: Input/output boundary policies preventing unsafe tool execution or illegal state changes.
- Observability First: Complete logging of agent reasoning steps, tool calls, and prompt trajectories.
- Human-in-the-Loop (HITL): Explicit human approval checkpoints for high-risk actions.
- Context Injection (RAG): Grounding agent prompts in verified, domain-specific knowledge bases.
- Idempotency: Ensuring agentic tool actions can be safely retried without side effects.
| Priority Tier | Classification | Enforcement & Trade-off Policy |
|---|---|---|
| P0 | Critical / Blocker | Non-negotiable security, data privacy, compliance, or core reliability. Must be verified before production. |
| P1 | High Priority | Core SLA performance targets (e.g. sub-200ms latency), error handling, and primary tracing. |
| P2 | Medium Priority | Secondary performance optimizations, extended analytics logging, automated developer tooling. |
| P3 | Low Priority / Nice-to-Have | Cosmetic UI enhancements, experimental features, non-blocking optimizations. |
4. Engagement Archetypes & Transformation Roadmaps
To prevent over-engineering non-development mandates, the SOP scales deliverable depth across 4 engagement archetypes:
| Archetype | Duration | SOP Stages Covered | Primary Deliverables |
|---|---|---|---|
| Archetype A: Strategic EA Assessment | 2β4 Weeks | Stage 01 + Stage 04 (High-Level) | Executive Context Map, Baseline Audit, 10-Domain Gap Triage, 30/60/90 Transformation Roadmap. |
| Archetype B: Target Blueprint | 4β8 Weeks | Stages 01 & 02 | Desired State Vision, Vendor/Technology Options Scorecard, C4 Models, Target Architecture Specs. |
| Archetype C: Enterprise Governance Model | 6β12 Weeks | Stages 01, 02 & 03 | Governance Charter, ARB Operating Manual, ADR Catalog, NFR Matrix (P0βP3), Safety Guardrails. |
| Archetype D: Delivery Steering & Implementation | Ongoing / Sprints | Stages 01 through 05 | Hands-on Delivery Guidance, ADR-as-Code, Pipeline Quality Gates, SDD Specs, Operational Telemetry. |
- First 30 Days (Foundation & Quick Wins): Establish governance rules, validate initial architectural POCs/spikes, finalize API interface contracts, align delivery teams.
- First 60 Days (Core Capability Delivery): Execute Phase 1 core services, integrate CI/CD quality gates, conduct mid-point ARB architecture reviews.
- First 90 Days (Scaling & Hardening): Deliver end-to-end integration, execute non-functional load/security tests, transition operational runbooks to client teams.
Three target projections generated from the Master Enterprise Architecture SOP:
- Executive Projection: 1-Page Business Value Bridge & 30/60/90 Strategic Transformation Roadmap for C-suite sponsors.
- Agentic Co-Pilot Projection: Structured System Prompts (
agent-architect-prompt.md) and JSON schemas for AI pair-architects. - Delivery & Governance Projection: Governance charters, ARB checklists, NFR assessment matrices, and CI/CD quality gate workflows for engineering leads.
5. AI Augmented Architecture Workflows & Governance
| Pillar | Framework / Mechanism | Operational Impact & Capability |
|---|---|---|
| 1. Workflow Automation | EA4ALL.AI | Natural language strategy Q&A, automated requirement-to-C4 blueprint generation (Mermaid), multi-agent task routing. |
| 2. Continuous Governance | CAS (Continuous Architecture System) | Shift from post-project audits to dual-loop pre-commit prevention, automated terminology linters, and Git delta log extraction. |
| 3. Pattern Mining | Idea-to-Pattern | Mining evidence-backed design patterns directly from real-world implementation repositories and execution signals. |
| 4. Coding Agent Collaboration | Pair-Architect Orchestration | Governing AI coding agents (Antigravity, Gemini, Claude) via pair-architect personas (agent-architect-prompt.md) and deterministic safety guardrails. |
- 1. Prevent Loop (Pre-Commit & PR Gates): Intercepts structural or narrative changes before merge. Runs policy linters (
scripts/validate_governance.py) and enforces Specification-Driven Development (SDD) spec requirements inspecs/. - 2. Correct Loop (Actionable Guidance & Auto-Fix): Provides exact line-level error details and policy references instead of silent build failures, enabling automated correction scripts to fix formatting and terminology drift.
- 3. Git-Aware Delta Extraction: Continuously extracts architectural changes from commit history, linking pull requests back to originating ADRs and business intent.
| Traditional EA Practice | AI Augmented EA Practice | Value & Impact Delivered |
|---|---|---|
| Manual Documentation Overhead | Automated natural language synthesis & C4 generation | 10x faster artifact creation |
| Reactive Gatekeeping Audits | CAS Prevent-and-Correct SDLC & CI/CD pipeline checks | Zero architectural drift |
| Theoretical Textbook Frameworks | Evidence-based pattern mining from code repositories | Reusable, proven designs |
| Ivory-Tower Isolation | Democratized EA knowledge access via conversational AI | Cross-functional alignment |
| Ungoverned AI Coding Sprawl | Governance-aware coding agent collaboration | Safe, scalable AI delivery |
6. Local Validation Commands & Governance Resources
Click any command block to copy it directly to your clipboard:
Run Full Governance Validation (Build + Terminology Check):
Run Terminology Policy Linter Only:
Build MkDocs Site in Strict Mode (Fails on Broken Links / Nav):
Serve Documentation Site Locally:
Run Pytest Test Suite for Governance Scripts:
docs/sop/index.mdβ Master SOP Overview & 5 Stage Summarydocs/sop/01-discover-align.mdβ Stage 01: Discover & Aligndocs/sop/02-target-architecture.mdβ Stage 02: Target Architecture & Strategydocs/sop/03-governance-framework.mdβ Stage 03: Governance & Decision Frameworkdocs/sop/04-delivery-enablement.mdβ Stage 04: Delivery Enablement & Execution Steeringdocs/sop/05-value-realisation-handover.mdβ Stage 05: Value Realisation & Handoverdocs/sop/ai-augmented-architecture.mdβ AI Augmented Workflows & Governancedocs/sop/agent-architect-prompt.mdβ Agent Architect Pair Promptdocs/how-i-work.mdβ How I Work: The 5 Bridge Towers