What happens when the box arrives.
The life of a Sókrates appliance, told in nine plates: from the moment it powers up at your site to the moment finished work lands on the record. Two acts: first the system orders itself around your operation, then your work flows through it.
Two acts. Nine plates. The whole lifecycle on the record.
Ordering the cosmos.
A loop, not a line: the system is assembled once, and then never stops being assembled.
Boot on-premises
The appliance arrives, plugs in at your site, and brings itself up: every service declared, not assembled by hand. The record is alive before the first act. From boot, each system event is captured without a second setup ritual.
Bind the sources
An operator connects the systems your company actually runs: the ERP, the finance stack, the databases. Each connection enters with a named scope, so the map starts with what the source system is allowed to show.
Three agents take turns ordering what flows in.
B3, B4, B5 — and back again. What one pass cannot finish loops around to be asked, authored or forged on the next. This loop is the load-bearing core of the whole system.
Information flows in
The bound sources are read and their structure is lifted into one typed map. And Sókrates doesn't just ingest — where the documentation is silent, it puts questions to your people, and the answers become part of what it knows.
Aristotle authors
Aristotle reads the matter and the answers, then writes the rules that say how your operation's pieces fit together and what counts as correct. Larger rules are composed from smaller ones, not bolted on.
Plato smiths
Plato works the capability gaps: where the system cannot yet do something, it forges the missing piece — a tool, a check, a bespoke agent fitted to your domain — and registers it, ready to be dispatched.
There is no done, only sharper.
Holes in the laws, missing capabilities, unanswered questions — each loops back into the queue, and the next pass closes it. Convergence is asymptotic by design.Work flows through it.
The ordered system at work: a request arrives, authority is established, and the work runs to done — on the record.
A trigger
Work begins with a trigger: a person asks for something over Slack, Teams or email — or the system opens a turn on its own, from a schedule or a condition it was watching. Either way, the request is on the record from its first moment.
The Philosopher-King reasons
The orchestrator plans what must happen and under whose authority. If a standing grant already covers this class of work, it proceeds; if not, it drafts the act and waits for a human signature. Either way the authority record is explicit.
The authorized workflow runs to done
The plan compiles into a durable workflow that survives restarts and pauses at the gates you have set — most visibly, the approval gate. Every step is stamped onto the record as it happens. The work runs to done.
On the record
The finished work lands in the system's history: every act, its cause and its authorization, auditable as one record. What the run revealed — a capability it lacked, a question it raised — feeds back into the loop. The cycle closes; the next ordering is sharper.
The honest version.
How is this different from just using ChatGPT?
A substrate, not a chatbot. Sókrates reasons over a verified, typed map of your systems and cites the rows behind every answer. It asks the model to operate over what is true, and every action carries an authority record you can inspect.
What happens if it gets something wrong?
Human approval is the default trust posture. Every action is a typed process with a named owner and an authority record, auditable as a single record. You authorise classes of work; you can revoke them.
Our data can't leave the country, or our network.
The appliance is installed on your premises. The Sovereign configuration uses local inference only.
What if we want to leave?
Clean exit, no hostage-taking. The hardware is yours; your operational data is yours. We deliver a portable custody export of your extracts, operating map, rule contracts, evidence and approval history. What ends is the managed department, not your ownership.
We're mid-migration. We can't take on another project.
The migration is the wedge. Sókrates provides semantic continuity across it: the same operational questions, the same evidence posture, before, during and after cutover.
One conversation is usually enough.
Bring one workflow that keeps crossing systems. Thirty minutes is usually enough to find the first useful question.