CauslEngineMode: "rust-ssot" | "js-ssot" | "ts-floor"

How a graph arrived at its CauslEngine — the construction route (#295).

  • 'rust-ssot' — built through this subpath with the Rust core canonical. Since 0.5.0 the ONLY mode a wasm construct on this subpath produces.
  • 'js-ssot'inert since 0.5.0; removed in 0.6.0. It meant: built through this subpath, but pinned to the wrapped TS closure as the source of truth (the §18A.7 Criterion 5 floor opt). #280 removed the engine: 'js-ssot' option that selected it and the WasmEngineMode type that named it, so no graph reports this value any more. The member stays DECLARED for one release for the same reason onCauslCapabilityFallback does: an adopter's exhaustive switch over this union keeps compiling.
  • 'ts-floor' — no wasm artefact is canonical for this graph. Still reachable: causlEngineOf() reports it for any Graph this subpath did not build, which after causl/causl-wasm-ts#279 slice S12 means a graph built somewhere other than this package. The three adopter-facing routes that used to reach it — a bare createCausl() with nothing preloaded, createCausl({ engine: 'js-ssot' }), and the §18A.13.1 capability degrade — now throw.

Declared independently of the (now removed) WasmEngineMode rather than aliased to it, on purpose: an alias would have taken this public type down with it.