Institutional Applications Map

Architecture Locked

← All Architecture documents

Institutional Applications Map v1.0

Status: Architecture Locked · 2026-08-09

Which application chapters sit on the Foundation — and under which rules. Not a product backlog. Not permission to implement.

Purpose

The Institutional Architecture Map (whole-institution How?) explains of what the institution is built.

This map answers: which Institutional Applications Era chapters are architecturally real, how they connect, and what must not be mixed when code begins.

Status board

Chapter Architecture Implementation
Notification Infrastructure LOCKED CLOSED
Institutional Event Catalog LOCKED — (vocabulary)
Business Relationship Infrastructure LOCKED CLOSED
Search / Digital Identity / Marketing — NOT OPENED 
Event Catalog              — LOCKED
Notification               — LOCKED (impl closed)
BRI Philosophy · Domain · Baseline — LOCKED
BRI Implementation         — CLOSED

Dependencies

Communication Infrastructure
        │
        ├─► Notification (N0 · Delivery)
        │
        └─► Business Relationship (B0–B3 · Business Record)
                 │
                 └─► Event Catalog (shared fact names)

Marketplace discovers. Business Records manage.

Standing rules (carry forward)

  • Attach speech to Context — no parallel relationship models
  • Event = fact; notification = delivery decision
  • No retroactive rename of accepted event types
  • One on-NFB relationship → one canonical Business Record
  • Evidence supports; never judges truth or legal outcome

Public reading cycle

Cursor writes → deploy public Architecture pages → read the real document on production → review → lock or amend. Internal docs/ govern implementation.

Related