WHAT WE BUILD, AND
WHAT IT GUARANTEES.
Every part of the system in one picture, what passes between the parts, and the promises it keeps, each linked to the page of our documentation that sets it out in full.
WHAT AN ONTOLOGY IS MADE OF.
An Ontology is a digital twin of your entire organization. Everything your organization collectively knows, does and records is codified within it: every object, every action, and every way they connect to each other.
What your organization knows: every object it works with, and how each one connects to the others.
- OBJECT
- Something your organization works with, such as an order or a customer.
- PROPERTY
- A fact held about an object, such as an order's price.
- LINK
- How two objects connect, named both ways: a customer places an order, and an order is placed by a customer.
What your organization does: every action that changes an object, and who is allowed to take it.
- ACTION
- A defined change to an object, such as approving an order.
- CONDITION
- What must be true before an action can be taken, such as the order having a price.
- ARCHETYPE
- A kind of person in your organization, such as a manager, and the actions that kind of person may take.
- AGENT
- An AI worker named in your Ontology, with keys of its own.
- KEY
- One action an archetype or an agent is granted.
What your organization records: the live data and documents from every system, kept current as the work happens.
- DATA
- The values your objects hold today, in your own database.
- RECORD OF CHANGE
- Who changed what, when, and the value before and after.
Every part of your Ontology is written in your organization's own words, so its owner can read every rule it holds.
Every change to your Ontology is numbered, checked against its own rules before it is accepted, and kept, so you can see what moved, who moved it and why.
Your Ontology is kept in the W3C's open standards, RDF Turtle with OWL 2 and SHACL, so any standard tool can read it.
EVERY PART, AND WHAT
PASSES BETWEEN THEM.
HOLDSEvery object, link and action your organization works with, and which archetypes and agents hold the key to each action.
GIVES BACKThe one statement every screen, table and agent is built from and checked against.
TAKES INWhat your organization tells us, and samples of your data, only ever read.
GIVES BACKYour Ontology, one numbered revision at a time, each checked against its own rules before it is accepted.
TAKES INYour Ontology, and the data in your data layer.
GIVES BACKYour application: a screen for each area of work, and an action check that lets each action through only for the archetypes and agents that hold its key.
TAKE INOnly the data their archetype may see, on a screen made for their area of work.
GIVE BACKActions, each passing the key check and the condition check before anything is written.
TAKE INTheir keys, each one action, and only the part of your Ontology their task needs.
GIVE BACKOnly the actions they hold keys for. Any other is refused at the key check, and the refusal is written to the record of change.
TAKES INEvery change to your data, and every action asked for, refusals included.
GIVES BACKWho acted, when, and the value before and after, kept in your own database where nobody can alter it.
TAKES INData from the systems you run today, only ever read. Nothing is written back.
GIVES BACKYour data in your Ontology's shape. Nothing lands until a named person accepts it.
TAKES INYour leadership's goals, from the North Star down to the numbers that show progress, and the work as it happens.
GIVES BACKEvery piece of work traced to the goal it serves.
TAKES INThe work as it happens, from DrawBridge.
GIVES BACKThe owner's report, each figure in it traced to the work it counts.
TAKES INYour questions about your own work, in plain words.
GIVES BACKAnswers drawn from your Ontology and from the data you may see.
Data comes up from your data layer through DrawBridge to the people and agents allowed to see it. Actions go down through the key check and the condition check. The record of change runs alongside every layer.
ONE ACTION, START TO FINISH.
A manager approves an order, and an AI agent tries the same action. The manager holds the key. The agent does not, so it is stopped at the key check, and its refusal is written down beside the manager's change.
Every change is a defined action. It runs only after the key check and the condition check pass, and the record of change keeps who took it and when.
An agent holds only the keys your Ontology grants it, and no key carries an administrator's or an engineer's powers.
Every action asked for is written to the record of change, refusals included.
WHAT THE SYSTEM GUARANTEES.
- RECORD OF CHANGE
Every change to your data is written to the record of change, with who made it, when, and the value before and after, and nobody can alter that record.
SECURITY AND CONTROL → - SEPARATION
Your system has its own deployment, database and repository, in your own accounts. Its database is never shared with another client.
SECURITY AND CONTROL → - ENCRYPTION
Every connection to your system is encrypted, and its database, backups and files are encrypted at rest.
SECURITY AND CONTROL → - AI AND YOUR DATA
Your data is never used to train an AI model. Every AI feature runs on your own provider account, set so the provider neither keeps nor trains on what is sent, and is sent only the fields your data agreement lists.
DATA COMMITMENTS → - DAY ONE
Your current systems keep running while DrawBridge is filled from them, only ever read. Nothing lands until a named person accepts it, and nothing is switched off until your people work in DrawBridge.
HOW TO VERIFY OUR WORK → - CHANGES TO YOUR SYSTEM
Every change reaches your live system only through named checks: data changes through the key check and the condition check, code changes through review by someone who did not write them, administrators included.
SECURITY AND CONTROL →
SEND THIS TO
YOUR ADVISER.
Our documentation sets out each guarantee in full, with the checks your technical reviewer can run on your own system.
Siege engineers your organization's work, its people and its technology as one design.