Leci Documentation Home
Leci Documentation Home
Section titled “Leci Documentation Home”What this documentation covers
Section titled “What this documentation covers”This documentation explains how Leci works today, what is planned next, and how to contribute safely to a legal-data-first platform. It is designed for developers, project stakeholders, and AI agents that consume project context.
Who should start here
Section titled “Who should start here”Use this page as the entry point if you are:
- a contributor setting up the project for the first time;
- a reviewer validating architecture and roadmap consistency;
- an integration owner evaluating API-readiness and legal data reliability;
- an AI agent requiring structured, explicit, and machine-parseable context.
Recommended reading paths
Section titled “Recommended reading paths”Fast onboarding path
Section titled “Fast onboarding path”getting-started/introductiongetting-started/quickstartdevelopment/setup
Architecture and implementation path
Section titled “Architecture and implementation path”architecture/overviewarchitecture/stackfeatures/index
Planning and risk path
Section titled “Planning and risk path”roadmap/indexroadmap/milestonesplanning/PREMORTEM.md
Current maturity in one paragraph
Section titled “Current maturity in one paragraph”Leci currently provides strong database and migration foundations for Brazilian federal legislation, including structured legal entities, search indexes, and revision audit primitives. Product-facing capabilities such as richer UI flows, internal API groups, and ingestion automation are roadmap-driven and should be treated as planned scope until code is present.
Source-of-truth policy
Section titled “Source-of-truth policy”When docs and implementation diverge, trust this order:
- Source code (
src/,drizzle/,scripts/) - Configuration files (
package.json,.env.example, build configs) - Planning artifacts (
docs/planning/*) - Narrative pages in docs