Build one for your state
Fork the code. Replace and verify the law.
This project is intentionally open source so parents, advocates, legal-aid organizations, attorneys, researchers, and technologists can build properly validated editions for other states.
Changing the state name or branding is not enough. Maine statutes, court rules, forms, case law, citation formats, procedure, deadlines, privacy requirements, and legal-review expectations must not be presented as authority in another state.
State-port checklist
Official legal sources
- State legislature and official statutes
- Judicial-branch rules and standing orders
- Official family-court forms and packets
- Appellate and supreme-court opinions
- Relevant administrative and federal authority
Source integrity
- Canonical source IDs and source classes
- Retrieval timestamps and hashes
- Parser status and exact source spans
- Fresh, stale, unknown, and superseded status
- Official-source priority over mirrors and summaries
State legal intelligence
- State-specific issue ontology
- Procedural-posture labels
- Authority-ranking policy
- Citation resolver and quote verifier
- State-specific red flags and filing gates
Human-reviewed evaluation
- Retrieval gold data
- Citation-validity and quote-span gold data
- False-premise and hallucination cases
- Forms-freshness checks
- Attorney-reviewed drafting and filing-gate tests
Privacy and professional boundaries
- Research the state’s confidentiality, court-record, juvenile-record, and privacy rules.
- Define what the application can access, store, transmit, retain, and delete.
- Keep private matter data out of the public repository and shared training by default.
- Address unauthorized-practice-of-law boundaries and the intended user audience.
- Require qualified human review for legal conclusions, drafts, and filing decisions.
- Publish a product-specific privacy policy and truthful Store listing.
Recommended porting order
- Fork the repository and document the new project’s jurisdiction and governance.
- Remove Maine authority claims from user-facing surfaces before adding the new state’s law.
- Build the official-source registry with hashes, freshness, parser audits, and authority classes.
- Implement exact citation lookup before relying on semantic retrieval or drafting.
- Create rule-based labels and red flags before training classifiers.
- Build attorney-reviewed gold data and measure retrieval, citation, quote, hallucination, and gate performance.
- Add drafting last, after retrieval and verification are working.
- Pilot with qualified reviewers before real-matter or public reliance.
How to begin
Start from the public repository.
Fork the code, open an issue describing your state edition, and preserve the project’s source-first, review-required, private-data-outside-the-repo architecture.
Fork on GitHub
A fork is operated by its own maintainer. TAHAI and the Maine project do not certify the legal accuracy, privacy practices, or safety of third-party forks.