enterprise-architecture

The manifest-driven monorepo of a small executive protection / protective intelligence firm: five domains and three cross-cutting elements, every artifact addressable by an immutable identifier, cross-domain dependencies typed as artifact seams, coherence machine-verified.

Map

IDNamePrefixWhat
D-01intelligenceOSINT-Sellable intelligence product portfolio (65 cells)
D-02protective-operationsEP-The EP program: advance, movement, covert protection, detail ops (32 cells)
D-03systems-infrastructureSYS-The firm’s own kit: C2/TOC, comms, platforms, monitoring (12 cells)
D-04business-operationsBIZ-Engagement lifecycle, vendor pipeline, logistics, cost model (13 cells)
D-05agentic-operationsAGT-Claude Code automation as system elements (10 cells)
CC-01region-packagesRGN-Per-AO packages; the regional repeatability mechanism
CC-02standards-Type standards, doctrine, classification
CC-03methodology-Delivery methodology (quartet, gated builds, reliability doctrine)

Reading path

PROJECT.md (this file) CLAUDE.md (doctrine and mechanics) CONVENTIONS.md (unenforced patterns) docs/superpowers/specs/2026-07-03-enterprise-architecture-design.md (the design) a domain architecture.md end to end (d01 and d02 are canonical).

Commands

uv run mbse new —domain —title ”…” —capability uv run mbse build (regenerate catalogs/graph/seams; idempotent) uv run mbse verify (coherence gate; nonzero exit on any defect) uv run pytest (engine tests)

Roadmap

  1. Operational gap closure (field reporting/TAM intake, K&R response, training/readiness, protective medicine, TSCM brokerage, insider-threat rewiring, AAR seam) 2. Approval burn-down (D-01/D-02/D-04 drafted cells through independent review with operator validation) 3. Mexico region package (RGN-003 full build) 4. Shape-E collection maps for EP-001..018
  2. Protective-intel stream v2 (SYS-008) 6. D-03 GAP hardware grounding (laptop, growth-tier rows)