Skip to main content

Module config

Module config 

Source
Expand description

In-file loop config + state — file-truths persisted through the substrate’s load_state/store_state as one JSON blob. Carries a schema version; unknown keys are ignored (serde default), so an older binary opens a newer file unchanged (proposal §7.3).

Structs§

AnalyzerConfig
Per-analyzer configuration. The file may enable/disable, raise severity floors, override params, and scope namespaces — never raise engine caps.
AnalyzerConfigUpdate
A partial update to one analyzer’s AnalyzerConfig — every field absent (None/false) leaves the stored value untouched, so the console can PATCH a single toggle. Deserialized straight from the POST /api/loop/config body.
AnalyzerSetting
One analyzer’s effective settings for the Setup view: the manifest facts plus the resolved file-config (override or manifest default).
AppliedRecord
Record of an applied recommendation: how to undo it and what to re-measure.
LoopPersisted
The whole loop persisted blob.
LoopState
Run state: the watermark that makes repeat runs cheap no-ops.

Constants§

SCHEMA_VERSION
Current persisted-state schema version.