Cognitive On-Ramp

Short definition

A deliberately small, tailored entry layer that answers what is this, and where do I begin? without requiring a reader or assistant to reconstruct an entire project before using one part of it.

In the current Root Sequence documentation system, each repository's START-HERE.md serves this role and routes onward to PROJECT-CONTEXT.md and the project's canonical sources.

Why it matters

Growing projects accumulate enough structure that orientation itself becomes work. A cognitive on-ramp reduces that reconstruction burden while preserving an important authority boundary: the short map is a route into current reality, not a substitute for the documents that own detailed status, evidence, architecture, decisions, policy, canon, or implementation.

The pattern is useful for new, returning, or overloaded readers and for assistants that need the smallest relevant context before acting. One shared Markdown layer also reduces the risk of maintaining separate human and machine summaries that silently diverge.

Ecosystem use

The organization-level documentation contract defines the pattern once; participating repositories tailor the actual on-ramp to their own purpose, current reality, boundaries, structure, and next useful routes.

  • Root Sequence: routes broad conceptual work without asking readers to understand the whole ecosystem first.
  • Root Sequence Wiki: routes terminology, provenance, projects, seeds, and architecture without turning the on-ramp into another source of truth.
  • Liberated Intelligence: provides a small entry into the intelligence/agency inquiry while retaining project-owned models and evidence.
  • Universal Coherence Framework: gives an orientation layer while preserving the framework's own definitions, claims, and evidence boundaries.
  • Being Human(e): provides an accessible entry into the field-guide project without replacing its substantive material.
  • Liberation Mass: orients participants and contributors before deeper ritual, commons, governance, or practice material.
  • Root Sequence Discussions: explains the coordination hub and routes durable work back to project-owned homes.

Adoption by other repositories does not make their private content public and does not imply that all projects share one theory or authority structure.

Relationship to project context

The cognitive on-ramp and project context are complementary rather than competing summaries:

  1. START-HERE.md gives the smallest useful map.
  2. PROJECT-CONTEXT.md gives the structured working briefing and source-of-truth map.
  3. Canonical project documents own authoritative detail.
  4. Ecosystem maps and the Wiki expose cross-project relationships.

This layering is an instance of coherence without duplication: important state should be discoverable from the right entry points while substantive material remains canonical in one appropriate place.

Provenance

The phrase is now part of the public Root Sequence documentation contract and was merged into the organization infrastructure on 2026-09-21. Similar language about small orientation layers appears across the rollout repositories, but the exact authorship and earliest wording have not been established; provenance therefore remains origin-unverified.

Canonical substantive home

The documentation-layer contract, update flow, relationship vocabulary, automation boundary, and privacy rule live in Root-Sequence/.github/DOCUMENTATION_SYSTEM.md.

The Wiki should keep only the stable identity, relationships, provenance, and routing role rather than duplicate that contract.

Wiki connections

Project lenses

Related entities

Referenced by entities

Canonical substantive home

  • https://github.com/Root-Sequence/.github/blob/main/DOCUMENTATION_SYSTEM.md