Skip to content

[Epic] Phase 4 — Agent-to-Agent + Mandate #11

Description

@iret77

Epic — Phase 4: Agent-to-Agent (+ binding Agent-to-Human). The strategic centre: two agents close end-to-end; plus the binding A→H pulled here from Phase 3 (Codex C3, plan.md §3.2).

Deliverables

  • Mandate issuance + kernel escalation gateMandate issuance + kernel escalation gate #12
  • proof.identity@1 extended with agent DIDs
  • Status-list hosting + mandate revocation lifecycle (Codex IMPORTANT)
  • SD-JWT disclosure for mandates (ANP §6.6, against cap leak)
  • Aggregate-cap enforcement
  • Mandate management UI (principal sets caps: "what may this agent sign without asking?")
  • Binding A→H + A2A acceptance flows

Done (plan.md §7 Phase 4)

Two agents of different parties close autonomously within their mandates · binding A→H via approve · an over-threshold action escalates reliably · mandates are revocable (status list) · full audit trail · ANP PRs for approve + mandate VC open.

Blocked by: Phase 3 (#9); Stage A — custody scale (R11).
Refs: plan.md §7 Phase 4, §3.1, §3.2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    anp-backflowTriggers a mandatory PR in byte5ai/anparea/identityproof.identity@1 — DID / keys / mandate (the crypto capsule)area/kernelbyte5ai/omadia kernel change (escalation gate / custody)type/epicTracking issue for a phase / stage

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions