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.

// Aevum Contribution Model const corePrinciples = { transparency: "All roadmap items and RFCs are public by default", meritocracy: "Code and ideas speak louder than titles", sustainability: "Long-term maintainability over short-term features", inclusivity: "Welcoming first-time contributors and academic researchers" };

Core Repositories

Explore the primary codebases that power Aevum's AI verification pipeline, knowledge graph engine, and public APIs.

aevum-core
MIT

The foundational framework handling content parsing, citation validation, and semantic indexing.

⭐ 12.4k 🍴 3.2k TypeScript
parsing indexing core
aevum-ai-verify
Apache 2.0

Multi-model fact-checking pipeline that cross-references claims against verified academic databases.

⭐ 8.9k 🍴 1.1k Python
NLP verification pipeline
aevum-knowledge-graph
MIT

Interactive graph visualization engine and RDF/SPARQL connector for exploring entity relationships.

⭐ 6.7k 🍴 890 Rust/WASM
graph visualization webassembly
aevum-cli
MIT

Command-line interface for querying the encyclopedia, exporting datasets, and managing local caches.

⭐ 4.2k 🍴 410 Go
cli developer-tools

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
Standardizes metadata across all academic references
@dr.voss Review 2025-05-12
AE-041
Real-time Multilingual Sync Protocol
Webhook-based translation alignment system
@lin.yu Implemented 2025-04-03
AE-040
AI Hallucination Mitigation Layer
Adds confidence thresholds to generated summaries
@aevum-core Accepted 2025-03-18
AE-039
Offline Knowledge Caching Spec
Defines compression and sync for air-gapped deployments
@k.rajput Draft 2025-06-01
AE-038
Community Moderation Weighting
Revises trust scores for editor contribution tiers
@mod.team Implemented 2025-02-27
View Full Archive →

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.

1

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.

2

Submit RFC / PR

Follow the .github/CONTRIBUTING.md template. All RFCs must include motivation, specification, and backward compatibility notes.

3

Community Review

Maintainers and tagged reviewers will provide feedback. Expect 1-2 weeks for consensus building on architectural changes.

4

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