Skip to content

docs: add DACS Forge to community index #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mj-deving wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: add DACS Forge to community index #69

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
89a1b0f
docs: add DACS Forge to community index
mj-deving Aug 1, 2026
25951ff
Merge Community main into Forge index submission
mj-deving Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions INDEX.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ The catalogue of community projects, in-tree and external. Conformance status va
|---|---|---|---|---|---|
| agent-commerce-demo | KyneSys Labs | Full lifecycle (DACS-1..5); exercises `pay-x402` end-to-end (buyer-side EIP-3009/Permit2, USDC on Base) | `vector-tested` (golden vectors, DACS-Standard `conformance/`) | TBD on publication | **Canonical** (steward reference implementation; repo currently private, publication pending) |
| [dacs-directory](./reference-implementations/dacs-directory) | [randomblocker](https://github.com/randomblocker) | Community agent catalog and browser UI: DACS-1 §6.3.6 catalog API and ListingSummary/ReputationHint shapes; DACS-1 CCI identity resolution; DACS-5 §10.4 bundle and referenced-artifact verification; §10.5 reputation derivation | `exercises-spec` — implementation tests cover security boundaries and verification policy; no claim of full golden-vector coverage | MIT | In-tree |
| [DACS Forge](https://github.com/mj-deving/dacs-forge) | [mj-deving](https://github.com/mj-deving) | Independent Bun/TypeScript fixture/no-spend service lifecycle against DACS v0.4: CORE §B.1/B.2/B.7 canonical identity, JSON, and signatures; DACS-1 Listing and identity checks; DACS-2 self-signed DeliveryAssertion/VerifyResult; DACS-3 agreement and commitment; DACS-4 settlement and attested delivery; DACS-5 role-local bundles and producer-independent consumer verification. Service forks own five bounded extension paths; Forge owns admission, SQLite persistence, restart/replay, and evidence packaging | `vector-tested` — passes the named v0.4 canonicalize, Listing unknown-field retention, signature-value encoding, settlement-finalization, and DACS-5 bundle-convergence vectors. The immutable [v0.1.1 Product Seal](https://github.com/mj-deving/dacs-forge/releases/tag/v0.1.1) publishes digest-bound independent-consumer and extension-only reference-fork evidence; this is not full normative conformance, certification, or live-commerce qualification | MIT | External — [run exact v0.1.1](https://github.com/mj-deving/dacs-forge/blob/2d2543c8724a4c998daebbca8322aa75e2da889a/README.md#reproduce-the-supported-release) with Bun 1.3.9 on Linux; no secrets required; fixture run performs no live registration, anchoring, broadcast, transfer, or reputation write |
| [pathos-dacs-ref](https://github.com/cX3po/pathos-dacs-ref) | PATH-OS Labs | DACS-5 §10.4 AttestationBundle + JCS canonical form §B.2 (signed-scope hashing); §10.4.2/3 two-sided anchoring + divergence; DACS-1 identity verify, DACS-2 recipe vetting, DACS-3 sealed-bid, DACS-4 settlement-evidence; selective-disclosure / consent / dispute-evidence layer | `vector-tested` — reproduces the DACS-Standard `conformance/` golden AttestationBundle hashes (§10.4 signed scope + canonical form §B.2); `exercises-spec` for the rest (two-sided anchoring, DACS-1/2/3/4, disclosure/consent/dispute) | MIT | External |
| [dacs-verify](https://github.com/mj-deving/dacs-verify) | mj-deving | Independent Bun/TypeScript verifier and conformance runner for DACS v0.1: canonical JSON + content hashes (§B.2), domain-separated signatures (§B.7), DACS-1 identity/listing checks, DACS-2 vetting primitives, DACS-3 agreement checks, DACS-4 settlement evidence, DACS-5 AttestationBundle/reputation verification, plus a proposed DACS-X dispute/disclosure prototype. **Generates DACS-Standard's published §14 golden vectors** — named as the `generator` in `conformance/MANIFEST.json` | `vector-tested` — passes 186 DACS-Standard golden conformance checks across DACS-1..5 verifier surfaces; DACS-X dispute/disclosure code is `prototype` / non-normative | MIT | External |
| [stranger-gauntlet](https://github.com/cX3po/pathos-dacs-ref/tree/main/showcase/stranger-gauntlet) | PATH-OS Labs | A2A trust showcase — one Shopper vets three stranger vendor agents through the DACS-5 §10.4.1 AttestationBundle acceptance verifier: two honest bundles → `accept`; a bundle tampered *after* signing → `reject` with the decisive check named. Exercises §10.4.1 signed-scope hashing (R5-1 anchoredByRole-excluded canonical form) and §7.5.1 do-not-collapse (`accept` vs `reject`/`indeterminate`) | `exercises-spec` — demonstrates the §10.4.1 verifier catching a counterfeit built from local fixed-seed fixtures (not named DACS-Standard vectors); the underlying verifier + canonical hasher are the vector-tested pathos-dacs-ref. Deterministic, zero-network, no deployed identities | MIT | External |
Expand Down