What This Page Is
A compact, opinionated cross-section of the Prismatic Platform architecture from the platform-architect perspective — what's deployed where, why, and which doctrine pillar enforces each layer. For deep dives, follow the see-also links.
Layered View
The platform splits cleanly into five tiers, each with its own runtime, doctrine surface, and failure boundary:
1. Infrastructure tier (Elixir/OTP umbrella)
- 92 umbrella apps under
apps/— per-domain isolation, independent compile units, dedicated supervision trees. - BEAM VM with process isolation + per-process garbage collection — no global stop-the-world pauses, soft-real-time guarantees.
- Storage adapters: PostgreSQL (transactional), KuzuDB (graph queries), Meilisearch (full-text), ETS (in-process cache), Cachex (cross-process L2). All exposed via Adapter Pattern.
- Supervision: Three-Nested-Loops (3NL) — outer (mission), middle (epoch), inner (cycle) — each with own state, telemetry, termination criteria.
2. Decision tier (NABLA Infinity)
- NABLA Infinity — seven-axiom epistemic engine: Signal Plurality, Contradiction Preservation, Provenance Mandatory, ...
- Trinity Gate — every analytic claim must survive structural + logical + formal-verification checks before downstream consumption.
- Epistemic Pipeline — typed claim flow with provenance, falsification gates, and uncertainty propagation.
- Quality DNA + autoevolve — tracks experimental quality across sessions; identifies improvement opportunities in graduated code.
3. Web tier (Zola + Phoenix)
- Zola promo site at
sites/promo/— static content (4400+ pages: agents catalog, glossary, OSINT toolbox docs, Kompendium of manipulation patterns), deployed to GitHub Pages athttps://prismatic-reality-com.github.io/prismatic-promo/via the.github/workflows/deploy-promo.ymlworkflow. - Phoenix LiveView app at
apps/prismatic_web/(port 4000 / fly.dev production) — interactive UI: real-time dashboards, OSINT toolbox, DD case management, decision engine, investigation reports. - Cross-product linking: Zola pages reference Phoenix routes via the
{{ cross_link(path=, text=) }}shortcode, which renders tohttps://prismatic-prod.fly.dev/<path>when[extra] deploy_target="ghpages"and to a relative/<path>whendeploy_target="fly". Single source of truth insites/promo/config.toml. - API: REST (
prismatic_apiumbrella app, port 4004 — auto-introspecting, 218+ endpoints discovered), MCP, GraphQL.
4. Agent tier (AIAD)
- 552 specialized agents registered via the AIAD standard, organized into 16 domains (Quality, OSINT, Security, Development, Strategic, M&A, Integration, Evolution, Mycelial, Infrastructure, Performance, Documentation, Crisis, ...).
- 228 commands as agent entry points (
/archer-supreme,/orchestrate,/investigate,/fix, ...). - Color teams (red, blue, purple, green, ... ) for adversarial simulation, defensive evidence-building, and findings closure.
- Authority levels: L1 workers, L2 specialists, L3 tactical, L4 operational, SUPREME, COSMIC.
5. Doctrine tier (19 pillars)
Compile-time, pre-commit, and CI enforcement of platform invariants:
| Pillar | Surface | Enforcement |
|---|---|---|
| 3NL | Three-nested-loops architecture | architectural |
| NMND | No Mercy, No Doubts | pre-commit BLOCK |
| NWB | No Way Back (forward-only) | CI |
| FLLM | Flowbite LLM CSS Hygiene | CI advisory |
| M5M | Max 5 Minutes | CI advisory |
| NCLB | No Claim Left Behind | CI BLOCK |
| TACH | Total Assurance Comprehensive Hardened | pre-commit BLOCK |
| ZERO | Zero Error Runtime Operations | pre-commit BLOCK |
| PERF | Performance Engineering Runtime Fence | pre-commit BLOCK |
| SEAL | Security Enforcement Absolute Lock | pre-commit BLOCK |
| DEPS | Dependency Engineering Protection | pre-commit BLOCK |
| DOCS | Documentation Standard | CI |
| OTEL | Observability Telemetry | CI |
| GITL | GitLab Integration & Traceability | CI |
| KNOW | Knowledge Coverage | CI advisory |
| RDME | README Required In Every App | pre-commit BLOCK |
| NLLB | No Link Left Behind | pre-commit (Check 7) + CI |
| HYGIENE | Repository Hygiene | pre-commit BLOCK |
| CZE | Czech-Language Excellence | bash hook (Level 3 STRICT for P0 docs) |
Cross-Cutting Concerns
- Telemetry: every interesting event flows through
Telemetry.execute/3with structured metadata; subscribers feed real-time dashboards + audit trails. - Provenance: every analytic claim carries provenance (source, transformation chain, confidence) — enforced by the NABLA Infinity Provenance Mandatory axiom.
- Health-aware orchestration: agents check
Prismatic.OrchestrationHealth.summary_line()before launching missions; system errors trigger stabilization-first behavior. - Reproducibility: dynamic stats (
mix prismatic.stats.validate) prevent hardcoded counts from drifting; commit-time pillar validation prevents regression.
Failure Boundaries
The platform is designed to fail at well-defined boundaries:
- Process boundary: a crashing GenServer is restarted by its supervisor; sibling processes unaffected.
- App boundary: a misbehaving umbrella app can be hot-restarted without bringing down others.
- Doctrine boundary: a code change that would regress an enforced pillar is rejected at pre-commit or CI — never lands.
- Epistemic boundary: a claim that can't pass Trinity Gate is held back from downstream consumers, not silently propagated.
See Also
- Architecture deep dives — adapter architecture, event sourcing, Phoenix LiveView, NABLA framework, PostgreSQL+KuzuDB
- Capabilities — what the platform can do (OSINT, EASM, M&A intelligence, color teams, autonomous self-healing)
- Teams — color team specifications and operational doctrine
- About — Prismatic for Architects — extended architecture narrative for senior architects
Status: This page is a structurally complete architecture overview created during the 2026-05-03 NLLB content-completion sweep, replacing the prior 50-references-deep
/about/architectureplaceholder. Living document — full sections on each tier are tracked in the architecture section.