Skip to content

DACS Forge v0.1.0 — Product Seal

Choose a tag to compare

@mj-deving mj-deving released this 30 Jul 18:15
· 64 commits to main since this release
Immutable release. Only release title and notes can be modified.

DACS Forge v0.1.0 — Product Seal

DACS Forge is a forkable DACS reference service and conformance kit for building specific service agents. v0.1.0 is its first supported source release and remains strictly fixture/no-spend.

What ships

  • A deterministic lifecycle from signed Listing and bilateral Vet through Agreement, settlement, Delivery, independent verification, and role-local DACS-5 bundles.
  • Exact binding of the executed service handler's canonical output bytes into Delivery, receipt, persistence, restart replay, and the terminal artifact graph.
  • A narrow service-fork contract: metadata, schemas, handler, and fixtures under service/; protocol, persistence, signing, verification, and the release rig remain Forge-owned.
  • One qualified direct upgrade edge from the immutable, unsupported v0.1.0-preview.2 release through shared Git history.
  • Source archives generated by GitHub from the annotated v0.1.0 tag. No package, binary, or container image is distributed.

Release identity and verification

  • Source commit: 81507c792c158a5782ea67e6c43c873d49356903
  • DACS profile: immutable DACS-Standard v0.4 at 4bb9e48a1095ab32c06c25b7c0b52018d3ce4091
  • Direct predecessor: v0.1.0-preview.2 at 0c6e92cc707c62db0ca3c9627d59bb95ba9970e9
  • The base service and an extension-only Counterparty Evidence fork passed the complete pinned release rig in fresh, separate clones. The fork differs from Forge only in the declared service/ extension paths.
  • Publication requires green CI on the exact release commit, immutable-release attestation, and credential-free public clone readback.

The machine-readable release manifest, capability profile, compatibility disposition, and upgrade guide define the exact supported surface.

Boundaries

This release does not provide or claim live registration, live payment, a production deployment, normative DACS conformance authority, certification, steward endorsement, Community listing, or adoption. It must not be used for live value transfer.