From 2395b2f99c2222faaa8e88211133c9e9debe3c5a Mon Sep 17 00:00:00 2001 From: snapsynapse <57973674+snapsynapse@users.noreply.github.com> Date: Wed, 23 Sep 2026 22:27:51 -0600 Subject: [PATCH] docs: record the deferred duty-holder role decision PUB-2 leaves the EV02 answer's actor unknown because Utah's "supplier" (section 13-11-3) does not match EveryAILaw's provider role. Record the decision, its forcing function and the default in the ROADMAP's open decisions so it survives the consumed cross-repo assessment handoff. Co-Authored-By: Claude Opus 5.5 --- MANIFEST.yaml | 2 +- ROADMAP.md | 1 + docs/MANIFEST.yaml | 2 +- docs/ROADMAP.md | 1 + 4 files changed, 4 insertions(+), 2 deletions(-) diff --git a/MANIFEST.yaml b/MANIFEST.yaml index 38ec2e60..ec97aac6 100644 --- a/MANIFEST.yaml +++ b/MANIFEST.yaml @@ -483,7 +483,7 @@ files: - path: ROADMAP.md role: protocol - hash: sha256:f0c3b1b25a911ddf943ee145fd64fc482dc6d427cae4671c2a91c232baa046c3 + hash: sha256:1a81ea460e00140c80a724fd76f1d038f68b1dff507baddba53fdfc8ae17f19b note: ROADMAP.md - path: INTENT.md diff --git a/ROADMAP.md b/ROADMAP.md index 23cb0f62..00b804f6 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -265,6 +265,7 @@ Each needs a forcing function — date, dependency, or explicit trigger. | w3id.org/publedge/ns/ PR submitted? | ~6 months stable extensions | Defer long-term | | Reverse linking everyailaw.com → publedge.org? | Editorial decision after v0.1 release | One-way only (PubLedge → EveryAILaw) | | Does MCP server expose hash-verified responses? | First client that needs integrity guarantees | Current server returns raw content | +| Structured duty-holder roles on OF obligations (`duty_holder_roles`)? Utah's "supplier" is defined by reference to Utah Code §13-11-3 (consumer-transaction sellers) and does not match EveryAILaw's `provider` (AI developer or market placer), so no EveryAILaw role is borrowed. Options: PubLedge-owned role IRIs or a shared Obligation-First role vocabulary; §13-11-3 must be retained as an admission source first. | A consumer question that needs a structured actor, or an Obligation-First role-vocabulary proposal | Actor stays `unknown` in OF projections and the EV02 consumer answer; the statutory term remains in record text and receipts | ## Cross-project dependencies diff --git a/docs/MANIFEST.yaml b/docs/MANIFEST.yaml index 38ec2e60..ec97aac6 100644 --- a/docs/MANIFEST.yaml +++ b/docs/MANIFEST.yaml @@ -483,7 +483,7 @@ files: - path: ROADMAP.md role: protocol - hash: sha256:f0c3b1b25a911ddf943ee145fd64fc482dc6d427cae4671c2a91c232baa046c3 + hash: sha256:1a81ea460e00140c80a724fd76f1d038f68b1dff507baddba53fdfc8ae17f19b note: ROADMAP.md - path: INTENT.md diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index 23cb0f62..00b804f6 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -265,6 +265,7 @@ Each needs a forcing function — date, dependency, or explicit trigger. | w3id.org/publedge/ns/ PR submitted? | ~6 months stable extensions | Defer long-term | | Reverse linking everyailaw.com → publedge.org? | Editorial decision after v0.1 release | One-way only (PubLedge → EveryAILaw) | | Does MCP server expose hash-verified responses? | First client that needs integrity guarantees | Current server returns raw content | +| Structured duty-holder roles on OF obligations (`duty_holder_roles`)? Utah's "supplier" is defined by reference to Utah Code §13-11-3 (consumer-transaction sellers) and does not match EveryAILaw's `provider` (AI developer or market placer), so no EveryAILaw role is borrowed. Options: PubLedge-owned role IRIs or a shared Obligation-First role vocabulary; §13-11-3 must be retained as an admission source first. | A consumer question that needs a structured actor, or an Obligation-First role-vocabulary proposal | Actor stays `unknown` in OF projections and the EV02 consumer answer; the statutory term remains in record text and receipts | ## Cross-project dependencies