The part that outlives the products.
The architecture · Commitment 3 / 4
The durable community layer is the part of Unifyhub that survives product churn. It protects the record a community needs in order to remain itself when interfaces, hosting models, AI systems, or product boundaries change.
Two terms, used precisely: the shared coordination layer is the five contract families every product consumes (identity, policy, audit, events, migration). The durable community layer is that layer plus everything that keeps it honest: stable APIs, extension rules, reference implementations, conformance, and public governance. The first is what products build on; the second is what communities can rely on.
What it includes
Portable membership, identity, and roles
A model of who belongs that a community can carry when it moves tools.
Policy and delegation
A model of who can do what, on whose authority, that is explicit and transferable.
Shared events
A common event model so important happenings are recorded in a way that outlives any single product.
Work object and workflow contracts
Common contracts for the objects and processes a community works with, so work survives product changes.
Audit records
Records of important actions and decisions, preserved after the fact.
Public, versioned APIs
Interfaces stable enough to depend on and public enough to build against.
Extension contracts and namespace rules
Clear rules for how products and extensions add to the ecosystem without colliding.
Reference implementation
Where practical, a working example of the layer that others can compare against.
Conformance tests and compatibility marks
Testable claims that an implementation honors the contracts, beyond mere assertion.
Public proposal and decision process
A visible process for changing the shared layer, so communities are never ambushed by ecosystem-level change.
The standard for products
Products are judged by how well they preserve this layer without privately capturing it.