clawft

ExoChain Compliance & Governance

How chain logging and governance gates are applied across the kernel, with counts recomputed from the 0.8.4 code. The April 2026 certification is not re-run.

Kernel state changes are meant to be chain-witnessed through the ExoChain, and sensitive operations to pass a governance gate first. This page states what the code shows at 0.8.4 and what has not been re-audited.

Current figures

Both numbers are recomputed from the tree and change with every release:

FigureValue at the 0.8.4 baseMethod
EVENT_KIND_* constants in chain.rs127grep -c "pub const EVENT_KIND_" crates/clawft-kernel/src/chain.rs
gate.check( call sites in crates/clawft-kernel/src, tests excluded81, in 17 filesgit grep -n "gate.check(" filtered for test files and comments (a rough count: the pattern also matches helper calls)

Files with a gate call: a2a.rs, app.rs, auth_service.rs, capability.rs, cluster.rs, config_service.rs, cron.rs, environment.rs, gate.rs, infer_proxy/listener.rs, licence/relay.rs, placement_vocabulary.rs, and the workload_ctl/ and workload_runtime/host.rs modules. Governed gate actions include config.set, auth.credential.register, capability.elevate, the workload.* family, and the A2A routing gate (ipc.send, ipc.signal, tool.<name>).

Pattern

  1. A service or router builds a context with an EffectVector for the action (GateEffectKind in governance.rs supplies the vector) and calls GateBackend::check.
  2. On Deny, the operation returns an error such as KernelError::GovernanceDenied or CapabilityDenied.
  3. With the exochain feature, the operation appends a chain event whose kind is one of the EVENT_KIND_* constants.

See Governance for how the engine decides and ExoChain for the chain itself.

Crates outside the kernel

Crates that cannot reach the chain directly (eml-core, clawft-graphify, clawft-weave) reach it through the kernel: eml-core keeps a per-model event log that the kernel drains, and Weaver session commands cross the WeaverCommand and WeaverResponse protocol, which is chain-logged at the kernel boundary. The graphify tracing-span bridge described in earlier versions of this page was not re-checked.

The April 2026 audit

An earlier version of this page reported a four-auditor compliance audit of v0.6.5 that found and closed 66 gaps (5 critical, 16 high), with a certification "applying to WeftOS v0.6.5" and a table of 21 gates. That certification predates the 0.8 line and has not been repeated. Its gate table named source files that no longer exist (tool_registry.rs, wasm_sandbox.rs, exochain.rs, cron_service.rs, workspace.rs), so it was removed rather than carried forward. Do not cite it as a statement about 0.8.4. A new audit needs a stated method (for example listing every pub fn that mutates state and checking for a chain append) and a recorded result.

See also

On this page