Five primitives. One typed map. One authority record per act.
The deep cut, for the people who gate on architecture. Sókrates compiles source systems into a typed hypergraph and runs governed work over it. None of this is required reading to buy; it is here because it holds up to scrutiny.
Evidence first. Action only with current authority.
Matter, form, actor, cause.
Hyle
The schema-compiler layer that reads source systems and lifts their structure into the map.
Eidos
The canonical typed hypergraph. Both the lakehouse and the runtime are projections of it; the form is what is canonical.
Demiurge
Anything that shapes the graph or acts under authority. A person, an agent, a process: each is a named actor.
Aition
The authority envelope every governed act carries. The substrate verifies it before anything is written.
traversable
Every edge carries a flag. A false flag is a capability gap, and the set of false-flagged edges is the work queue. The substrate knows what it cannot do.
The map is a function of the territory.
Eidos is canonical; the lakehouse and the runtime are projections of it.One sovereign router. Three vassals, each with one job.
Vassals never call each other laterally; the orchestrator is the only router. The brand is Sókrates; the dialogue vassal is also Sókrates. The overload is intentional.
PK
Runs the runtime, holds consent custody, and is the only router. It does no domain work itself.
Sókrates
The only vassal that talks to humans. Channel-facing, on Slack or Teams; the surface you actually speak to.
Aristotle
The only vassal that writes Laws, the executable rules, into the graph.
Plato
The only vassal that mints capability artifacts to close gaps: a predicate, a deterministic node, a fitted model, a tool.
Read by default. Write with current authority.
Discovery answers from the standing data grant. Action requires current authority from a data owner: either a standing grant for that class of work, or a one-time approval the operator just clicked. The capability layer compounds across the fleet, so onboarding stays finite.
One conversation is usually enough.
Bring one workflow that keeps crossing systems. Thirty minutes is usually enough to find the first useful question.