SIEGE / Documentation
Siege technical documentation · version 2026-10-16 · 11 pages
01
Overview
01
What Siege builds
What Siege builds, the layers it is made of, how every action is controlled, and what a technical reviewer can check.
02
Approach and philosophy
What Siege believes about building a company's operating system, and the commitments that follow from it for the client and its technical person.
02
The Ontology
03
The Siege Ontology Framework
One model of the business presented through five views (altitudes, perspectives, axioms, governance and analyses), and the single file that holds the model and lets each agent be given exactly the part it needs.
04
The Ontology
Why Siege starts every system from an Ontology, what keeps one clean, how every data model, screen and agent is built from it and checked against it, and how changes to it and the actors in it are governed.
05
The three-way cross-check, Ontology, Choreograph and application
Why Siege keeps the rules, the order of work and the running software as three separate layers, how each layer is checked against the other two, and what that guarantees before anything ships.
03
Control and security
06
AI and agents under control
How every action by a person or an agent is controlled, why the application comes before any agent, the keys an agent holds, how untrusted text is handled, and how Siege's Forward Deployed Engineer (FDE) works in the client's system.
07
Security and control
How a client's system is secured, what each control guarantees and how a technical reviewer can check it, and what must be done before the client's real data connects.
04
Data
08
Refractor: moving and cleaning data
What Refractor guarantees when a client's existing data is moved, cleaned or brought into its Ontology.
09
Data commitments
The data agreement every engagement signs before real data connects, the two approvals needed to go live, and Siege's commitments on use, retention, breach notice and export.