Documentation
Architecture
Tiresias-ZT follows the classic zero-trust split: a policy decision point (PDP) that evaluates every request against policy, and a policy enforcement point (PEP) proxy that sits in the request path in front of your memory / MCP backend.
The complete guides for the current release are published at admin.tiresias.network, user.tiresias.network, and quickstart.tiresias.network. Administer your deployment from the admin portal.
Request path
An agent's request to its memory or MCP backend passes through the Tiresias proxy. The proxy verifies the agent's identity and capability token, evaluates deny-by-default policy, screens the request, and only then forwards it upstream. The decision is deterministic — no LLM is consulted in the decision path.
Audit
Every decision is written to an append-only audit log signed with the tenant's SoulKey, using hybrid Ed25519 + post-quantum ML-DSA signatures, so the trail is tamper-evident end to end.
Data boundary
Tiresias is bring-your-own-backend: the proxy runs in your infrastructure and your data stays in your store. Sovereignty gates ensure content marked never-cloud is never readable from a cloud instance.