Shared work starts with shared meaning.
A vocabulary used precisely is part of the work. These are the terms this site leans on, defined once.
C 6
Capability plane
A horizontal ability shared by the whole ecosystem rather than owned by one product: interfaces, domain services, events, agency, knowledge, collection, models, substrate, physical automation, delivery. Adopting any part of the system brings the planes with it.
Capture
The point where a system that started as a community's tool becomes the community's owner: records, relationships, history, and decision rights all behind one company's control. The failure mode every principle guards against.
Community sovereignty
A community's practical ability to understand, govern, and move its own operating life: membership, decisions, policies, records, and tools.
Conformance
Proof, by public tests rather than by relationship, that an implementation honors the shared contracts. What makes "compatible" a fact instead of a negotiation.
Contract
A stated agreement between parts of the system, carrying rules, the reasoning behind them, an executable check, and a public process for changing it. Boundaries between layers are contracts, which is what keeps parts replaceable.
Credible right of exit
The guarantee that a community can leave with identity, history, data, relationships, and operating memory intact, through usable exports, documented formats, and published migration guidance.
D 3
Declaration
A description of a desired assembly, written as a document a runtime turns into the running thing: a screen, a service surface, a deployment, a procedure. Declarations can be read, diffed, generated, and reversed, which is why the system prefers them to instructions.
Delegated actor
Software acting on a community's behalf, holding its own identity, operating within an explicit scope for a stated period, and appearing in the record as itself. Never a borrowed human account.
Durable community layer
The part of the system that survives product churn: the shared coordination layer plus stable APIs, extension rules, reference implementations, conformance, and public governance.
E 1
Evidence
What was observed, kept as observed, with time and source attached. The difference between a notification that something changed and a basis for acting on it.
I 1
Intent frame
The structured object Praxis builds from human signals before any action: who is acting, through which modalities, meaning what target, requesting what action, at what confidence, requiring what confirmation.
O 2
Operating record
Everything a community needs to remain itself: who belongs, what was decided, who can act, what changed, and why. The thing Unifyhub exists to keep hard to lose and hard to capture.
Operational language
An interface that has become shared vocabulary between people, teams, tools, and agents. Once an interface reaches this status, it gets versioning, compatibility tests, and governance rather than casual redesign.
P 1
Provenance
Where a claim came from and how it was determined, travelling with the claim rather than stored beside it. Required on records, on graph statements, and on anything a model produced.
S 5
Shared coordination layer
The five contract families everything in the ecosystem consumes: identity, policy, audit, events, and migration. One layer, many replaceable experiments.
Signal
Any raw input a system can interpret: a webhook, an alert, a sensor reading, a spoken phrase, a gesture. Signals become actions only through governed flows with provenance.
Steward
A community member accountable for the record they help build, holding a visible path to influence decisions. Stewardship is responsibility with influence attached; titles are beside the point.
Structural trust
Trust held by the architecture: rules, records, and accountability that stay true regardless of who is in charge. The opposite of trust that depends on a founder's goodwill.
Substrate
The compute, storage, network, secrets, and delivery mechanism everything else runs on. Judged by operability rather than by ownership alone: a substrate a community cannot patch, observe, back up, and restore is autonomy in name only.
T 1
Trust
The unit of measure of a contributor's standing in Unifyhub: earned in the open on past achievement related to this work, and revocable. Trust makes a person eligible for trusted roles; authority itself comes only from an election, a confirmation or a local grant. Not a title, not a headcount; a record.