How it Works
From the job the deployer sets to a record anyone can check.
Purpose In
The deployer sets the agent’s purpose and keeps the authority over it.
The deployer is the person or organization that puts an agent to work and answers for it. The TELOS they write down is the anchor for everything below, because each action the agent sends through TELOS is measured against it. TELOS measures. The deployer decides.
- Writes down the agent’s TELOS and signs it.
- Sets how tightly its boundaries sit.
- Is the only one who approves a change to it.
- Decides what happens when something is flagged.
- 1
Write the purpose
The deployer writes down, in plain documents, what the agent is for, where it works, where it stops and which tools it uses.
Manifest: the written purpose · Purpose Anchor: its compiled reference - 2
Sign it
The deployer defines the purpose and rules. In a deployment, the deployer signs the TELOS.
The signature goes into the Record of Trust. In the published snapshot, commissioning row 18 names TES’s amended purpose file by its hash and carries the Witness signature. Row 19 binds the receipt digest of the filmed session. The offline checker verifies the Record’s Root and Witness signatures with the public key it ships with. Three early rows (commissioning 4 and 5, code 1) have no defined signed message, so they report NOT VERIFIED. Receipts in the published format carry an integrity hash.
Ed25519 key signature · human approval needs separate evidence - 3
Compile it
TELOS turns the written purpose into a reference it scores against, on five dimensions: purpose, scope, boundary, tool and chain continuity. Chain continuity also compares each action with the one before.
compiled purpose model · embedding centroids
The Run
The agent works. TELOS measures each submitted action against its declared purpose and records the result.
- 4
The agent works
Your agent runs the way it always does, on its own runtime and tools. TELOS sits beside it.
your agent’s own runtime · attached by adapter - 5
Connected actions are recorded
TELOS records actions on the paths connected to it.
receipts for what your agent sends through TELOS - 6
Scored against the purpose
The engine measures each action your agent sends through TELOS across purpose, scope, boundary, tool and chain continuity, before the action runs. A score is information for you as the deployer, and you set how sensitive the measurement is.
each action scored against the written purposepayload.scoressample-receipt.json
- purpose_alignment
- 0.94
- scope_discipline
- 0.91
- risk_review
- 0.90
Proof Out
TELOS turns the work sent through it into a record anyone can check, and that record has checks that can detect changes to it.
- 7
A receipt per action
Each action your agent sends through TELOS is measured against the purpose the deployer set. TELOS writes each measurement it records as a receipt.
one receipt per measured actionreceiptsample-receipt.json
- verdict
- EXECUTE
- composite_score
- 0.92
- integrity_hash
- sha256:5c4eb662…c965217a
- 8
Records link by hash
TES session journals and the Record of Trust link their entries by hash, and the checks detect a broken link. Compare the final hash of the journal or Record you are checking with one you kept yourself, apart from the record.
receipt list · hash-linked session journal · hash-linked Record - 9
Anyone can verify
The public Record carries each row’s hash and its place in the chain. Some fields, such as hostnames, sit behind salted commitments. An offline checker verifies the chain and the Root and Witness signatures. For an outside anchor, compare the head hash with one you got on your own.
offline verifier bundle · a final hash you keep yourself lets you check it later - 10
A person decides
A person reads the scores and receipts and decides what to do.
the human stays the authority
What this produces: the Record of Trust
A checkable record of what an agent sent through TELOS and how it scored against the purpose the deployer set. Hashes, links and signatures make changes to the covered data show (tamper-evident). Check it offline with the published Root key and a head hash you got on your own.