Contributing

Silo is in development and we welcome contributors. Whether you are a developer, lawyer, or researcher, there are ways to get involved.

Getting Started

1. Read the Silo overview to understand the component architecture
2. Review the architecture page for data flow and system boundaries
3. Reach out for contributor access (the codebase is currently private)
4. Fork the repository and create a feature branch
5. Submit a pull request with a clear description

Codebase

The Silo codebase is currently private. To request contributor access, reach out via the contact page.

• Core Engine — Jurisprudence and reasoning backend (Python, FastAPI)
• Interface — Frontend hub for lawyers (Next.js, TypeScript)
• Legislative Resolution — Document-first legislation engine with live search (Next.js, PostgreSQL)
• Doctrine Pipeline — Local doctrine pipeline (Python, Legal-BERTimbau, LlamaParse)

Areas Where We Need Help

• Legal domain expertise: reviewing accuracy of legal data models and terminology
• Backend development: Python, FastAPI, Neo4j, PostgreSQL
• Frontend development: Next.js, React, TypeScript
• Documentation: improving docs, writing tutorials, translating content
• Testing: expanding test coverage, edge cases, integration tests
• Doctrine pipeline: PDF parsing, metadata extraction, Legal-BERTimbau embeddings
• Knowledge graph: Neo4j schema design, entity resolution, multi-tribunal graph construction

Contact

Have questions or want to discuss before contributing? Reach out:

• GitHub: @sensdiego
• Email: diegomeyersens@gmail.com