Skip to content

Record the deferred duty-holder role decision #19

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

Merged
snapsynapse merged 1 commit into from
Sep 30, 2026
Merged

Record the deferred duty-holder role decision #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion MANIFEST.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,7 +483,7 @@ files:

- path: ROADMAP.md
role: protocol
hash: sha256:f0c3b1b25a911ddf943ee145fd64fc482dc6d427cae4671c2a91c232baa046c3
hash: sha256:1a81ea460e00140c80a724fd76f1d038f68b1dff507baddba53fdfc8ae17f19b
note: ROADMAP.md

- path: INTENT.md
Expand Down
1 change: 1 addition & 0 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion docs/MANIFEST.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,7 +483,7 @@ files:

- path: ROADMAP.md
role: protocol
hash: sha256:f0c3b1b25a911ddf943ee145fd64fc482dc6d427cae4671c2a91c232baa046c3
hash: sha256:1a81ea460e00140c80a724fd76f1d038f68b1dff507baddba53fdfc8ae17f19b
note: ROADMAP.md

- path: INTENT.md
Expand Down
1 change: 1 addition & 0 deletions docs/ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading