Skip to content

18. Appendix

18.1. Environment variables

VariableDefaultUsed byEffect
EIGENIUS_DB(none, in-memory)eigenius servePath to the RocksDB persistence directory
EIGENIUS_HOMEworkspace root in dev / /opt/eigenius in containerseigenius env buildBase path for resolving the default Julia worker source ($EIGENIUS_HOME/julia/runtime-worker/). Overridden per invocation by --worker-source-dir.
EIGENIUS_ORCHESTRATOR_ENDPOINT(none)eigenius serveKernel’s URL for the orchestrator (alternative to --orchestrator)
EIGENIUS_KERNEL_ENDPOINThttp://localhost:50051OrchestratorEndpoint the orchestrator uses for kernel callbacks (read/query host imports)
EIGENIUS_ORCHESTRATOR_PORT8080OrchestratorPort the orchestrator binds to
EIGENIUS_MOCK_LLMfalseOrchestratorWhen true, swap real LLM handlers for canned mock responses
ANTHROPIC_API_KEY(none)OrchestratorRequired when EIGENIUS_MOCK_LLM is unset
EIGENIUS_EXTFILE_CACHE_DIR(none)eigenius data provision, kernel recomputeDepot extfile-cache root where pinned external files materialize (<cache>/<sha256>/<name>). Default cache root for data provision when --cache-root is omitted; the directory the kernel reads for native file-backed SampleSet recompute (D53 §6.1 / §7).
EIGENIUS_OXEN_BINoxenRuntime substrate (Oxen fetch)Path to the prebuilt oxen client binary used to fetch oxen:// references (D53 §2).
EIGENIUS_OXEN_SCHEMEhttpsRuntime substrate (Oxen fetch)URL scheme the Oxen client uses for the remote host (set http for a local/plaintext Oxen server).
OXEN_CONFIG_DIROxen client defaultRuntime substrate (Oxen auth)Oxen config dir holding auth_config.toml (per-host bearer token). The token is substrate-side only and never enters a worker image (D53 §10).
RUSTFLAGS(none)cargoRUSTFLAGS="-D warnings" upgrades clippy warnings to errors (used by just check)

CLI commands also accept --endpoint <url> as an alternative to setting an env var; the flag takes precedence.

18.2. File and directory locations

LocationContents
target/debug/Workspace build artifacts (debug profile)
target/debug/eigeniusThe CLI binary
target/release/Workspace build artifacts (release profile)
~/.cache/deno/Deno-cached TypeScript dependencies
<rocksdb-path>/ (e.g. /var/lib/eigenius)Persisted state when serve --db is used
/var/lib/eigenius/substrate-depot/Runtime-substrate depot path (chapter 11). Bind-mounted into the orchestrator at the same path so worker UDS sockets are reachable from both host and orchestrator container.
julia/runtime-worker/Julia worker source baked into substrate env images
julia/common/EigeniusJuliaCommon/Substrate-side Julia utilities shared across institutions
julia/institutions/<institution>/Per-institution handler package (Project.toml + src/) and chain declarations
julia/comorphisms/Cross-institution comorphism declarations

18.3. Default ports

PortServiceConfiguration
50051Kernel gRPCeigenius serve --port <N>
8080Orchestrator HTTPEIGENIUS_ORCHESTRATOR_PORT=<N>

18.4. The four embedded ontology layers

Loaded at every kernel startup; their parent-pointer chain forms the bootstrap:

LayerIRI baseSource
coreurn:eigenius:coreontologies/core/core-ontology.json
programurn:eigenius:programontologies/program/program-ontology.json
reflectionurn:eigenius:reflection(embedded — reasoning traces, epistemic categories)
institutionurn:eigenius:institution(embedded — institution and comorphism classes)

When serve --db <path> is used, a SHA-256 manifest of these is written on first start and verified on subsequent starts (drift refusal — see chapter 6 §6.3).

18.5. Source index — implementation files referenced in this guide

CLI

  • cli/src/main.rs — every subcommand, the Commands enum is the source of truth for command shapes

Kernel

Storage backends

Runtime substrate (chapter 11)

Examples

WASM example components (examples/wasm-*) were removed on 2026-07-08 along with the rest of WASM extensibility.

Orchestrator

Demo scripts

Deployment

Build / task automation

  • justfile — task recipes (build, test, check, up, serve, etc.)

The full design-document set lives in docs/design/.

18.7. Phase status

The platform is currently complete through Phase 11e (see top-level README.md):

  • Phases 0–9: kernel + orchestrator + LLM integration + WASM extensibility + persistence + tasks
  • Phase 10: kernel completeness (ontology-as-types resolution)
  • Phase 11a–e: type theory extensions (Map/Reduce, inductive types, institution decide procedures, comorphisms, ESL+EigenQL surfaces)

Next: Phase 12 (worked institution examples — life-science demos drawing on Phase 11’s surface).


Return to README.