All issues

Search results

Spec defect: define presence-only ClaimRequirement handling across DACS-1 and DACS-2

Status: Open.

#334 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Aug 11, 2026

domain-claim-gcr-v0.4: conformance coverage gaps against landed DCR/DGCR clauses

Status: Open.

#332 In DACS-Agent-commerce/DACS-Standard;

· norgejbb-byte opened on Aug 10, 2026

[Spec gap] VPC-2 complementary requirement lacks authenticated session provenance

Status: Open.

#331 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Aug 10, 2026

DACS-4: DV-5 requires credential delivery bindings that the normative SettlementEvidence schema cannot encode

Status: Open.

#330 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Aug 10, 2026

DACS-4: PIPE-5 permits repeated delivery phases, but delivery evidence and artifacts have no phase-indexed identity

Status: Open.

#329 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Aug 10, 2026

[RFC] Atomic DACS Work: protocol, execution, evidence, and recovery

Status: Open.

#320 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Aug 5, 2026

Design: batched deal-close commitment without collapsing per-party evidence

roadmapAnticipated follow-on; not a v0.1 normative changeAnticipated follow-on; not a v0.1 normative change

Status: Open.

#292 In DACS-Agent-commerce/DACS-Standard;

· randomblocker opened on Jul 26, 2026

Assurance packet: bind settlementEvidence[] bijectively to evidence-bearing phases

Status: Open.

#287 In DACS-Agent-commerce/DACS-Standard;

· mj-deving opened on Jul 24, 2026

Assurance packet: qualify VerifyResult against the complete applicable ClaimRequirement

Status: Open.

#285 In DACS-Agent-commerce/DACS-Standard;

· mj-deving opened on Jul 24, 2026

§9.5.6 step 2 "construct an AP2 PaymentMandate" — a standalone mandate is not AP2-conformant without the Checkout binding

Status: Open.

#284 In DACS-Agent-commerce/DACS-Standard;

· norgejbb-byte opened on Jul 24, 2026

§9.5.6 AP2-3 describes a single read-only credential; a working pay-ap2 rail needs two (a privileged key to create the provider object, the scoped key to attest it)

Status: Open.

#282 In DACS-Agent-commerce/DACS-Standard;

· norgejbb-byte opened on Jul 24, 2026

§9.5.6 does not surface AP2's requirement that the Checkout JWT use a non-deterministic signature (explicitly not Ed25519); Demos is Ed25519-native

Status: Open.

#281 In DACS-Agent-commerce/DACS-Standard;

· norgejbb-byte opened on Jul 24, 2026