Living Framework Architecture · 2HE-ARCH-001

2HEco Living Platform

2HEco is a Living Universe whose canonical artifacts preserve a stable Current Working Version while permanently retaining their own structured capability to evolve.

Living Universe Principle

Every canonical artifact SHALL contain its own evolution capability.

The Living Factor is not an optional module. It is embedded throughout 2HEco so that documents, standards, capabilities, services, workspaces, projects, and governance remain stable enough to use and structurally capable of further evolution.

Git and 2HEco evolution analogy

Git supplies technical version control. 2HEco adds the semantic, participatory, and validation-oriented evolution model.

flowchart LR subgraph Git[Git] G1[main] G2[Branch] G3[Commit] G4[Pull Request] G5[Merge] G6[Commit History] end subgraph Eco[2HEco] E1[CWV
Current Working Version] E2[Idea Workbench] E3[Evolution Step] E4[Promotion Proposal] E5[Canonical Promotion] E6[Evolution History] end G1 --- E1 G2 --- E2 G3 --- E3 G4 --- E4 G5 --- E5 G6 --- E6

The 2HEco Living cycle

flowchart TD A[CWV
Stable canonical standard] --> B[Real use and Experience] B --> C[Observation] C --> D[Idea Workbench] D --> E[Evolution Steps
Collaboration and Experiments] E --> F[Validation] F --> G[Promotion Proposal] G --> H[Canonical Promotion] H --> A A -. preserved through .-> I[Evolution History] D -. visible evolution potential .-> I H -. recorded as .-> I
Quality emerges through experience, validation, and integration—not through collecting ideas alone.

Living Artifact

CWV

The currently valid, stable, canonical standard.

Idea Workbench

The visible participatory space for ideas, discussion, experiments, and collaboration.

Promotion path

The governed route from evidence and validation to Canonical Promotion.

Evolution History

The traceable record of how and why the artifact reached its current state.

You is an Entity

Participants are not merely passive users. An Entity may be a natural person, legal person, organization, team, AI agent, hybrid participant, or another compatible future participant type. Eligible Entities can contribute to Idea Workbenches, collaborate, validate, and help improvements reach canonical maturity.

Canonical architecture

This platform diagram is generated during the Guide build from platform/data/architecture.json. It is not manually maintained in this page.

flowchart TB
    ecosystem["2HEco<br/><small>Living Universe and canonical framework identity</small>"]
    constitution["Constitution<br/><small>Defines identity, purpose, authority, and evolution space</small>"]
    conventions["Canonical Governance<br/><small>Derives philosophy, ontology, patterns, principles, Conventions, Standards, and Specifications</small>"]
    evolution["Evolution & Applicability<br/><small>Maintains the CWV and routes the smallest coherent governing set</small>"]
    capabilities["Capabilities & Services<br/><small>Defines provider-independent ability and service semantics</small>"]
    templates["Components & Templates<br/><small>Materializes reusable governed implementations and structures</small>"]
    cli["2HE-CLI<br/><small>Executes conventions through one repository interface</small>"]
    repositories["Consumer Workspaces<br/><small>Contain local domain, project, and implementation work</small>"]
    products["Products & Systems<br/><small>Deliver operational outcomes</small>"]
    ecosystem -->|is governed by| constitution
    constitution -->|governs| conventions
    conventions -->|activates| evolution
    evolution -->|routes| capabilities
    capabilities -->|is realized by| templates
    conventions -->|defines| cli
    templates -->|creates| repositories
    cli -->|operates| repositories
    repositories -->|builds| products
2HEco Living Ecosystem · v1.1.0 · canonical

Canonical publication

GitHub main is the repository CWV and SSOT; the governed repository workflow is its SSE. GitHub Pages is a generated representation of that canonical state.
2he pages build

The build validates canonical data, generates the architecture representation, inserts it into this page, and validates Guide navigation.