PubLedge
Transparent recordkeeping protocol for fact-specific written interpretations between two parties — JIAs, RMAs, no-action letters, private letter rulings, and analogous instruments.
PubLedge is an independently maintained, versioned companion to official records. Coverage is partial; record pages identify sources and recorded review dates. Utah coverage review and known gaps.
Mapping entries associate records with obligation anchors. The clause-level provision count measures structured sections indexed, a different measure. Zero means no clause-level sections indexed in this format, not that the instrument has no obligations. Registry totals include unissued proposals; they are not counts of executed or authority-issued instruments.
Upcoming Milestones
Closest enforcement and term-end dates across the registry. Subscribe: calendar.ics.
Quick Links
Use PubLedge
Walk the hierarchical index of instruments by country, jurisdiction, authority, and type.
Every record exposes a stable identifier, a canonical URL, a record.json endpoint, and Schema.org LegalDocument markup.
Query the registry from Claude, Cursor, or any MCP client. List, filter, fetch by URL, search obligations, upcoming milestones.
Open a GitHub issue to add an instrument, flag a correction, or discuss a mapping. Contribution guidelines in
CONTRIBUTING.md.
PubLedge is not legal advice. Source policy, limitation of liability, AI-assisted-compilation notice.
Authorities can annotate a record with authority_response. Responses preserve the original record while adding the authority's own position, source, date, and optional signature.
Legal Instruments — 10 most recent
See all 18 legal instruments →
Obligations — by group
Most cross-cutting — obligations shared by the most legal instruments
requirement 4 legal instruments
Within thirty days after the end date of an RMA, the participant must file a written report with OAIP summarizing the demonstration, any incidents of harm, any legal actions, and any complaints filed against the participant in connection with the mitigation period.
requirement 4 legal instruments
An RMA participant must implement data security measures conforming to Utah Code §63A-19-102 and maintain a cybersecurity framework that is updated on an ongoing basis to address emerging threats and vulnerabilities. No statutory or common-law cybersecurity obligation is waived by the RMA.
requirement 4 legal instruments
An RMA participant agrees to hold OAIP, the relevant Division, and their agents, officers, and employees harmless from any claims, liabilities, damages, losses, or expenses arising from the participant's work performed under the mitigation.
requirement 4 legal instruments
Each Learning Lab RMA participant submits a monthly report to OAIP at `ai@utah.gov` covering user data, incidents, complaints, research findings, and any other information specified by the Office. The report is the primary ongoing accountability mechanism between participant and regulator during the mitigation period.
See all 35 obligations →