Skip to content

index: A2A trilogy — stranger-gauntlet, verify-peer (apps) + convergence-harness (tool)#5

Open
cX3po wants to merge 1 commit into
mainfrom
submit/a2a-trilogy-reference-impls
Open

index: A2A trilogy — stranger-gauntlet, verify-peer (apps) + convergence-harness (tool)#5
cX3po wants to merge 1 commit into
mainfrom
submit/a2a-trilogy-reference-impls

Conversation

@cX3po

@cX3po cX3po commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Submission checklist

  • Added as INDEX rows (external projects)
  • Each entry states what it is + DACS surface (modules + §)
  • Conformance declared honestly: exercises-spec for all three (see scope below)
  • Runs from a fresh clone (each README documents npx tsx …)
  • License declared (MIT, External)
  • No secrets (fixed-seed local keypairs; no keys/endpoints/non-test mnemonics)

What & why

Three external entries answering the showcase-era ask — implementation that exercises the standard:

  • stranger-gauntlet (Reference impls & apps) — the A2A "trust a stranger's agent" problem at the artifact layer: one Shopper, three stranger vendor agents, the §10.4.1 referee catches a bundle tampered after signing — and names the decisive check.
  • verify-peer (Reference impls & apps) — an A2A peer-trust gate binding an AgentCard's claimed identity to the identity the §10.4.1 bundle proves; an impostor whose card and bundle disagree is declined. The card is discovery evidence; the bundle is trust.
  • convergence-harness (Tools) — a cross-impl convergence runner for the §10.4 bundle surface, now carrying an independent 2nd adapter over @mj-deving's dacs-verify (already indexed here), vendored verbatim + attributed → a genuine two-impl matrix: canonical-hash convergence 3/3, no decision divergence.

Honest scope

All three are exercises-spec. The showcases run local fixed-seed demo fixtures and the harness runs its own in-repo §10.4 corpus — none run named DACS-Standard conformance vectors, so none claims vector-tested. The verifyBundleV1 + canonical hasher they call are the vector-tested pathos-dacs-ref verifier already indexed. Nothing here is "certified" or "conformant."

Referee, not authority

The convergence harness reports convergence evidence; it does not certify conformance. DACS-Standard owns what "DACS-conformant" normatively means; the harness links to it rather than speaking for it. dacs-verify is credited as the independent 2nd implementation; its agreement makes the convergence real, not a self-report.

…ergence-harness (tool)

Three external entries (cX3po / PATH-OS Labs), all exercises-spec, answering the
showcase-era ask. convergence-harness credits mj-deving's dacs-verify as the
independent 2nd impl (vendored @10aefa7f, MIT) — genuine 2-impl canonical convergence 3/3.
Referee-not-authority: reports convergence evidence, does not certify conformance.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant