</> Delimit

The merge gate for AI-written code, with signed, replayable attestation.

Wrap any AI coding assistant (Claude Code, Codex, Cursor, Gemini CLI) with a governance chain that runs your gates, records what changed, and signs a replayable receipt for every merge.

$ delimit wrap -- claude "fix the flaky test in tests/api.spec.ts"
✓ repo_diagnose

✓ security_audit       0 critical · 0 secrets

✓ test_smoke           165/165

✓ changed_files        1

✓ attestation signed   att_a05050eb8e13277e

                       delimit.attestation.v1 · HMAC-SHA256

                       replay → https://delimit.ai/att/att_a05050eb8e13277e

Every wrapped run emits a delimit.attestation.v1 bundle: repo head before/after, changed files, gate results, HMAC-SHA256 signature, and a replay URL. Advisory by default; flip to enforcing when you're ready.

---

Fastest path to value: delimit check

Zero-config PR safety gate. No init, no setup, no account, no keys — run it on any repo and it applies deterministic checks (breaking API changes + leaked secrets) to your staged or modified files.

npx delimit-cli check

$ delimit check
Delimit Check
Policy: default | Base: HEAD | Specs: 1
+ api/openapi.yaml — clean
PASSED — no breaking changes, no leaked secrets

When a check finds a breaking change or a leaked secret, it prints the offending file and the issue and exits non-zero — so it drops straight into a pre-commit hook or CI step.

Common options:

delimit check --staged          # only check staged files
delimit check --base main       # compare against a git ref (default HEAD)
delimit check --fix             # show migration guidance for violations
delimit check --record          # write a content-pinned record of this check

--record writes a content-pinned record of the check to .delimit/records/check-<ts>.json (or a path you name). That record is the precursor to the signed, replayable Seal attestation — the same evidence shape, pinned to the exact content you checked.

<p align="center">
<a href="https://delimit.ai/methodology/mcp-attestation">Methodology</a> · <a href="https://delimit.ai/reports/cal-com-v2-attestation">cal.com v2 worked example</a> · <a href="https://delimit.ai/docs/workflow">Workflow guide</a> · <a href="https://delimit.ai">Website</a>
</p>

---

Worked examples

Real, reproducible merge-gate runs against public API specs:

- OpenAI OpenAPI: a year of AI frontier evolution under a cross-vendor merge gate — OpenAI (openai/openai-openapi)
- Stripe v1 OpenAPI: 57 days under a merge gate — Stripe (stripe/openapi)
- Anthropic API: 76 days under a cross-vendor merge gate — Anthropic (anthropics/anthropic-sdk-python)
- Twilio v2010 OpenAPI: 55 days under a merge gate — Twilio (twilio/twilio-oai)
- Docusign eSignature v2.1 OpenAPI: 46 days under a merge gate — Docusign (docusign/OpenAPI-Specifications)
- Supabase Auth OpenAPI: 57 days under a merge gate — Supabase Auth (supabase/auth)
- cal.com v2 OpenAPI: 60 days under a merge gate — cal.com (calcom/cal.com)
- EU TED v3 procurement API: $ref'd component-schema drift under a merge gate — European Commission (TED v3 Public API)
- Cross-agent handoff: one artifact, four CLIs — Cross-CLI session handoff (worked example)
- delimit-mcp-server (self-attestation): same merge gate, third artifact class — delimit-mcp-server (self-attestation)

See the full index at delimit.ai/reports. For the schema and signing methodology behind every report, see delimit.ai/methodology/mcp-attestation.

---

Golden Path — your first 10 minutes

The merge gate for AI-written code, end to end: lint a spec, see exactly what breaks, classify the bump, settle the hard calls with multiple models, and walk away with a signed, replayable attestation. Then keep the context that survives across sessions and models.

1. Install

npx delimit-cli scan          # discovery: finds your OpenAPI specs, frameworks, security issues, tests
npx delimit-cli init          # wire up the merge-gate config (--preset strict | default | relaxed)

scan (delimit_scan) reports what Delimit can do for this repo. init (delimit_init) drops in the policy preset and merge-gate config. No account, no keys.

2. The merge gate, end to end

Lint the spec change (the gate). Baseline vs. proposed, with policy applied — one pass/fail verdict.

npx delimit-cli lint old.yaml new.yaml       # tool: delimit_lint

See exactly what breaks. Pure structural diff — added/removed/modified endpoints, schemas, params, no policy.

npx delimit-cli diff old.yaml new.yaml       # tool: delimit_diff

Classify the bump. Deterministic MAJOR/MINOR/PATCH/NONE — same input, same answer, every time.

delimit_semver       → MAJOR/MINOR/PATCH/NONE + next version string
delimit_impact       → blast radius: scans your dependency manifest for downstream callers (informational)

Settle the hard calls. When the gate verdict is a judgment call, put it to multiple models and let them debate to consensus.

```bash
npx delimit-cli deliberate "Is dropping the deprecated v1 /users field a safe MINOR?"