Skip to content

Domain Strategy: Unified Core

Domain: Unified Mandate: The Central Nervous System Package Scope: packages/modules/unified/* Status: ACTIVE

1. Executive Summary

The Unified Core is the "Central Nervous System" of the platform. It provides the cross-cutting capabilities required by all other domains (Finance, Community, Operations). It does not contain "Business Logic" per se, but rather the Physics of the digital environment.

1.1 The Trifold Role

  • Intent: To provide a seamless, invisible, and secure substrate for application logic.
  • State: Currently distributed across signals, identity, audit, and communications packages.
  • Evolution: Moving toward a strictly event-driven, policy-aware kernel.

2. Functional Sub-Domains

Sub-Domain Prefix Description Key Services
Identity (ID) UNI-ID "The Who". Analysis of Forensics, Access, and Personas. IdentityService, RBAC
Signals (SIG) UNI-SIG "The Pulse". Event Bus, Telemetry, and Async Processing. SignalService, EventBus
Communications (COM) UNI-COM "The Voice". Omni-channel messaging and routing. NotificationService, VoiceRouter
Audit (AUD) UNI-AUD "The Memory". Immutable logging and forensic traceability. AuditService, BaseRepository
Knowledge (KNO) UNI-KNO "The Brain". Library and Search. LibraryService, SearchEngine
Vault (VLT) UNI-VLT "The Safe". Generational Secure Document Storage. VaultService
Navigation (NAV) UNI-NAV "The Map". Data-driven UI routing and menus. NavigationService

3. The Separation of Concerns (Unified vs Foundation)

The Unified Domain stands on the shoulders of the Foundation Domain (packages/foundation).

Layer Focus Question Example
Foundation Infrastructure "The How" Auth: Knows how to identify a user via JWT. (No Rules).
Unified Business Logic "The Why" RBAC: Knows why a user has the Owner role (Persona Policy).

Principle: Foundation knows the mechanics. Unified knows the Policy. Unified wraps Foundation to inject "Sovereignty".

4. Architectural Patterns

3.1 The Signal Bus

All interactions between Domains MUST occur via the SignalService. Direct coupling (importing Services) is permitted only for "sisters" within the same Domain. Cross-Domain calls should be async triggers where possible.

3.2 The Policy Substrate

The Unified Core is the primary consumer of the Policy Governance Model.

  • Identity verifies Who can act.
  • Audit records What happened.
  • Communications decides Where to send output based on Policy.

4. Roadmap (Evolution)

  • [ ] Consolidation: Formalize unified packages under a single Blueprint.
  • [ ] Policy Awareness: Ensure Signals and Comms respect Sovereign Rules (Done for Comms).
  • [ ] Deep Telemetry: Expand Signals to capture "Business Health" (Finance signals).

Changelog

Date Author Description
2026-01-24 Antigravity Initial Creation