01. Master Blueprint: System Architecture & Entry Point
Status: Active / Golden (Entry Point) Version: 1.1 (Reconciled Jan 2026)
"The definitive entry point for the Singular Dream platform's architecture. Use this as your map before diving into the specialized Domain and Capability manuals."
1. System Metaphor: Layered Service Architecture
The platform is organized into a Forensic Service Architecture. Dependencies strictly flow downward. This ensures that core infrastructure (Foundation) is never polluted by business logic (Modules), and that generic horizontal logic (Unified) remains reusable.
🏛️ Layer 1: Business Partitions (The Verticals)
_Source: packages/modules/_*
These are the business domains containing logic unique to community operations.
- Reference: See BLP-DOM-010_COMMUNITY_DOMAIN.md, BLP-DOM-020_OPERATIONS_DOMAIN.md, and BLP-DOM-030_FINANCE_DOMAIN.md.
🌉 Layer 2: Unified Core (The Horizontals)
_Source: packages/modules/unified/_*
Generic capabilities that integrate different Layer 1 processes (e.g., Search, Workflow, Audit).
- Reference: See BLP-DOM-040_UNIFIED_SERVICES.md.
🧱 Layer 3: Foundation (The Infrastructure)
_Source: packages/foundation/_*
Agnostic plumbing and technical abstraction (Database, Auth, Storage).
- Reference: See BLP-SYS-005_INFRASTRUCTURE_OPS.md.
2. Capability Model: The "Big Four"
We group technical modules into four primary commercial value pillars.
-
Reference: For the full, audited functional matrix of all 200+ features, see BLP-PRD-001_PRODUCT_CAPABILITIES.md.
-
Property Registry: The "Digital Twin" and Single Source of Truth for assets.
- Digital Democracy: Remote, weighted voting and owner oversight.
- Operations Machine: Converting decisions into physical service execution.
- Financial Engine: Automated dues, assessments, and double-entry ledger.
3. The Identity Model: Contextual Persona
We do not use flat "Roles." We use a Context-Aware Persona Model. A user is defined by their Relationship to a physical asset or legal entity in the Directory.
- Hat (Persona): Who am I acting as? (Owner, Board Member, Vendor).
- Scope: What is my radius? (My Unit vs. The Building).
- Asset: What is the target? (Unit 102, Main Pump).
Standard 60 (The Pivot Shell): The UI automatically provides the correct forensic lens (People, Assets, Services) for the current context.
- Reference: See BLP-PRC-013_PERSONA_UX_JOURNEYS.md for the Persona list and STD-SEC-010_AUTHZ_MODEL.md for the technical implementation of Context.
4. Operational Strategy
- Roadmap: See BLP-SYS-004_ACTIVE_ROADMAP.md for current execution status.
- Planning Pattern: See STD-ARC-006_Construction_Hierarchy.md for the Building Order methodology.
- Agentic Velocity: See BLP-SYS-044_AGENTIC_FORCE_VELOCITY.md for Double-Axis Scaling and "The Beast" benchmarks.
- Standards: See STD-ARC-001_Blueprint_Standards.md for the "Toxic Import" rule and other mandatory coding patterns.
- Philosophy: See HIST-SYS-010_AGENTIC_OPERATIONS.md for our Agentic Development Protocol and Capability-Driven Design values.
- Technology Stack: See BLP-SYS-042_GOLDEN_STACK.md for our component selection hierarchy and library preferences.
- Compliance: See STD-CMP-001_Compliance.md for Financial/GAAP and Legal alignment.
Version History
| Version | Date | Author | Change |
|---|---|---|---|
| 0.1.0 | 2026-01-26 | Antigravity | Initial Audit & Metadata Injection |