The supported extension surface is Sigil plus the embedded shell. Deferred work lives in docs/ARCHITECTURE_PHASE1.md.
boot.sigilis loaded at startup byghost_sovereignsigil_corecompiles.sigilsource into.sigbcPOST /api/sigilexecutes live Sigil and accepts shell control commands/commit_abstractions ...stages explicit abstraction distillationGET /?channel=chatopens the chat WebSocket bridge--project-shard=<id>orGHOST_PROJECT_SHARD=<id>switches the committed shard you are modding against
The runtime resolves boot.sigil through build_options.project_root, which is compiled into the binary.
For shard-local experimentation:
begin scratch- send Sigil or
/commit_abstractions ... committo make staged work live, ordiscardto throw it away
For shard-local checkpointing outside scratch:
snapshot- make live changes
revertorrollbackto restore the snapshot
/commit_abstractions is not implicit learning. It is an explicit command, it requires an active scratch session, and its staged output only becomes live on commit.
Sigil:
POST /api/sigil
The request body can be raw Sigil text or JSON with a script or sigil field.
Chat:
GET /?channel=chat
Send JSON text frames such as:
{"type":"input","text":"Describe the current resonance field."}Working VM keywords:
MOODLOOMLOCKSCANBINDETCHVOIDTEST
Working shell control commands:
begin scratchdiscardcommitsnapshotrevertrollback
Working LOOM commands:
VULKAN_INITCPU_ONLYTIER_1TIER_2TIER_3TIER_4
Compile manually when needed:
./zig-out/bin/sigil_core boot.sigil- Binary plugins
- Hot-loaded
.dllor.somodules - Automatic plugin discovery on boot
- A separate productized plugin API in the shell
- Automatic semantic distillation without an explicit
/commit_abstractionscommand - A user-facing runtime selector for exploratory reasoning mode
The repo contains compatibility and platform helpers outside this surface. They are not the current modding API.