Architecture
How applied ASH runs as governed software: the Forsetti host boundary, the ASH Pattern System, and the Aeostara health layer — app-owned systems, capability-governed and host-mediated.
Forsetti is the application framework Sigil is built inside — not the thesis, not a peer, not a plugin, and not an external library.
Layers, not peers. ASH Cosmology is the subject; Raven Forge applies it; Sigil is the first working demonstrator; and Forsetti is the application framework inside which Sigil and its app-owned systems are built. ASH state, WRW canon, and Aeostara are implemented within that framework — not parallel to it. SigilForsettiBootstrap.makeHostArtifacts assembles a module registry, a capability policy, a service container, and the runtime.
Four app-owned modules
Sigil exposes its capabilities through app-owned Forsetti modules, each declaring an empty capability set — so the Release allow-list is the host’s available surface.
SigilCoreModule
App workspace and primary Sigil interaction.
CanonCodexService
PersonalCodex and canon identity access.
ASHPatternService
State, transition, topology, diagnostics, generation plan.
AeostaraConfigHealth
JSON/config validation, safe-only recovery, audit.
The shipped build reaches only an allow-list
DEBUG
AllowAll — the full host surface, for development ergonomics.
Release
FixedCapabilityPolicy allow-list: storage, secureStorage, telemetry, viewInjection, uiThemeMask. Nothing else is reachable.
Sealed internals, editable app surfaces. Sigil is an application built inside the Forsetti Framework. Its ForsettiCore and ForsettiPlatform internals stay sealed — private framework code is never modified for app-specific behavior — while Sigil’s own implementation lives in app-owned, editable surfaces inside the framework: modules, manifests, services, host composition, and generated scaffolding (RFSigilForsettiModules, RFCoreModels, RFSigilPipeline, RFMeaning, RFExport, and App/), wired in through public Forsetti contracts.
ASH, as software contracts
An implemented, app-owned layer. Its runtime, DefaultASHPatternRuntime, reuses the same ASHCoreEngine the shipping pipeline runs — so the published contract and the live engine cannot drift apart.
State & operators
ASHState (0…511), ASHCodeword, ASHOperatorSet — 9-bit GF(2) state and doubly-even codewords.
Topology & plan
ASHTopologyReport and ASHGenerationPlan — a stable plan digest, produced before any geometry materializes.
Runtime & conformance
evaluateState, generateTopology, makeGenerationPlan — plus an optional conformance report proving the running pipeline matches the contracts.
Self-healing export & JSON health
Where the Pattern System governs state and generation, Aeostara governs validation, recovery, verification, and audit — running diagnose → make a safe-only recovery plan → verify → audit, and never mutating the input artifact.
Recover if derivable
Missing optional metadata derivable from canonical state is recovered; a stale schema with a known deterministic migration is migrated.
Halt, never guess
Missing required identity/hash or an out-of-range mesh index is unrecoverable — geometry is never repaired.
Safe-halt & fail
Unknown schema/version safe-halts for human review; corrupt JSON fails outright with no guessing.
It validates wrw_personal_codex_v3, rf.sigil_mesh_export.v1, and rf.export_metadata.v1 — proof that applied ASH can govern reliability, not only generation.
A host boundary makes the proof reusable
Game & lore tools
Character, faction, and quest systems on the same deterministic identity.
Creator tools & readers
Canon-aware artifact generation and lore readers.
APIs & infrastructure
Diagnostics dashboards, asset/mesh exporters, character/creator APIs, symbolic software infrastructure.