Academic programmes

THE FULL LIFECYCLE

Perissos covers an AI agent from design to retirement. Not every stage is shipped. Each part below says how far it is built today, the stage table on our About page gives more detail for the stages it covers, and we would rather you check than take our word for it.

BEFORE IT SHIPS

Today: deriving the obligations is BUILT. The Agent Passport is PARTLY built: an agent's record (what it does, its autonomy, its tools, its owner and who can halt it) can be published, and on paid plans included in a signed export that anyone holding it can verify offline against our published key. Who approved the agent is not recorded yet.

Know which obligations will bind the agent before you write it, and publish a signed Agent Passport your customers can verify: what the agent is, what it may do, who approved it, and how it is stopped.

WHILE IT RUNS

Today: PLANNED.

Keep the agent inside the rules at the moment it acts, with each decision kept as dated evidence rather than a log line nobody can cite.

AFTER IT SHIPS

Today: PARTLY. On paid plans, an incident you record starts the reporting clocks it triggers under the rules we hold. Monitoring your agent after release is not built yet.

Post-market monitoring and serious-incident readiness that answer to the Act's own deadlines, not a generic playbook.

TESTING YOUR OWN AGENTS

Today: PLANNED. Consented testing is designed, not built.

Adversarial testing under your authorisation, with results sealed as dated evidence you can put in front of an auditor.

SEEING WHAT YOUR BUYERS SEE

Today: PARTLY. The public read of a company's declared AI surface runs today; agent-level reads are planned.

A read of your agents from the outside, the way a customer's security team would see them, bound to the obligations each finding implicates.