Inspiration
We identified this as an intuitive problem faced by law firms when regulatory changes occur, and figure that it would be a huge hindrance to achieve resilience.
What it does
Code Council automates the process of identifying recent changes in the law, and identifies the forms affected within a law firm. It then proposes necessary amendments to reduce the burden of lawyers and knowledge management teams.
How we built it
Frontend
Next.js 15 (App Router) · React 19 · TypeScript 5.7 · Tailwind CSS v4
LLM layer
Provider interface with three implementations - claude_cli (for demo), local (on-prem Ollama, the privacy story), mock (deterministic tests) - behind a content-addressed response cache. Swapping is one config line.
Data
SQLite for state, relations and workflow. Plain markdown is the source of truth for document content - Obsidian-compatible, git diff-readable. graph.json holds the clause-concept graph. Every scraped response is recorded to data/fixtures/, so CC_OFFLINE=1 replays a full day with no network.
Challenges we ran into
We had to reconcile the different communication styles between law students and the technical terms used by computing students.
Accomplishments that we're proud of
Coming up with a feasible idea for a real problem faced by law firms, all within a day.
What we learned
We learned important communication skills between people of different backgrounds.
What's next for Code Council
We hope for our idea to be implemented in law firms, regardless of whether we win or not.
Built With
- claude
- sqlite
- tailwind
- typescript
