Skip to main content

Module consent

Module consent 

Source
Expand description

Shared consent/v1 plan card bodies for the daemon requester and responders.

A reply can approve only the pending request on the daemon-owned connection, after that connection’s trust and active registration are rechecked. Matching these body fields is necessary, never sufficient authority. Rendering a card or asserting that a terminal showed a diff is not approval.

Structs§

ConsentRequest
Canonical plan view and exact approval binding, not a caller-composed summary.
ConsentResponse
A response echoes every approval binding. Unknown decisions decode for diagnostics but never approve. Decline, timeout or disconnect applies nothing.
Digest
A full SHA-256, encoded as sha256: followed by 64 lowercase hex characters.
InputVector
Plan
Immutable approval payload. The input vector includes subc.jsonc and every touched module’s layers, declaration and covered program identities.

Enums§

CanonicalError
ConsentDecision
Only an explicit approved answer can approve; future decisions fail closed.

Constants§

CONSENT_V1