EIDOS Explorer — Developer Reference

This reference manual is compiled from the Documentation Knowledge Model (KM). All content is derived from verified source files — no assertions are made from memory.

Architecture at a Glance

EIDOS Explorer is a distributed graph service with three data layers:

.eidos ZIP (read-only base)
    +
mutations/ overlay (JSON-LD, mutable)
    =
Effective Graph (in-memory, rebuilt on demand)

Core Concepts

• Effective Graph — the merged in-memory view that all APIs query
• Overlay — the mutable write layer on top of the immutable base
• Domain — independently deployable subtree served by one backend instance

Key Workflows

• Mutation Pipeline — preview → confirm → commit → cache-invalidate
• Composite View Assembly — how base + overlay merge correctly
• Cache Coherence — three-tier cache lifecycle
• Cross-Domain Resolution — routing to secondary backends
• Import Pipeline — Excel batch import via preview → commit

Invariants

System-wide guarantees that all implementations must preserve:

• Overlay Wins on Conflict
• Atomic Write
• Domain Routing Key
• Preview Before Commit
• Deterministic UUID