Syntropy — Holons

Order out of chaos for the age of AI agents.

The nine holons of SyntropyOS, one directory each.

Each capability is a holon: autonomous yet connected — a whole in its own scope and part of the Syntropy ecosystem at the same time.

This repository is the substrate, not the product. It exists because nine repositories that each contained one file cost more to maintain than they proved. The directory layout is the thesis made visible: every capability is a separate piece with its own problem, its own customer and its own place in the build order.

A holon is not built because it is on a roadmap. It is built when a diagnosis in a real organization finds the chaos this holon resolves.

This criterion replaces prioritizing by technical interest, and it is why the priorities changed. A holon with no diagnosed chaos behind it is a guess.

Defined means the design and activation criteria are documented; it does not mean it ships. Only the substrate (VantaDB) is in production today.

Cardinal comes first because the others depend on it: without verifiable context there is nothing to perceive and nothing to verify. Meta moved from ninth to third because it is the differentiator — the competition sells capability, this sells verifiability.

Plan appears after Meta because its output is meant to be verifiable, and verification is what Meta provides. It is not an independent capability.

Sage is adaptation in both halves: the machine learns from corrections, and the people change how they work. Enterprise AI fails on adoption more often than on accuracy, and no other holon covers that.

VantaDB is the one holon already built. It lives in its own repository because it is a released library with an independent version cycle. Everything in this repository is what is missing.

The substrate is not a dependency of the holons. Each holon owns a scope, a deliverable and a metric of its own. VantaDB is the reference implementation of storage, not a requirement. Three questions decide whether something is a holon or a feature of the store:

1. Does it survive a backend change? A holon does: what it owns is logic and semantics, not tables.
2. Does it deliver something on its own? An index, a log, a dataset, a rollback.
3. Does it have its own surface — API, SDK, MCP — beyond a table inside the store?

If all three answers are no, it is not a holon: it is a table. None of the nine fails this test.

The holons are not an invention. They map onto the canonical decomposition of an agent architecture:

Episodic memory is identified by the industry as a capability that is missing and that production frameworks treat only superficially. That is Cardinal, and it is a real gap.

Hard rule: if a capability only exists inside a human interface, it is consultancy disguised as software. Everything done for the client has to exist as an API.

VantaDB  (substrate, in production)
   └─► 1. Cardinal   context       ┐
   └─► 2. Iris       perception    ├─ without Cardinal there is nothing to verify
   └─► 3. Meta       trust         ┘
   └─► 4. Execute    execution     requires prior trust
   └─► 5. Sage       adaptation   requires trustworthy context and Iris
   └─► 6. Plan       decomposition requires something to verify the steps against
          Orchestra   runtime       once two holons are alive

No dates. The order comes out of the diagnosis, not out of a calendar.

Reverb and Reason are deferred with written reactivation conditions inside their own READMEs. Deferral is not deletion: the condition that would bring each one back is on record.

Every document in this repository exists in English as the primary version, with Spanish as an option:

README.md                        English  ← primary
README_ES.md                     Español
holons/<name>/README.md          English
holons/<name>/README_ES.md       Español

The same convention applies across the organization: MANIFESTO.md, ROADMAP.md, CONTRIBUTING.md and the rest are English, with a _ES.md counterpart.

This repository contains what we build. The why and the for whom live elsewhere:

The split is deliberate. Mixing "this is what we believe" with "this is what we know about the market" degrades both.

Apache 2.0 — see LICENSE.

History. This monorepo replaced nine per-holon repositories, syntropy-<holon>, deleted on 29 September 2026. Each was merged with git subtree, so all 27 original commits survive here with their original authors and dates. Their history lives inside the monorepo.