Skip to content

Ethical-AI-Syndicate/clawforge

ClawForge

License CI/CD Tests TypeScript Node.js Performance Security

Production-ready audit trail for agentic systems. Benchmarked at 2,500 events/sec. Cryptographically verifiable. Proven in production.

What ClawForge Is

ClawForge is an audit trail system for AI-assisted workflows. It doesn't run your agents—it records what they do.

Your agents (Claude, GPT, custom code, anything) produce artifacts and events. ClawForge ensures those artifacts are:

  • Immutably recorded with hash-chained events
  • Verifiably intact with SHA-256 content addressing
  • Exportable as bundles for compliance and audit

That's it. No orchestration. No agent management. No workflows to configure.

The simplest description: It's a cryptographic ledger for AI-generated artifacts.

Who Uses ClawForge

Role Why
Compliance Teams Need provable audit trails for agent actions
Platform Engineers Building agentic systems with accountability
DevOps/SRE Recording production changes with verifiable evidence

Why ClawForge?

The Problem: Agent-based systems produce opaque, non-reproducible results. Organizations struggle to answer: what happened, why, in what order, and can we prove it?

Our Solution: ClawForge makes every workflow action a schema-validated, hash-chained audit event. We provide:

  • Immutable Audit Trails - Every action cryptographically chained to the previous
  • Verifiable Evidence - Export complete, self-contained audit bundles
  • Deterministic Workflows - Same inputs always produce identical hash chains
  • Content-Addressable Storage - Artifact integrity guaranteed by SHA-256 hashes

Real-World Applications

✅ Use Case: Incident Response at Scale

# Record an incident investigation with immutable evidence
pnpm clawctl new-run --run incident-2024-0824
pnpm clawctl validate-contract incident-postmortem.json
pnpm clawctl append-event --run incident-2024-0824 --event event.json
pnpm clawctl export-evidence --run incident-2024-0824 --out incident-evidence.zip

Result: Complete, tamper-evident incident record that can independently verify what happened.

✅ Use Case: Code Change Governance

# Track a production change with full audit trail
pnpm clawctl new-run --run deploy-feature-x
pnpm clawctl put-artifact --run deploy-feature-x --file rollout-plan.pdf
pnpm clawctl put-artifact --run deploy-feature-x --file approval.json
pnpm clawctl verify-run --run deploy-feature-x

Result: Every change with documented intent, approvals, and rollback capability.

✅ Use Case: AI Agent Audit Trail

Your AI agents (Claude, GPT, custom code) produce artifacts. ClawForge records them:

  • Agents produce files, decisions, outputs
  • ClawForge hashes and chains every artifact
  • Result: complete, verifiable audit trail

No changes to your agents. Just point them at ClawForge's artifact store.

Key Features

🔒 Immutable Evidence

  • Hash Chains: Every event cryptographically linked (event_n.hash = hash(event_n.content + event_{n-1}.hash))
  • Content Addressing: Artifacts stored by SHA-256 hash, ensuring integrity
  • Self-Contained Bundles: Export complete evidence packages with verification tools

🚀 Zero-Configuration

  • Local-First: Single SQLite database, no complex infrastructure
  • Single Binary: pnpm clawctl provides all functionality
  • Provider Agnostic: Works with any agent framework, language, or model

📊 Enterprise Ready

  • TypeScript: Full type safety and IntelliSense support
  • 200+ Tests: Comprehensive test coverage with deterministic guarantees
  • Compliance Ready: Export bundles designed for regulatory review

Quick Start

Prerequisites: Node.js 20+ and pnpm

See Installation below for setup instructions.

# Initialize your workspace (creates ~/.clawforge/)
pnpm clawctl init

# Create your first workflow run
pnpm clawctl new-run --json
# Save the runId for subsequent commands

Your First Governed Workflow

# 1. Define what you want to do
cat > intent.json << 'EOF'
{
  "schemaVersion": "1.0.0",
  "intentId": "demo-001",
  "title": "System upgrade validation",
  "description": "Verify system post-upgrade",
  "actor": { "actorId": "ops-team", "actorType": "team" },
  "constraints": { "maxSteps": 5, "timeoutMs": 600000 },
  "inputParams": { "system": "production-api" }
}
EOF

# 2. Validate and record
pnpm clawctl validate-contract intent.json
pnpm clawctl append-event --run <runId> --event contract-recorded.json

# 3. Add evidence artifacts
echo '{"status":"healthy","checks":10,"passed":10}' > validation-results.json
pnpm clawctl put-artifact --run <runId> --file validation-results.json \
  --mime application/json --label "Validation Results"

# 4. Verify integrity
pnpm clawctl verify-run --run <runId>
# Output: Run <runId>: VALID (3 events)

# 5. Export for compliance
pnpm clawctl export-evidence --run <runId> --out upgrade-evidence.zip

How It Works

1. Your agent does something      →  Produces artifact (file, JSON, decision)
2. ClawForge hashes the artifact   →  SHA-256 content address
3. ClawForge appends hash event   →  Chain to previous event
4. Repeat for every action
5. Export bundle for audit        →  Self-contained, verifiable

That's the entire flow. Your agents don't change. ClawForge just records them.

Architecture Overview

┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   Contracts     │    │   Event Store    │    │  Artifact Store │
│                 │    │                  │    │                 │
│ • Intent        │───▶│ • Append-Only    │───▶│ • Content-Addr. │
│ • Task          │    │ • Hash-Chained   │    │ • SHA-256       │
│ • Validation    │    │ • SQLite         │    │ • Immutable     │
└─────────────────┘    └──────────────────┘    └─────────────────┘
         │                       │                       │
         ▼                       ▼                       ▼
┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   CLI/Tools     │    │   Evidence       │    │   Your Agents   │
│                 │    │   Export         │    │                 │
│ • clawctl       │    │ • ZIP Bundle     │    │ • Claude/GPT    │
│ • Validation    │    │ • Verification   │    │ • Custom code   │
│ • Verification  │    │ • Portable       │    │ • Any tool     │
└─────────────────┘    └──────────────────┘    └─────────────────┘

Determinism Guarantees

ClawForge provides semantic determinism - identical logical content produces identical hashes:

  • Canonical JSON: Sorted keys, no undefined, UTC timestamps
  • Deterministic Hashes: Same event content → same SHA-256 hash, always
  • Verifiable Chains: Given identical events, chains are identical
  • Portable Evidence: Bundles contain all schemas and verification tools

Trust Model

Component Trust Level Why it Matters
Event Store Authority Append-only, hash-chained, integrity-verified
Artifact Store Verified Content-addressable with hash verification
CLI Untrusted Thin wrapper, library validates everything
Agent Workers Untrusted Ephemeral, produce artifacts only
Evidence Bundle Derived Exported from trusted store, self-verify

Start Here: Proofs

ClawForge ships two reference wedges that prove the kernel's guarantees using real inputs and verifiable evidence bundles:

  • Ship a Change — records a planned change with intent, artifacts, and a hash-chained audit trail.
  • Incident Postmortem — records an unplanned failure investigation using the identical kernel semantics.

Both produce self-contained evidence bundles. See docs/wedges.md for what they prove and how they differ.

Commands Reference

Command Description Example
clawctl init Initialize workspace pnpm clawctl init
clawctl new-run Create workflow run pnpm clawctl new-run --run deploy-001
clawctl validate-contract Validate schema pnpm clawctl validate-contract contract.json
clawctl append-event Record audit event pnpm clawctl append-event --run <id> --event event.json
clawctl put-artifact Store evidence pnpm clawctl put-artifact --run <id> --file data.json
clawctl verify-run Check integrity pnpm clawctl verify-run --run <id>
clawctl export-evidence Create bundle pnpm clawctl export-evidence --run <id> --out audit.zip

Configuration

Setting Default Environment Variable
Database ~/.clawforge/db.sqlite CLAWFORGE_DB_PATH
Artifacts ~/.clawforge/artifacts/ CLAWFORGE_ARTIFACT_ROOT

Installation

# Clone and install
git clone https://github.com/Ethical-AI-Syndicate/clawforge
cd clawforge
pnpm install
pnpm build

Verify the installation:

pnpm clawctl --help

Documentation

Development

pnpm test          # 200+ tests with full coverage
pnpm build         # Compile TypeScript
pnpm clawctl       # Run CLI commands

Project Structure

src/
  contracts/    Schema validation, migration, redaction
  audit/        Event model, canonical JSON, hashing, SQLite store
  storage/      Content-addressable artifact store
  evidence/     Evidence bundle export (zip)
  cli/          CLI entry point and commands
docs/
  contracts.md    Contract schema specification
  audit.md        Audit event model specification
  architecture.md Module boundaries and design decisions
  threat-model.md Security analysis and mitigations
  cli.md          CLI reference and usage guide
tests/
  contracts.test.ts       Schema validation tests (68 tests)
  canonical.test.ts       Canonical JSON tests (15 tests)
  hashing.test.ts         Hashing and chain verification tests (24 tests)
  store.test.ts           SQLite event store tests (25 tests)
  artifact-store.test.ts  Artifact store tests (25 tests)
  evidence-export.test.ts Evidence bundle export tests (15 tests)
  cli.test.ts             CLI smoke tests (28 tests)

What ClawForge is NOT

  • Not an Agent Framework - We don't run your agents. We record them.
  • Not Orchestration - No workflow definitions, no task queues, no agent lifecycles
  • Not a Distributed System - Local-first, single-node
  • Not a UI Platform - CLI-primary; build UIs on top if you want
  • Not Encryption - Data at rest is your responsibility

Production Use

ClawForge is used in production by enterprise applications:

saas-boilerplate

Enterprise SaaS applications — Dual audit pattern (DB + ClawForge)

  • Integration: Optional via @saas/compliance package
  • Pattern: Dual audit for compliance-critical actions
  • Use case: SOC2/GDPR evidence bundles
  • Performance: Zero impact when disabled

View integration

mcpcodex-v2

MCP governance validation — Full stack (ClawForge + governance-validator)

  • Integration: Core audit infrastructure
  • Pattern: Event recording + policy validation
  • Use case: AI-assisted development governance
  • Performance: 550 validations/sec

View architecture

Ecosystem

ClawForge is Layer 1 of the Ethical-AI-Syndicate audit ecosystem:

Layer Purpose Repo
1. Audit Event recording, session sealing ClawForge (this repo)
2. Governance Policy validation governance-validator
3. Application Complete MCP solution mcpcodex-v2

See docs/ARCHITECTURE.md for details.

License

Proprietary. All rights reserved.

Support & Community


Built by Ethical AI Syndicate - Creating transparent, governable AI systems for the enterprise.

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors