Navigation layer
Why the platform is structured as it is today, which milestones changed its development path, and which evolutionary steps are planned next.
The repository became the authoritative source for 2HE architecture, terminology, principles, conventions, standards, and specifications.
Why it mattered: 2HE stopped being a collection of loosely related instructions and gained a single canonical platform foundation.
Evolutionary effect: Later repositories and AI participants could refer to one authoritative architecture instead of relying on remembered chat context.
General and specialized conventions were separated through the Applicable Conventions model: specialized rules may extend or constrain, but may not silently replace the general layer.
Why it mattered: Context-specific workflows could become precise without fragmenting the shared rules of 2HE.
Evolutionary effect: A convention could now be activated for a task, repository, participant type, or cooperation session while remaining subordinate to higher canonical layers.
The LCP-based cooperation protocol introduced participant-owned files, handshake validation, task exchange, review, and a mandatory conventions refresh before execution.
Why it mattered: The user no longer had to manually transport all project state from one chat into another.
Evolutionary effect: Cooperation became explicit, inspectable, repository-backed, and safer than assumed shared memory.
Canonical Markdown remained authoritative while GitHub Pages became the fast navigation, workflow, and conceptual-understanding layer.
Why it mattered: The architecture became quicker to understand and easier to operate without weakening canonical source control.
Evolutionary effect: 2HE gained a visible Navigation Layer that can grow into a developer cockpit rather than a conventional documentation site.
A product-independent participant model was defined for Copilot, Codex, Cursor, human developers, and future repository-bound agents.
Why it mattered: Repository cooperation no longer depends on one named AI product or coding environment.
Evolutionary effect: Repository developers became first-class 2HE participants with repository, branch, workspace, commit-head, and working-tree context.
The complete path was standardized: open repository, refresh conventions, resolve applicable rules, read the cooperation record, handshake, execute, validate, commit, pull request, review, merge, and close.
Why it mattered: Cooperation rules became an executable development rhythm rather than only a communication protocol.
Evolutionary effect: Future AI developers can join a repository through the same lifecycle without being individually hard-coded into the platform.
Knowledge Capture became operational through the Idea Cache and the command now exposed as 2he cache.
Motivation: Valuable ideas repeatedly emerged during real engineering work, but discussing them immediately disrupted the active task while postponing them risked losing context.
Outcome: Repository Validation now separates small sprint-relevant canonical updates from larger or unrelated captures. Every promotion check includes repository, duplication, domain, maturity, Guide, Evolution, and sprint relevance.
Key principles: Capture first; continue the sprint; canonicalize proven local improvements; keep unresolved hypotheses explicitly non-canonical.
Evolutionary effect: 2HE can preserve discoveries, maintain a clean working conversation, and prevent scope expansion from delaying implementation.
A safe GitHub Actions runner exposes 2he pages build and 2he repo status through manual workflow dispatch and short-lived command issues.
Why it mattered: Repository validation can be requested from a project conversation without requiring access to the local Codespace terminal.
Boundary: Only read-only validation commands are remotely exposed. Publishing and arbitrary shell execution remain unavailable.
Evolutionary effect: The conversation-to-repository loop now includes remote execution while retaining a constrained, inspectable security boundary.
2HE DO <Target> became the durable authorization for one scoped repository cycle through implementation, validation, commit, push, applicable deployment, and external verification.
Why it mattered: The user no longer has to repeat routine publication instructions while every reported state remains evidence-based.
Boundary: The contract does not authorize unrelated changes, secret publication, destructive history operations, or bypassing required review.
Evolutionary effect: Pages Create, Read, Update, and Delete operations now have one canonical source-to-public lifecycle with explicit completion boundaries.
Workbench, implementation, and consumer repositories received one global binding, README, bootstrap, local-content, adoption, and public-workspace contract.
Why it mattered: Repository independence no longer implies canonical autonomy, and new participants can recover both shared governance and the actual local implementation state.
Boundary: Applicable global and Component rules stay canonical in the Ecosystem; code, configuration, architecture, operations, and project status remain local to the implementation repository.
Evolutionary effect: New chats continue existing systems from verified sources instead of repeatedly recreating project intent from conversation memory.
Conversation Driven Engineering was established inside the Engineering domain as the method by which structured conversations shape repositories, canonical knowledge, architecture, processes, and products.
Why it mattered: Direct repository engineering from the project conversation proved that conversation can be part of the engineering process rather than merely a prompt interface.
Outcome: Repository-first development, repository validation, continuous canonicalization, domain locality, and sprint-preserving updates now form the initial CDE working model.
Evolutionary effect: New 2HE projects can begin with an empty repository and an initialized project conversation, then develop through short commit, build, review, and continuation loops.
The first canonical concept, Participant, defines an identifiable entity that can actively take part in the 2HE-Eco.
Next dedicated sprint: Validate Role, Assignment, Capability, Authority, Permission, Responsibility, and Trust.
Current boundary: The remaining concepts and meta-architecture hypotheses are preserved in the Idea Cache and do not block product coding in other project conversations.
Expected evolutionary effect: Identity becomes reusable across conversations, repository developers, agents, automations, services, and future 2HE systems.
Continue turning the guide into a developer cockpit with timelines, diagrams, repository context, cooperation state, search, and concise visual explanations.
Why it matters: Snappy visual understanding reduces the time required to form a reliable mental model of 2HE.
Expected evolutionary effect: The Navigation Layer becomes a practical working surface for learning, doing, and inspecting platform state.