A system that can account for itself.
The architecture · Structure 4 / 5
A community can only govern what it can see. Past a certain size, seeing stops being a matter of reading documentation and becomes a matter of whether the system can account for itself. Unifyhub treats that account as a required output of every part rather than as a project someone does once.
Description is generated, not written
Each part of the system publishes a structured statement of what it is: its interfaces, its dependencies, its deployment, its contracts, its documents, its physical assets. Because the statement is derived from the thing itself, it stays true when the thing changes, which is the failure mode that eventually destroys every hand-maintained architecture diagram.
Statements join into one map
Uniform identity
Everything worth referring to has a stable identifier of a known kind, so two producers describing the same thing produce the same node.
Relationships are first-class
Dependency, ownership, implementation, deployment, and derivation are edges, which is what turns a catalog into something you can ask questions of.
Provenance is mandatory
Every node and every relationship states where it came from and how it was determined. Confidence and source travel with the claim.
Depth is selectable
The map is layered from ecosystem shape down to fine detail, so a person or an agent can ask for the altitude they need instead of drowning in the one that exists.
What legibility makes possible
Impact is answerable
What a change would touch is a query rather than an experienced person's guess, which matters most when the experienced person is unavailable.
Delegation gets safer
Software acting on a community's behalf can orient itself in a described system. An agent operating in an undescribed one is guessing, confidently.
Onboarding is structural
A newcomer can see the shape of what exists without being granted access to everything or waiting for someone's attention.
Exit is informed
A community that leaves takes the map along with the records, which is the difference between receiving your data and understanding it.
The honest limit
A map is a claim about reality, and claims decay. The defenses are provenance, generation from source, and treating a disagreement between the map and the system as a defect. What the map must never become is a second source of truth that people maintain by hand and trust by habit.