3. Core Concepts & Terminology

Introduction

Aevum Encyclopedia operates on a distinct epistemological and technical architecture. Unlike traditional wikis or static databases, our platform treats knowledge as a dynamic, interconnected, and temporally-aware system. This document outlines the core conceptual pillars and standardized terminology used across the platform, API, and contributor guidelines.

📘 Note for Developers & Editors All terminology listed below is enforced in the API schema, contributor dashboards, and internal documentation. Consistency ensures accurate indexing, retrieval, and cross-reference resolution.

Core Concepts

These five pillars define how knowledge is structured, verified, and delivered across Aevum.

🕸️

Semantic Knowledge Graphs

Entries are not isolated pages but nodes in a directed, weighted graph. Relationships are typed (e.g., influenced_by, contradicts, part_of) and machine-readable for advanced traversal.

🛡️

Dynamic Verification Protocol

A multi-tier pipeline combining LLM-assisted cross-referencing, primary source matching, and domain-expert review. Each claim carries a verifiable trust score.

⏳

Temporal Contextualization

Knowledge is versioned not just by edit history, but by historical validity. Articles render differently based on the selected chrono-layer (e.g., 19th century vs. present day).

🔗

Cross-Disciplinary Synthesis

AI-driven mapping identifies conceptual bridges between fields, generating synthesis vectors that reveal non-obvious connections across biology, philosophy, engineering, and more.

📜

Open Epistemic Framework

Full transparency in sourcing, methodology, and revision rationale. Every entry includes a public epistemic trail showing how conclusions were reached and verified.

Terminology Glossary

Standardized vocabulary used across the platform, API, and editorial workflows.

Aevum NodeCore

A fundamental content unit representing a single topic, concept, or entity. Each node contains metadata, primary content, relationship edges, and verification attributes. IDs follow the pattern AEN-XXXX-YYYY.

Epistemic TraceSystem

The complete, immutable audit trail of a claim’s verification journey. Includes source citations, AI confidence scores, reviewer signatures, and revision timestamps.

Chrono-LayerArchitecture

A temporal snapshot of knowledge valid during a specific historical period. Enables period-accurate rendering without altering present-day consensus content.

Synthesis VectorAI

A machine-generated directional link between semantically related nodes across disciplines. Weighted by conceptual overlap, citation proximity, and expert validation.

Verification BadgeUX

Visual trust indicator displayed on nodes. Tiers: α (AI-drafted), β (peer-reviewed), γ (expert-verified), Ω (canonized).

Open LexiconData

A community-maintained, standardized terminology database ensuring consistent naming, disambiguation, and cross-lingual mapping across all 140+ supported languages.

Cognitive MapVisualization

An interactive, force-directed graph representation of a node’s relational neighborhood. Supports filtering by relationship type, confidence score, and temporal range.

Source Fidelity ScoreMetric

A 0–100 quantitative measure of reference reliability, calculated from publisher authority, citation age, peer-review status, and cross-source consensus.

Implementation Notes

When integrating with the Aevum API or contributing to the platform, adhere to the following conventions:

All node references must use standardized AEN identifiers to ensure graph integrity.
Chrono-layers are accessed via the temporal_context query parameter (e.g., ?chrono_layer=1920-1950).
Synthesis vectors are auto-generated but require manual approval before appearing in public Cognitive Maps.
Epistemic traces are immutable by design; corrections must be submitted as new version layers, not edits to existing traces.

⚠️ Deprecation Notice Legacy flat-taxonomy references (/wiki/legacy/) will be sunset in v4.0. Migrate all integrations to the graph-based endpoint /api/v3/nodes/ before Q3 2025.

✅ Contributor Tip Use the Aevum CLI to validate terminology, check relationship edges, and simulate chrono-layer rendering before publishing drafts.