How wordhippo757/global-law works
Global Law combines jurisdiction-level law repositories into a dated Git history, then exposes that history through command-line and MCP queries and a visualization suite. The principal user workflow is to ask about a provision or jurisdiction on a date, resolve the relevant history, and return the text or change information with the record’s coverage limits. The README documents additional citation, precedent, and case-timing tools. Source excerpts are partial, so visualization internals and several MCP relationships are represented only where documented or indexed.
Main entry points: build.py History builder · law.py Date-based law queries · compose.py Visualisation composition · mcp_server.py MCP tools and prompts
Components 13
Law corpus
- Jurisdiction repositories
- Corpus checks
tools/check_corpus.py
Global history
- History builder
tools/build.py - Dated law history
Law access
- Date-based law queries
tools/law.py - MCP tools and prompts
tools/mcp_server.py
Research visualisations
- History analyses
visualisations/src/analysis2.py - Visualisation composition
visualisations/src/compose.py - Interactive figures
visualisations/src/part_global_js.js
Other components
- Corpus maintainers
- CLI user
- MCP client
- Researcher
Connections 11
- Corpus maintainers → Jurisdiction repositories: maintains
- History builder → Corpus checks: runs checks
tools/build.py - History builder → Jurisdiction repositories: reads histories
- History builder → Dated law history: builds chronology
- CLI user → Date-based law queries: queries law
- Date-based law queries → Dated law history: reads dated state
tools/law.py - MCP client → MCP tools and prompts: requests tools
- MCP tools and prompts → Date-based law queries: uses law queries
tools/mcp_server.py - Researcher → Visualisation composition: views findings
- Visualisation composition → Interactive figures: assembles figures
visualisations/src/compose.py - History analyses → Visualisation composition: supplies findings