A system that can describe itself.

All capabilities · In build

Communities lose more to forgetting than to failure. The decision nobody can reconstruct, the rule whose reason left with a person, the system nobody can explain any more: these are how a group stops being able to govern itself. This plane exists to make remembering structural.

saturday opening

source · minutes/2025-03-11source · rota/volunteers.csv

Illustrative example · five nodes of a much larger map. One decision, what it came from, what it changes, and where each statement was read.

The system describes itself

  • Every part emits a description

    Code, services, deployments, documents, contracts, infrastructure, and physical assets each publish a machine-readable account of what they are and what they relate to. The description is generated from the thing itself, so it cannot drift into wishful documentation.

  • Descriptions join into one map

    Those accounts merge into a single graph of the ecosystem: what exists, what depends on what, what a change would touch, where a capability is implemented, and which record backs a claim. The map is queryable by people and by delegated software.

  • Every statement cites its source

    A node or a relationship carries where it came from and how confident the producer was. A map without provenance is a rumor with better typography.

Layered memory

  • Working memory

    What is true for the task in front of someone right now, discarded when it ends.

  • Project memory

    The goals, constraints, and decisions of an ongoing effort, including the reasoning that would otherwise be lost between sessions.

  • Durable memory

    What the community has settled: rules, preferences, standards, and the reasons behind them, written where the next person will find them.

  • Reference memory

    Pointers to the authoritative external thing rather than a copy of it, because a copy is a fact with an expiry date nobody stamped.

Retrieval that can be checked

Questions are answered from the record with the source attached, not from a model's recollection. Retrieval is scoped by the same identity and policy rules as everything else, so what a person or an agent can be told matches what they are allowed to know. An answer without a citation is treated as a draft.

Why this is a trust capability

A system that can describe itself can be audited by people who did not build it. That is what makes a credible right of exit more than a file format promise: a community leaving takes not only its records but the map that explains them, and a community staying can see the shape of what it depends on.