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

[cX3po]

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.

[randomblocker]

Verified the refreshed submission against current main. All three linked projects and MIT license are live; the vendored dacs-verify commit/provenance is valid. Fresh-clone runs passed for stranger-gauntlet, verify-peer, and the convergence harness. The final diff is exactly three additive INDEX rows, preserves later catalog entries, and accurately reports the harness current three-implementation 3/3 hash convergence with decision comparison not evaluated (0/0). No blocker.