Scope & Coverage

This document defines the boundaries, methodology, and operational parameters of the Aevum Encyclopedia platform. It outlines what we cover, how we verify information, and where we draw editorial lines.

v3.2.1 — Last Updated Oct 2024 Open Licensing (CC BY-SA 4.0) 140+ Languages

Coverage Domains

Aevum Encyclopedia maintains structured coverage across 12 primary knowledge domains. Each domain is subdivided into sub-disciplines with defined depth levels and language parity targets.

Domain Depth Level Status Language Parity
Physical & Natural SciencesComprehensiveActive92%
Mathematics & LogicComprehensiveActive88%
Technology & ComputingComprehensiveActive95%
History & ArchaeologyBroadActive76%
Philosophy & EthicsComprehensiveActive81%
Arts, Literature & MediaSelectiveActive68%
Biology & EcologyComprehensiveActive90%
Social SciencesBroadActive74%
Medicine & HealthComprehensiveActive85%
Law, Policy & GovernanceSelectiveActive62%

Verification Process

Every entry undergoes a multi-stage verification pipeline before publication. We prioritize primary sources, peer-reviewed literature, and institutional data.

1

Automated Pre-Screening

AI cross-references claims against 14M+ verified academic and institutional datasets. Flagged inconsistencies trigger manual review.

2

Domain Expert Review

Subject-matter experts validate accuracy, neutrality, and contextual framing. Minimum 2 reviewers per entry.

3

Source Attribution & Citation

Every factual claim is linked to traceable, publicly accessible sources. Uncitable statements are either removed or marked as speculative.

4

Periodic Re-Audit

Entries are re-evaluated on a schedule tied to their domain volatility. High-change fields undergo quarterly audits.

Editorial Boundaries

Transparency requires clear boundaries. The following content falls outside Aevum's operational scope:

  • Speculative Fiction & Alternate Histories: Fictional universes, fan expansions, and non-factual timelines are hosted on partner archival platforms.
  • Unverified Conspiracy Theories: Claims lacking empirical or documentary evidence are excluded. Historical context may be provided neutrally.
  • Personal Advice & Medical Diagnosis: Aevum provides medical information, not clinical guidance. Disclaimer protocols apply.
  • Commercial Product Endorsements: No paid placements, sponsored entries, or marketing content is permitted.
  • Defamatory or Non-Consensual Personal Data: Privacy-first policy. Living persons are covered only within public, verifiable contexts.

Update & Review Cadence

Knowledge evolves. Our maintenance schedule ensures entries remain current without compromising verification rigor.

Real-Time
Breaking Events
Initial summaries within 2–4 hrs, full audit within 7 days
Weekly
Trending Topics
Tech, policy, and rapidly evolving sciences
Quarterly
Standard Domains
History, philosophy, established sciences
Annual
Core Reference
Foundational texts, classical literature, static data

Contribution Scope

Aevum operates as a meritocratic, open-contributor platform. Participation is governed by transparency and accountability.

🔓 Open Editing

Registered accounts can draft, suggest edits, and propose new entries. All changes enter a review queue.

🛡️ Verified Contributors

Academics, journalists, and industry professionals receive elevated trust scores and direct publishing privileges within their domains.

🌐 Translation Network

Community translators localize entries. Back-translation validation ensures semantic accuracy across languages.

📜 Code of Conduct

Zero tolerance for harassment, vandalism, or ideological manipulation. Appeals handled by independent editorial council.

Technical & API Scope

Developers and institutions can integrate Aevum's knowledge graph and content streams programmatically.

Endpoints: /v3/articles, /v3/graph, /v3/audit-log

Formats: JSON-LD, RDF/XML, CSV dumps (daily)

Licensing: Content licensed under CC BY-SA 4.0. Metadata under ODbL 1.0.

Rate Limits: 1,000 req/min (free tier), 10,000 req/min (institutional), custom SLA available.

All API responses include provenance headers, confidence scores, and version hashes for reproducibility.