Ask about TES and her record

TES runs on Anthropic's Claude, so we send your question to Anthropic to get the answer. Please do not put anything sensitive in your question.

Press Enter to ask. Shift+Enter adds a new line.

TES is an AI.

How TES works

Constitutive governance means the deployer defines an agent’s purpose and rules, and the agent is formed from them. At runtime TELOS measures how closely the agent holds to them. Read .

Ask one question in up to 800 characters. Your downloaded record carries a fingerprint in place of your question text.

We declared TES’s purpose at commissioning. Before TES answers, TELOS scores your question against that purpose when it can, and the record shows what happened. If your question looks like it holds a secret, like a password or a key, TES puts a marker in its place and does not score it.

TES supplies a passage. The page locates it in the pinned source and shows that source text.

Check your session file

For an Ask-only session, a delivered file is signed (TES-SESSION-BUNDLE/2) only when coverage is complete and signing succeeds. Otherwise it is unsigned (TES-SESSION-BUNDLE/1), even with complete coverage.

The offline checker compares the payload with its recorded digest. For a file with an attestation, it also checks the supplied chain links and signatures against the Record of Trust files you provide.

Use Python 3.11 or later with cryptography 48.0.1. Keep verify_session_record.py and verify_bundle.py in one folder. Obtain the public record/bundle folder with its published paths and follow its README and requirements.txt to prepare your Python environment. If you followed the README's virtual-environment setup, activate that environment in this terminal before running the command. In the command below, replace tes-session-bundle.txt with your downloaded filename.

Download session checker (verify_session_record.py) Download required companion (verify_bundle.py)
python3 -I verify_session_record.py tes-session-bundle.txt record/bundle

Exit 0: attestation checks passed; for current files no further action is needed. Read the coverage line for older files. Exit 1: a check failed; follow Report a check problem below. Exit 2: check Python 3.11+, cryptography 48.0.1, both checker files in one folder and the record folder as the second argument, then rerun. Exit 3: read the printed lines. NOT ATTESTED means this file has no attestation. If attested with incomplete or unavailable session coverage, read the coverage line and any MEMBER and GAPS lines.

Report a check problem: for exit 1, email info@telos-labs.ai with the SHA-256 of the entire downloaded file and the full checker output. We aim to acknowledge reports within two business days, on a best-effort basis. For this prototype, one TELOS AI Labs operator holds all three roles: page operator, Witness key holder and report recipient.

A passing attestation check binds the payload digest to the Witness key enrolled in Record of Trust row 15 under the supplied root key. The payload origin field remains unauthenticated.

To check the signed Record of Trust, follow the steps on the Record of Trust page.

The check covers the supplied public session record, not native receipts. A passing attestation check does not establish trusted signing time, who operated the key, per-row human approval, complete event capture, or the truth or correctness of the recorded work. Constitutive fidelity readings are recorded measurements, not proof that the work followed the declared specification.