amduat-api/registry
Carl Niklas Rydberg e54a9009a6 Add GET /v1/space/mounts/resolve with local mount resolution tests
Add mount-aware v2 federation cursors with remote_space_id support
2026-01-24 19:50:13 +01:00
..
amduatd-api-contract.v1.json Add GET /v1/space/mounts/resolve with local mount resolution tests 2026-01-24 19:50:13 +01:00
api-contract.jsonl Add space manifest CAS head and read-only /v1/space/manifest endpoint 2026-01-24 18:42:01 +01:00
api-contract.schema.md federation 2026-01-21 19:51:26 +01:00
README.md federation 2026-01-21 19:51:26 +01:00

amduat-api registry (draft)

This directory mirrors the core vendor/amduat/registry/ model for the amduatd HTTP API contract.

Goal

  • Keep a stable, machine-readable API contract in-repo.
  • Seed that contract into the daemon's single ASL store root at startup.
  • Advertise the store-backed contract ref via GET /v1/meta.

The daemon remains thin: the contract bytes are data, and the store-backed ref acts as the version identifier.

Files

  • api-contract.schema.md — JSONL manifest schema for API contracts.
  • api-contract.jsonl — manifest of published contracts.
  • amduatd-api-contract.v1.json — contract bytes (v1).

Receipt note:

  • /v1/pel/run accepts optional receipt v1.1 fields (executor fingerprint, run id, limits, logs, determinism, rng seed, signature) and emits receipt_ref when provided.