2AYE
Evidence-backed status

What this implementation proves today.

This is capability status for the public reference implementation—not a hosted-service uptime dashboard, certification, or production-readiness claim.

Run the verified path Read the specification
Repository-backed

Implemented and tested

  • Deterministic runtime decisions

    The frozen predicate envelope reaches one evaluation path and fails closed when deterministic checks fail.

  • Exact, single-use authorization

    Grants bind material parameters, expire quickly, and use atomic redemption to prevent replay.

  • Delegation cannot expand authority

    Child intent is checked at creation and again when an action is evaluated.

  • Portable verification foundations

    Public grant keys, JavaScript verification, published canonicalization vectors, and protected-resource executors are repository-backed.

  • Hash-linked runtime evidence

    Decisions, grants, redemptions, human decisions, and execution receipts append to the audit chain.

Explicitly open

Not yet demonstrated end to end

  • Production key custody

    No cloud-provider SDK is bound to the managed signing-key abstraction, so KMS or HSM custody is not demonstrated in deployment.

  • Complete multi-instance authentication

    Runtime entities can share Postgres, but sessions, applications, and OAuth authorization and refresh grants remain process-local.

  • Externally verified connectors

    The HTTPS protected-resource connector is implemented and tested, but no vendor-specific adapter has run against a real provider account.

  • Semantic and mobile approval completion

    Semantic findings remain NOT_EVALUATED, and the Flutter client does not yet complete the device-signed approval ceremony.

  • Cross-edge replay proof

    Single-use consumption is tested, but replay rejection has not been demonstrated across two separately deployed gateways.

Operational boundary

Live service monitoring is not connected.

No production regions, uptime percentage, incident history, maintenance window, or SLA is asserted on this page. Those claims require deployed telemetry and an operating service.

Source of truth

Inspect the evidence, not a badge.

Implementation status follows the repository’s story manifest and specification divergence table. A story is only end-to-end verified when its deployed surface, failure paths, and abuse paths have evidence and no recorded gaps. Every capability each page does not claim is tracked as work in CAPABILITY_BACKLOG_2026-09-24.md, generated from the same data the pages read.

Your governed workflow

Bring the next consequential action under control.

Show us the actor, protected resource, and action that must never execute without exact authority. We’ll map the decision and evidence path with you.

Discuss your workflow Read the implementation guide
Verified Implementation Status | 2AYE