What This Page Is
ProtoSynthesis is a layered architecture system. This page provides a navigable overview of how the system is structured and how its major components relate to one another.
It is not a technical specification. It is a structural map designed to help understand how the architecture is organised.
Core Architectural Layers
1. Root Layer (Identity)
Defines what ProtoSynthesis is, what it is not, and the boundaries of the system. This layer establishes system legitimacy and scope.
2. G01DN Layer (Structural Governance)
Defines how the system is structured internally, including how authority, inheritance, and relationships between layers operate.
3. Constitutional Layer (Existence Rules)
Defines what is permitted to exist within the architecture. This includes structural constraints and system validity conditions.
4. Protocol Layer (Interaction Rules)
Defines how components within the system interact, relate, and resolve structural relationships.
5. Standards Layer (Consistency Rules)
Defines naming conventions, formatting rules, compliance expectations, and structural consistency requirements.
6. Reference Layer (Public Representation)
Defines how the system is presented, documented, and understood externally. This is the human-facing expression of the architecture.
How the System Works
The architecture operates as a hierarchy of constraints and definitions. Higher layers define structural truth. Lower layers express implementation and representation within those constraints.
Changes flow downward. Validation flows upward. Structure remains consistent across all layers through inheritance rules defined in the core system.
Key Principle
The system is not a collection of documents. It is a structured model of governance, meaning each layer has a defined responsibility and cannot override higher-level definitions.
Navigation Map
- Root Specification → System identity and boundaries
- G01DN → Structural governance model
- Constitutional → Existence rules
- Protocol → Interaction rules
- Standards → Consistency rules
- Reference → Human-readable system view
Intent of This Layer
This page exists to make the architecture navigable without exposing internal governance logic or implementation constraints. It is a structural entry point into the system.