Protocol v0.1.0Verification EnginePatent Pending

Lockstep

Stop trusting your AI agent.
Verify it.

Cryptographic receipts for AI-generated code. Every step hashed. Every action verified. Every receipt independently verifiable.

STATUS QUO: TRUST

AI agents lie.

Not maliciously. They hallucinate, skip steps, and claim completion prematurely.

> Build auth module (5 steps)
Agent: Working on it...
- Schemas created
- Middleware implementation skipped
- Routes configured
Agent: Done! All 5 steps complete.
> npm run build
Error: missing middleware dependency.
LOCKSTEP: VERIFICATION

Math doesn't.

Every step validated. Every validation hashed. Every hash chained.

> lockstep run spec.yml
1
Step 1: Schemas ✓
Hash: a3f7c...
2
Step 2: Middleware ✓
Hash: e8b1d... | Prev: a3f7c...
3
Step 3: Routes (Pending)

The
Protocol

Write a deterministic YAML spec. Define execution steps. Attach validators to each step. Lockstep orchestrates the AI agent, enforces execution order, and cryptographically signs the passing validations.

Read the Docs
.lockstep.yml
version: "1"
config:
  agent: "claude-code"

steps:
  - name: "Initialize Core"
    prompt: "Create Next.js app with TypeScript"
    validate:
      - type: file_exists
        target: "package.json"

      - type: command_passes
        command: "npx tsc --noEmit"

      # Independent AI Evaluation
      - type: ai_judge
        criteria: "Follows modern App Router conventions"
        threshold: 8

12 Validators

Mix deterministic engineering checks with subjective AI evaluation.

ai_judge
KEY INNOVATION
Independent AI quality evaluation.
criteria: "Handles edge cases"
threshold: 8
file_exists
Verifies presence of exact file paths.
target: "src/main.rs"
command_passes
Executes command, requires exit code 0.
command: "cargo test"
file_contains
Regex or string match within file contents.
text: "pub fn init()"
type_check
Runs strict type compilation validation.
strict: true
api_responds
Pings endpoint for 200 OK status.
url: "http://localhost:8080"
json_valid
Parses target file to ensure valid JSON.
target: "config.json"

Execution
& Proof.

Watch the engine enforce compliance in real-time. Upon successful completion, an immutable JSON receipt is generated, linking every step hash to the genesis state.

stdout