Our Open Source Philosophy
Aevum Encyclopedia is built on the belief that knowledge infrastructure should be transparent, auditable, and collaboratively maintained. We operate under the Apache 2.0 and MIT licenses, ensuring that educators, researchers, and developers can freely use, modify, and redistribute our tools without restriction.
Core Repositories
Explore the primary codebases that power Aevum's AI verification pipeline, knowledge graph engine, and public APIs.
The foundational framework handling content parsing, citation validation, and semantic indexing.
Multi-model fact-checking pipeline that cross-references claims against verified academic databases.
Interactive graph visualization engine and RDF/SPARQL connector for exploring entity relationships.
Command-line interface for querying the encyclopedia, exporting datasets, and managing local caches.
RFC Tracker
Review active proposals, track implementation status, and participate in the voting process for protocol updates.
| ID | Title | Author | Status | Created |
|---|---|---|---|---|
| AE-042 |
Unified Citation Format v3
|
@dr.voss | Review | 2025-05-12 |
| AE-041 |
Real-time Multilingual Sync Protocol
|
@lin.yu | Implemented | 2025-04-03 |
| AE-040 |
AI Hallucination Mitigation Layer
|
@aevum-core | Accepted | 2025-03-18 |
| AE-039 |
Offline Knowledge Caching Spec
|
@k.rajput | Draft | 2025-06-01 |
| AE-038 |
Community Moderation Weighting
|
@mod.team | Implemented | 2025-02-27 |
How to Contribute
Whether you're proposing a protocol change, submitting a bug fix, or adding documentation, follow these steps to get your work merged.
Open a Discussion
Start by creating an issue in the relevant repository or drafting an RFC in the proposals directory. Clear problem statements are required.
Submit RFC / PR
Follow the .github/CONTRIBUTING.md template. All RFCs must include motivation, specification, and backward compatibility notes.
Community Review
Maintainers and tagged reviewers will provide feedback. Expect 1-2 weeks for consensus building on architectural changes.
Merge & Release
Once approved, pass CI checks, and receive two maintainer approvals. Semantic versioning applies to all public APIs.
Governance Model
Aevum operates as a decentralized meritocracy. Decisions are made transparently, and roles are earned through sustained contribution.
👥 Contributors
Anyone who opens issues, submits PRs, or writes RFCs. Contributors gain write access after 3 merged substantial PRs.
🛡️ Core Maintainers
Responsible for code quality, RFC voting, and release management. Elected annually by the contributor base.
⚖️ Steering Committee
Oversees strategic direction, funding allocation, and license compliance. Meets monthly with public meeting notes.
- Transparent voting records
- Conflict of interest disclosures
- Open governance meetings