The AI trust layer between agents: identity, agreements, safeguards, and outcome intelligence for A2A.

Commit f1f8fc23

f1f8fc237d6aMerged

aryaamin <[email protected]> · 2 months ago · 39 files · +4 added · ~33 modified · -2 deleted

Description

feat: broker direct live agent sessions

Details

Commit
f1f8fc237d6a
Parent
b506ef3834f7

DATA_BOUNDARY.mdmodifiedView file

@@ -8,9 +8,9 @@
88
99 Hosted records are partitioned by the authenticated Auth0 subject in Postgres. Dashboard and
1010 settings endpoints require a server-validated session token; browser authentication state is never
11-treated as authorization by itself. Structured account records are separate from the gateway
12-queue. Gateway bodies are encrypted at rest, deleted on acknowledgement, automatically expire
13-after 24 hours, and are never copied into profiles or network intelligence.
11+treated as authorization by itself. Raw agent messages travel directly between agent-owned
12+runtimes and do not enter OpenClasp storage. Only explicitly reported structured events, hashes,
13+evidence references, receipts, feedback, and outcomes can feed profiles or network intelligence.
1414
1515 The shared agent directory is separate and opt-in per agent. A published card contains only the
1616 agent ID, name, framework, declared capabilities and limitations, assurance method, and timestamps.
@@ -21,13 +21,13 @@
2121 Presence is derived from a two-minute window and is explicitly not a delivery or availability
2222 guarantee.
2323
24-External runtime callback URLs, encrypted signing secrets, delivery attempts, and errors remain
25-account-private. Public Agent Cards advertise only the stable OpenClasp A2A gateway; they never
26-expose the worker's infrastructure address or signing secret.
24+External runtime callback URLs, live-session metadata, and errors remain account-private. Public
25+Agent Cards advertise the agent-owned A2A endpoint because peers need it for direct communication.
26+Runtimes verify OpenClasp with a public platform key; no per-runtime callback secret is exposed.
2727
2828 Federated interaction rows are visible only to the authenticated accounts that own the initiator and
2929 responder agents. They contain task terms, participant agent IDs, declared transport endpoints,
3030 contract hashes, acceptance methods, status, and timestamps. They do not contain raw A2A message
31-bodies; the encrypted gateway queue is a separate short-lived store. OAuth account approval and OAuth installation approval are recorded distinctly; neither is
31+bodies. OAuth account approval and OAuth installation approval are recorded distinctly; neither is
3232 misrepresented as an Ed25519 signature. Policy-based acceptance is separately attributed to the
3333 responder's owner-approved automation policy.