Canonical derivation · Current Working Version

2HEco canonical architecture

The ecosystem is not a flat collection of “Conventions.” Meaning flows through explicit canonical layers; capabilities, services, consumer workspaces, projects, and artifacts realize that meaning without becoming competing sources of it.

Derivation chain

2HEco↓Constitution↓ Philosophy↓Ontology↓ Pattern Language↓Principles↓ Conventions↓Standards↓ Specifications↓Capabilities and Services↓ Consumer Workspaces↓Projects and Artifacts

Each lower layer derives from its applicable canonical parents. No layer may silently bypass or redefine higher meaning.

Canonical foundation

ConstitutionIdentity, purpose, scope, authority, and legitimate evolution space Living Universe PrincipleEvery canonical artifact retains its own evolution capability OntologyEntities, identity, relationships, and what exists in 2HEco Pattern LanguageRecurring implementation-independent structures PrinciplesStable decision foundations derived from meaning

Operative governance

Conventions FrameworkCBP, General and Applicable Conventions, categories, and adoption Evolution and ApplicabilityCWV, semantic status, promotion, history, and smallest-coherent-set routing Repository BindingHow other repositories derive governance without duplicating the SSOT CooperationParticipant identities, records, handshakes, and working lifecycles Agents, Teams, and NetworksContinuity freshness, live coordination, XRT separation, and ownership boundaries StandardsReusable baselines for coherent interoperability SpecificationsPrecise and verifiable realizations

Realization layers

Capabilities and Services

Provider-independent semantics describe what can be done. MCP, connectors, APIs, CLIs, native adapters, and controlled human steps are possible implementations.

Components

Reusable implementations such as 2HE-CLI carry Component-specific governance while remaining derived from the ecosystem.

Consumer workspaces

Repositories and projects retain local implementation knowledge and apply only the shared governance that matches their type and task.

Living Factor across every layer

Every canonical layer remains connected to a CWV, Idea Workbench, Evolution Steps, validation and Promotion, and Evolution History. Canonical means currently validated and authoritative—not permanently finished.

Authority rule: this page is a human-facing map. The linked Markdown and structured data on authoritative main remain the canonical CWV.