Holonic

ARCHITECTURE

Most software is built to run. Holonic is built to reason.

Every part of a Holonic system is a holon: whole on its own, and part of something bigger. Each one declares what it is and what it's for, so you can reason about a big system without holding all of it in your head. And neither does your AI. It's the open-source architecture every Fathym product is built on.

.Takes().Returns().For()PART OF SOMETHING BIGGERWHOLE ON ITS OWN

every piece declares what it is, so you (and your AI) can reason about it

WHY IT MATTERS

From systems that report to systems that reason.

Software and the data under it were built to report: store it, dashboard it, let a human decide. Enough for visibility; it breaks when you want machines and humans to reason and act together. The old architecture can't reliably reason about what changed, what to do, whether it's allowed, and how the decision's recorded. Holonic is built for reasoning, not just reporting. Every part declares what it is and what it's for, so a system and its AI can act on what's happening.

Built to report

data → dashboard → you read
(passive, after the fact)

Built to reason

you + your AI reason → decide → act
(governed, in the loop)

HOW IT WORKS

What every piece carries.

Every piece declares what it is.

What it takes, what it returns, what it's for: as data your AI can read. Your AI reasons from what it declares, instead of guessing.

Composition is safe.

A piece behaves the same on its own as inside something larger. Build a big system a piece at a time; it never becomes a tangle.

Governance is built in.

Each piece carries its own guardrails wherever it goes: governed by construction, not a gate bolted on.

A human stays in the loop.

Observe, understand, propose, decide, execute, verify: a human decides what's consequential.

AT EVERY SCALE

One shape, all the way up.

The same holon works from one tool up to a whole platform. The architecture doesn't change as you scale, only the scope does. Nothing to relearn: you declare what things are, and the structure comes from how they fit together.

workbench
workshop
studio
platform

ACROSS THE FAMILY

The same loop, everywhere you build.

Every product runs this same loop: a change gets proposed, a human weighs in where it matters, and it ships once approved. Holonic is what keeps it the same at every scale.

observeunderstandproposedecideexecuteverify

BUILD ON IT

Open, and yours to build on.

Holonic isn't a tier or a product you buy. It's the architecture every Fathym product is built on, and it's shipping today.

@fathym/steward

The core holonic architecture. Capability, tool, operation, vault: the same holon shape. On JSR.

@fathym/cli

The command line for the whole stack. On JSR.

@fathym/fai

The personal workbench and the workbench runtime (fai run). On JSR.

// an Operation composing a Capability: every piece declares itself
const op = Operation('sync-readings')
.Takes(ReadingsSchema).Returns(SyncReport)
.Uses(Capability('historian'));

Coming to holonic.fathym.com: @fathym/holonic, a training corpus, and a public MCP server.