clawft

ExoChain Compliance & Governance

Coverage report for ExoChain audit logging and governance gate certification across all WeftOS subsystems.

Every state-modifying operation in WeftOS is chain-witnessed through the ExoChain append-only hash chain. Security-critical paths pass through governance gates that evaluate an EffectVector before allowing execution. This page documents the compliance audit results and certification status.

Overview

The ExoChain compliance program ensures that:

  1. Every mutation is logged: No state change escapes the audit trail
  2. Security paths are gated: Governance gates enforce constitutional rules on sensitive operations
  3. Events are typed: 75+ EVENT_KIND constants provide structured audit data
  4. Gaps are tracked: A systematic audit identified and closed all 66 gaps

Coverage Summary

MetricCount
EVENT_KIND constants75+
Governance gate locations21
Gaps identified66
Gaps closed66 (100%)
Critical items5/5 pass
High items16/16 pass
Independent auditors4

Critical Items

All 5 critical audit items have been verified and pass:

IDSubsystemIssueResolutionStatus
C-1ExoChainMissing chain witness on kernel boot phasesAdded EVENT_KIND for INIT, CONFIG, SERVICES, NETWORK, READYPASS
C-2GovernanceEffectVector bypass on emergency restartEmergency path now logs with elevated priority + post-hoc gatePASS
C-3WASM SandboxTool execution not chain-loggedEvery tool invocation produces a ChainLoggable entryPASS
C-4Agent SupervisorProcess spawn/kill missing provenanceProcess table mutations emit chain events with actor IDPASS
C-5EML ModelsTraining events not chain-witnessedEmlEvent types (Trained, Drift, Saved, Loaded) forwarded to chainPASS

High Items

All 16 high-priority audit items pass:

IDSubsystemIssueStatus
H-1CausalGraphEdge creation not chain-loggedPASS
H-2CausalGraphNode removal missing provenancePASS
H-3HNSW ServiceVector insert/delete not auditedPASS
H-4CrossRefStoreCross-reference creation unloggedPASS
H-5ImpulseQueueImpulse emission not witnessedPASS
H-6CognitiveTickTick interval changes unloggedPASS
H-7Mesh NetworkingPeer connection/disconnection eventsPASS
H-8DiscoverymDNS/seed peer changesPASS
H-9ClusteringCluster membership changesPASS
H-10Config ServiceRuntime configuration mutationsPASS
H-11Auth ServiceAuthentication/authorization decisionsPASS
H-12Cron ServiceSchedule creation/deletion/executionPASS
H-13SkillsSkill registration and invocationPASS
H-14AssessmentAssessment run start/complete/findingsPASS
H-15WorkspaceWorkspace create/load/delete operationsPASS
H-16GraphifyKnowledge graph mutations and exportsPASS

Governance Gate Inventory

21 governance gates enforce EffectVector evaluation on security-critical paths:

GateLocationEffectVector DimensionsPurpose
tool.executetool_registry.rsrisk=0.3, privacy=0.1Tool execution authorization
tool.signtool_registry.rssecurity=0.5Tool signature verification
agent.spawnsupervisor.rsrisk=0.2, novelty=0.3Agent process creation
agent.killsupervisor.rsrisk=0.4Agent process termination
agent.elevatesupervisor.rsrisk=0.6, security=0.5Capability elevation
wasm.loadwasm_sandbox.rsrisk=0.3, security=0.4WASM module loading
wasm.fuelwasm_sandbox.rsrisk=0.1Fuel budget allocation
mesh.connectmesh.rsrisk=0.2, privacy=0.3Peer connection
mesh.disconnectmesh.rsrisk=0.1Peer disconnection
config.mutateconfig_service.rsrisk=0.3, fairness=0.2Runtime config change
auth.grantauth_service.rssecurity=0.7, privacy=0.5Permission grant
auth.revokeauth_service.rssecurity=0.5Permission revocation
cron.createcron_service.rsrisk=0.2, novelty=0.2Scheduled task creation
cron.executecron_service.rsrisk=0.3Scheduled task execution
chain.emergencyexochain.rsrisk=0.8, security=0.8Emergency chain operation
governance.amendgovernance.rsrisk=0.9, fairness=0.7Constitutional amendment
governance.vetogovernance.rsrisk=0.5, fairness=0.8Judicial veto
assess.runassessment.rsrisk=0.1, novelty=0.1Assessment execution
workspace.deleteworkspace.rsrisk=0.4Workspace deletion
eml.traineml_kernel.rsnovelty=0.2EML model retraining
eml.loademl_kernel.rsrisk=0.1EML model loading from disk

Each gate evaluates the EffectVector against the current governance policy. If any dimension exceeds its threshold, the operation requires elevated authorization or is rejected.

Non-Kernel Chain Events

Crates outside the kernel (eml-core, clawft-graphify, clawft-weave) cannot directly access the ExoChain. They use a tracing-based bridge:

  1. eml-core: Accumulates EmlEvent in a per-model event log. The kernel drains events via model.drain_events() and appends them to the chain.

  2. clawft-graphify: Knowledge graph mutations emit structured tracing spans. The kernel's tracing subscriber captures these and forwards to the ExoChain.

  3. clawft-weave: Weaver session lifecycle events are forwarded through the WeaverCommand/WeaverResponse IPC protocol, which is chain-logged at the kernel boundary.

This architecture keeps non-kernel crates chain-agnostic while ensuring complete audit coverage.

Certification Process

The compliance audit was conducted by 4 independent auditors:

  1. Static analysis auditor: Scanned all pub fn signatures in kernel modules for missing chain logging calls. Identified 42 gaps.

  2. Runtime trace auditor: Ran the full test suite with chain logging enabled and verified that every mutation path produced at least one chain entry. Identified 18 gaps not caught by static analysis.

  3. Governance gate auditor: Enumerated all security-critical code paths and verified that each passes through a governance gate with appropriate EffectVector dimensions. Identified 6 missing gates.

  4. Cross-crate auditor: Verified that non-kernel crates (eml-core, graphify, weave) have bridging mechanisms for their events. Confirmed all 3 crates are covered.

All 66 identified gaps have been closed and verified. The certification applies to WeftOS v0.6.5.

See Also

  • ExoChain -- append-only hash chain architecture
  • Governance -- three-branch constitutional engine
  • EML -- self-learning functions with chain-witnessed lifecycle
  • Security -- overall security architecture

On this page