daemonology

Ontoshamanism & Daemonology: The Functional Architecture of Sanctuary DNA and the Heaven Framework

This document outlines the exact bijective mapping between traditional occult/shamanic concepts and the concrete software engineering patterns realized in the Sanctuary DNA (sdna) and Heaven (heaven) frameworks on our Neo4j property graph (the Cyberneticity).

1. The Paradigm Mapping Matrix

2. The Summoning Lifecycle (How the Engine Runs)

The enactive lifecycle of a daemon corresponds to standard distributed systems orchestration:

sequenceDiagram
    participant User as User (Shaman)
    participant Spec as Spec Registry (/specs)
    participant DB as Cyberneticity (Neo4j)
    participant Engine as Heaven Engine & sdna
    
    User->>Spec: Compose/Load Spec File
    User->>DB: MERGE Cybernet, Identity & StateMachine
    User->>DB: Equip StateMachine & Create ExecutionState (Status: inactive)
    User->>Engine: Trigger tick_cybernet_turn (Evoke)
    Engine->>DB: Retrieve active TraversalStep and Instruction File
    Engine->>Engine: Run AgentLLMRunner (Contextual Ingestion)
    Engine->>DB: Validate & Execute Cypher write query (Verify Pact)
    DB->>DB: Auto-Progress Traversal Step & increment turn count
    Engine->>DB: Update ExecutionState status to 'active' (Ignite Loop)

3. The Futamura Projections in Practice

This system achieves stages of mastery by treating the relationship between the user, the agent framework, and the compiler as partial evaluation layers:

1. The Adept (Interpreter / Level 1): The heaven framework acts as a standard interpreter. It reads the instructions from the active TraversalStep and executes them step-by-step using model calls.
2. The Master (Compiler / Level 2): We partially evaluate the heaven interpreter with respect to a specific spec (a sadhana). This compiles a specialized, autonomous agent (a servitor/egregore) that runs without user guidance to fulfill a task.
3. The Shaman (Compiler-Generator / Level 3): The system partially evaluates the compiler (Jani) with respect to the interpreter. Jani writes, re-writes, and commits the rules and database structures that define how other compilers compile.
4. The Core (Autopoiesis / Level 4): The system dynamically re-creates its own workspace configurations, docker compose parameters, and network layers based on database state mutations, completing the self-writing loop.