{ "generated": "2026-08-19", "as_of": "2026-08-19", "count": 10, "issues": [ { "id": "ACC-001", "title": "February 11 order implementation and adult logistics", "owner": "York trial court; the adults responsible for implementation", "first_verified": "2026-02-11", "latest_verified": "2026-08-19", "status": "Hearing scheduled", "status_group": "scheduled", "response": "The October 8 enforcement hearing is scheduled. The public record still describes disputed practical implementation of contact, therapy, transportation, and information-sharing.", "remedy": "Enter specific, adult-operable implementation terms and rule on the disputed enforcement issues promptly.", "next_review": "2026-10-08", "source_label": "Amanda Morse implementation record", "source_href": "/amanda-morse-order-implementation-record", "limits": "This public record does not itself establish contempt, motive, or every disputed fact.", "tags": "trial-court implementation child-time contact therapy scheduling", "days_open": 189, "as_of_days": 189 }, { "id": "ACC-002", "title": "Law Court usual-course directive and downstream implementation gap", "owner": "Maine Supreme Judicial Court / Law Court and the trial-court path it identified", "first_verified": "2026-05-12", "latest_verified": "2026-08-18", "status": "Escalated; oversight referral filed", "status_group": "escalated", "response": "Signed orders were entered May 12 and June 23. A public open letter followed August 17, and a Rule 10(c) intake and routing request followed August 18.", "remedy": "Clarify the action-capable path and prevent an appellate directive from becoming practically null through downstream delay.", "next_review": "2026-09-18", "source_label": "Law Court accountability record", "source_href": "/maine-supreme-judicial-court-accountability", "limits": "The June 23 order was signed for the Court; authorship and individual responsibility are not assumed.", "tags": "law-court appellate directive oversight referral implementation", "days_open": 99, "as_of_days": 99 }, { "id": "ACC-003", "title": "York Judicial Center enforcement intake, service, and scheduling", "owner": "York Judicial Center / York District Court", "first_verified": "2026-08-07", "latest_verified": "2026-08-14", "status": "Hearing scheduled", "status_group": "scheduled", "response": "The August 14 procedural order preserved one enforcement motion, dismissed the other submitted documents, required certified-mail service, and set an October 8 hearing.", "remedy": "Provide a prompt merits ruling and an implementation-ready order after the scheduled hearing.", "next_review": "2026-10-08", "source_label": "York Judicial Center + eCourt record", "source_href": "/york-judicial-center-ecourt-accountability", "limits": "The 62-day interval is an elapsed-time fact, not a claim that a specific rule required an earlier hearing.", "tags": "york judicial center district court service hearing scheduling ecourt", "days_open": 12, "as_of_days": 12 }, { "id": "ACC-004", "title": "eFileMaine notification multiplication and rejection-loop performance", "owner": "Tyler Technologies; Maine Judicial Branch configuration and governance; clerk-review workflow", "first_verified": "2026-03-30", "latest_verified": "2026-08-18", "status": "Open; performance response not yet linked", "status_group": "open", "response": "The site audit counts 878 filing-system notices and 234 rejection/return messages. One representative envelope generated 30 automated emails.", "remedy": "One authoritative envelope status, one consolidated rejection record, stable reason codes, and public performance reporting.", "next_review": "2026-09-19", "source_label": "Tyler / eFileMaine accountability record", "source_href": "/tyler-technologies-efilemaine-accountability", "limits": "Message counts are not unique filings, unique defects, or judicial decisions.", "tags": "tyler efilemaine ecourt rejection notices technology performance", "days_open": 142, "as_of_days": 142 }, { "id": "ACC-005", "title": "Maine Board of Overseers complaint handling and public-member review", "owner": "Maine Board of Overseers of the Bar / Clerk and Bar Counsel lanes", "first_verified": "2026-05-15", "latest_verified": "2026-07-27", "closed_date": "2026-07-21", "status": "Closed by dismissal; disposition disputed", "status_group": "closed-disputed", "response": "A July 21 dismissal was issued. On July 27, Bar Counsel advised that further filings should be directed to the Clerk’s Office.", "remedy": "Publish a reasoned, claim-by-claim comparison and preserve a meaningful public-member review route.", "next_review": "2026-09-01", "source_label": "Board accountability record", "source_href": "/maine-board-of-overseers-accountability-record", "limits": "A complaint is not a finding, and a dismissal is not proof that every factual conflict was resolved.", "tags": "board overseers grievance dismissal public-member review attorney oversight", "days_open": 67, "as_of_days": 96 }, { "id": "ACC-006", "title": "Rule 10(c) intake, preservation, and judicial-conduct routing request", "owner": "Board intake / Committee on Judicial Conduct routing lane", "first_verified": "2026-08-18", "latest_verified": "2026-08-18", "status": "Filed; routing disposition pending", "status_group": "pending", "response": "A public-safe summary and redacted sent-message proof are posted. No public disposition artifact is linked in the site record as of August 19.", "remedy": "Issue a written jurisdictional disposition and preserve or transmit the matter through the proper judicial-conduct channel.", "next_review": "2026-09-18", "source_label": "Rule 10(c) referral section", "source_href": "/maine-supreme-judicial-court-accountability#rule-10-referral", "limits": "The filing proves submission, not jurisdiction, investigation, agreement, or adjudicated misconduct.", "tags": "rule 10c referral judicial conduct board intake preservation", "days_open": 1, "as_of_days": 1 }, { "id": "ACC-007", "title": "Public money to court-technology performance", "owner": "Administrative Office of the Courts; DAFS procurement; Tyler; legislative oversight", "first_verified": "2016-04-15", "latest_verified": "2026-08-19", "status": "Records and performance request ready", "status_group": "ready", "response": "Cost context and user-side workflow metrics are assembled. Contract-level acceptance criteria, service obligations, invoices, defect logs, and performance reports are not yet in the public site catalog.", "remedy": "Publish contracts, amendments, invoices, acceptance testing, service levels, defects, and quarterly outcome metrics.", "next_review": "2026-09-19", "source_label": "Public money to performance record", "source_href": "/public-money-court-technology-performance", "limits": "The $100M-plus figure is contextual and combines distinct facility and statewide technology buckets.", "tags": "public money contract procurement performance tyler ecourts york", "days_open": 3778, "as_of_days": 3778 }, { "id": "ACC-008", "title": "Five operational court-reform demands", "owner": "Maine Legislature; Judicial Branch administration; rulemaking and court operations", "first_verified": "2026-08-19", "latest_verified": "2026-08-19", "status": "Public proposal; sponsor and adoption pending", "status_group": "proposal", "response": "A one-page public proposal now states five measurable reforms without presenting them as current legal requirements.", "remedy": "Secure sponsors, hearings, administrative commitments, and implementation metrics for each demand.", "next_review": "2026-11-04", "source_label": "Five operational reform demands", "source_href": "/five-operational-reform-demands", "limits": "These are policy proposals, not statements of current law or mandatory court procedure.", "tags": "reform demands implementation-ready orders rejection metrics legislature", "days_open": 0, "as_of_days": 0 }, { "id": "ACC-009", "title": "Institutional response, correction, and adverse-material ledger", "owner": "JTforME publication process; every institution invited to provide a source-based response", "first_verified": "2026-07-07", "latest_verified": "2026-08-19", "status": "Live and continuously reviewable", "status_group": "live", "response": "Responses are separated into automated acknowledgment, human acknowledgment, substantive response, action, dispute, and no public-safe response artifact linked.", "remedy": "Publish source-supported corrections, adverse material, and institutional responses without erasing the original version history.", "next_review": "2026-08-26", "source_label": "Response ledger", "source_href": "/institutional-response-ledger", "limits": "Absence from the site is not proof that no private or later response exists.", "tags": "response ledger corrections adverse material transparency", "days_open": 43, "as_of_days": 43 }, { "id": "ACC-010", "title": "Full public-safe source catalog with stable IDs and hashes", "owner": "JTforME publication process", "first_verified": "2026-08-19", "latest_verified": "2026-08-19", "status": "Published; ongoing maintenance", "status_group": "completed", "response": "The full public-safe download corpus is cataloged by stable ID, file type, page count, size, and SHA-256 hash.", "remedy": "Maintain superseded/current labels and preserve stable source IDs as the record grows.", "next_review": "2026-09-19", "source_label": "Public record catalog", "source_href": "/public-record-catalog", "limits": "Catalog inclusion does not transform party assertions or public commentary into adjudicated findings.", "tags": "source catalog hashes public record library verification", "days_open": 0, "as_of_days": 0 } ] }