AncientOS / Luna Documentation

This is the outer documentation layer for AncientOS and the Luna Discord assistant app/interface.

AncientOS is a transport-neutral, provider-neutral governed cognition kernel for personal AI continuity.

Public shorthand: "AncientOS lets your AI relationship move with you."

What lives here

• High-level architecture
• Operational concepts
• Canonical terminology and architecture boundaries
• Visual diagrams
• Links into generated Sphinx API docs

Canonical vocabulary

Start with Canonical Terminology when naming the AncientOS kernel, Luna interface, kernel services, applications/workflows, transports, providers, and external-tool boundaries.

Use AncientOS Kernel Specification v1.0 as the constitutional architecture reference for kernel invariants, service ownership, application boundaries, provider/capability posture, memory, transport, governance, repository knowledge, and prohibited drift.

Use AncientOS v3 Architecture as the canonical application-platform architecture reference for Chen, domains, domain manifests, registry visibility, and the rule: Kernel governs -> Chen orchestrates -> Domains implement.

Use Chen Architectural Intent as the design-intent reference for why Chen exists, why Media became the first domain, and why future domains should follow resolver, broker, agents, approval, and execution boundaries.

Use Governance Kernel as the canonical architecture reference for the Objective to Loop lifecycle, authority boundaries, Oracle review model, evidence, approval, execution, and LifeVault retention.

AncientOS is the persistent governed cognition kernel around AI relationships. Luna is the current interactive assistant/personality and interface layer over AncientOS. Existing repo, service, path, API, command, environment variable, and module names may still use historical Luna naming until a future mechanical rename phase.

Runtime context

• Session Context
• Canonical Terminology
• AncientOS Kernel Specification v1.0
• AncientOS v3 Architecture
• Governance Kernel
• AncientOS Kernel Services
• AncientOS App And Component Boundary Model
• Natural Context Retrieval
• Governed Memory Architecture
• Operational Awareness And Knowledge Ingestion
• Clockwerk Dashboard
• AncientOS Knowledge Surfaces
• Operational Cognition Routing
• Governed Coordination Cognition Doctrine
• Meepo Transition Revalidation
• Naga-Siren App Boundary

Roadmap alignment

The current implementation aligns with active roadmap work in Phase 6C, Phase 8, and Phase 9:

• read-only clock and runtime awareness before authority
• governed memory and retrieval backed by artifacts
• archive-first retention and replayable operational reports
• future-ready local ingestion for Notion, Airtable, CRM, roadmap, PDF, and documentation exports