Kompendio
Kompendio is the reference & integration layer of Konnaxion: a publishable repertory of standards, maps, and versioned “how things connect” charts.
It exists to keep the ecosystem governable—so people can understand dependencies, reuse proven components, and avoid reinventing everything every time.
What Kompendio does
- Makes the ecosystem legible: what exists, what depends on what, and what standards are used.
- Publishes stable “reference stacks”: so teams can align on shared building blocks.
- Creates versioned charts you can pin to projects: so a project always has an explicit, inspectable foundation.
- Supports portability: by making integrations explicit and repeatable.
Kompendio vs Kintsugi
Kintsugi is the “one-roof” integration experience (how modules behave like one product).
Kompendio is the “reference and maps” layer (how modules remain understandable, auditable, and composable over time).
Where Kompendio exists today
Kompendio is being defined per module. Some parts are already documented; others are explicitly marked as TBD.
KonnectED
TBDCompetence, credentials, and the public learning layer. The module is public, but its dedicated Kompendio reference pack is not yet shipped as a standalone page.
keenKonnect — Kompendio
AvailableReference stacks and charts that can be pinned to projects so teams share the same explicit foundation.
ethiKos — Kompendio
TBDThe module has a clear deliberation workflow, but the Kompendio reference layer is not yet defined as a complete, standalone artifact. When it exists, it will publish versioned “how deliberation works” maps.
Kollective Intelligence
TBDSmartVote and EkoH are defined operationally, but a dedicated Kompendio reference layer (maps, standards, published lenses) is not yet shipped as its own module document.
Use Kompendio the right way
Kompendio is not “docs for developers.” It is the civic engineering equivalent of a public ledger: publishable maps that make systems inspectable, reusable, and contestable.