Open source / shared contracts

Runtime Contracts

Project Adrasteia’s shared contract vocabulary for The Fates runtime protocol.

Last reviewed 31 August 2026

Core package

MIT-licensed public repository.

What are Runtime Contracts?

Project Adrasteia defines portable runtime identity, registration, capabilities, health, sessions, references, compatibility and protocol representation.

What problem do they solve?

Multiple runtimes need shared structural language without silently sharing authority. Contracts make identity and compatibility inspectable while leaving policy and execution to the appropriate owner.

How does it work?

The public package provides schemas, types and compatibility helpers. It validates structure and representation; a schema-valid request is not automatically an authorised request.

What is out of scope?

Policy engines, orchestration, memory systems, retrieval, persistence, gateways, transport adapters and other runtime behaviour remain outside the contracts package.

Contracts are not permissions.

The same distinction protects the architecture from turning “well formed” into “allowed”.

Source and evidence

Inspect the protocol surface.

Related projects

Ananke

Policy and governed execution.

FAQ

Does Adrasteia execute actions?

No. It is a contracts-only package and does not implement runtime authority.

What does a valid contract prove?

It proves that a representation satisfies the package’s structural rules. It does not prove that the request is authorised.