Expand description
Optional module config-gate control bodies.
A module opts in by listing CONFIG_REVIEW_OP in HELLO control_ops, not
by changing its manifest. Send these operations only after HELLO_ACK advertises
CONFIG_GATE_CAPABILITY. Without it a module keeps its existing file reader;
with it, a refusal must never cause a fallback to unapproved files.
These standalone bodies leave the existing exhaustive session enums alone.
Extension fields are ignored on read. Unknown policy strings preserve their
spelling but grant no authority. All calls use channel 0; failures use
crate::ErrorBody, not a successful reply with an empty configuration.
Structs§
- Config
Applied Reply - Receipt of an outcome; refusals travel in an ERROR frame instead.
- Config
Applied Request - A complete-generation outcome bound to the caller’s child, project and delivery attempt. An ACK includes readiness, never a partial field apply. Duplicate, stale or wrong-generation outcomes cannot move active pointers.
- Config
Changed - Daemon hint to the active delivery target only. Resynchronize on reconnect and ignore stale hints; this is not an activation record.
- Config
Declare Reply - Receipt of a declaration does not approve its schema or locations.
- Config
Declare Request - Declare once after HELLO_ACK and before the first get or applied on this connection. The schema and layer locations are proposals, not authority: only the approved declaration is enforced after stamping. Workspace mappings remain daemon-owned. Module identity comes from the connection, never a body.
- Config
GetReply - Active and optional pending views. Apply
pendingbefore ACKing it; retainactivefor recovery. A module with no approved configuration is refused withcrate::error_codes::CONFIG_GATED, never given empty file bytes.active: nullis permitted when a first delivery has no prior active view. - Config
GetRequest - Pull the caller’s view. Exact-generation selectors are only for the caller’s daemon-assigned delivery attempt, not arbitrary modules or project tuples.
- Config
Layer Snapshot - Immutable raw input, never an instruction to open a mutable path.
- Config
Review Refusal - A field or project refusal. Cross-field reasons name every implicated JSON
pointer in
paths. Reasons must not contain secret values. - Config
Review Reply - Normalized old/new values, sources and apply kinds for every field, including unchanged values whose source changed. Any refusal prevents approval; the daemon validates this reply against the schema and supplied immutable base.
- Config
Review Request - Pure daemon-to-module review of immutable candidate layers against a supplied
last-approved base, which the plan replaces and which can differ from the
generation the module is running. The module must not read files, environment,
network or secrets, or recompute old values under a new build.
base: nullmeans there is no previous approval. - Config
View - One immutable module/project view. Generation zero with
unstampedstatus represents current files before stamping, not an approved generation. Unknown statuses or snapshot layers must not be activated. - Digest
- A full SHA-256, encoded as
sha256:followed by 64 lowercase hex characters. - Field
Change
Enums§
- Config
Apply Result - Only an explicit ACK acknowledges a complete generation, including readiness.
- Config
Layer - Snapshot layer identity. An unknown layer must not be merged or delivered.
- Config
Status - Delivery status. An unknown status must not be treated as an active view.
- Layer