DACS Forge v0.1.1 — public qualification evidence
This source-only patch preserves the v0.1.0 fixture/no-spend runtime and makes
its independent-consumer and extension-only reference-fork qualification
directly acquirable from the public release.
Evidence correction
- The standalone consumer source is a complete Git bundle at commit
a8e307a34a143357dc3e74203854ad1fa9918027. It imports the built public Forge
entrypoint and no producer, lifecycle, fixture, database, handler, service, or
Forge source module. Its 32-test positive and mutation matrix passes against
the public v0.1.0 build and the published serialized graph. - The Counterparty Evidence reference fork is a complete shared-history Git
bundle at commite8b2f2cc2fd7e18dc222488866218d5d9b5e7212, tree
954cf9a3efd1eb795e2fa1b47bbd1767ce1ac458. Its exact product authority is
separately bundled at863ff5b0bfecf1e40a7a84d02cf1021ffa2f5866. - The qualification index binds every report,
source revision, asset locator, and digest. The release manifest,
compatibility record, and capability profile all use the same
qualified-public-evidencedisposition.
Boundary
Counterparty Evidence emits fixture observations, source descriptors,
timestamps, hashes, availability, ambiguity, and explicit limitations. It does
not issue KYB certificates, establish source truth, make compliance or sanctions
decisions, or use live sources.
The Forge-local WorkProductReceipt remains non-normative. DACS-2 Delivery,
DACS-4 SettlementEvidence, and the DACS-5 graph remain the interoperability
boundary. This release adds no registration, deployment, payment, transfer,
production, certification, steward endorsement, Community listing, or adoption
claim.
The tag is annotated but is not claimed as cryptographically signed. No
maintainer signing identity and consumer trust policy are configured. Immutable
GitHub release attestation and public asset readback remain mandatory.