LineBreak
Add the free gate ↵
Gated · auditable · local

The tools your team loves write the code.LineBreak governs what gets built.

AI writes the code. Humans sign what ships. LineBreak keeps the signed, offline-verifiable record of who approved what, and a free CI gate that blocks known CVEs before they merge.

Request a demoAdd the free gate to your CI
✓1,242 downloads/mo on PyPI✓Listed in the official MCP registry✓Offline-verifiable signatures

Financial sector and regulated environments

Your regulation already demands what LineBreak evidences

When the auditor asks who is the person responsible for a change an AI generated, the answer must be verifiable. We map the regulations, article by article:

United StatesSOC 2United StatesSOX ITGCGuatemalaJM-98-2025Costa RicaCONASSIF 5-24HondurasCNBS 025/2022El SalvadorNRP-23 & NRP-32
See all frameworks →
Why the Bureau exists

AI writes faster than anyone can review.

The bottleneck moved: from writing code to proving control over it. The numbers are not ours:

34%of teams that hit an incident could not tell whether AI-written code was involved.GitLab AI Accountability Report, Jun 2026 ↗>60%of developers discovered errors in AI-generated code only after deployment.DORA: State of AI-assisted Software Development 2025 ↗

When something breaks, “who approved this?” should be a lookup, not an investigation.

Real pull request blocked by the LineBreak Security Gate: required check failing and merge disabled
This is what enforcement looks like. Not a mock: it is a real public PR. Open it →
How the Bureau works

Four desks between a prompt and production.

01

The intern builds

Your agents write the code, the docs, the whole stack of paperwork. Beautifully. Then they wait at the window, because…

The AI: tireless, eager
02

The inspector blocks

Known CVEs, unmet criteria, missing sign-offs. If it doesn't pass, it doesn't ship: the stamp says BLOCKED, on the record.

The gate · fail-closed
03

The notary signs

A human with the right role approves. The signature binds who, what, and the exact content hash. No forgeries, no vibes.

Ed25519 · offline-verifiable
04

The archivist files

Every decision lands in git next to the code it governs. When the auditor asks, you open a folder, not an investigation.

The record · in your repo

AI writes. Humans approve.

Built for regulated industries. The product is built for teams whose code is read by auditors before it is read by users.

HealthcareFintechFinancial servicesGovernmentDefenseLegalInsuranceEnergyManufacturing
LineBreak Gate · free in your CI

Nothing merges without inspection.

A fail-closed gate for AI-written code: dependency CVEs blocked with CVE ID + CVSS on the record, acceptance criteria checked against the working tree, human-only overrides scoped to one package+version+CVE. If the scanner crashes, the check fails: it never shrugs and passes.

  • pip install linebreak-gate · GitHub Action @v1
  • Free CVE scan · no account, no key
  • One setup PR via the GitHub App: protected in ~5 minutes
Add the gate to your CI
La Inspectora: never lets a CVE through
LineBreak Bridge · free MCP server

The approved spec, delivered to the editor your devs already love.

linebreak-gate mcp serves your signed acceptance criteria straight into Claude Code, Cursor, or Codex: the agent reads the spec, checks its own story with the same engine CI runs, and can't edit an approved criterion. Git is the transport: no server, no account, works on a bare clone.

  • Six tools: list, read, next, status, check, verify
  • Sealed en route: the bridge can never alter a criterion
  • Spec still in Notion or Jira? Distill + approve: spec new → spec approve
  • linebreak-gate mcp install --editor claude-code | cursor | codex
Install the bridge
El Mensajero: delivers it sealed, never opens it
The Record · the gate's paid layer

Who approved what, provable from a bare clone.

Nothing new to install: it's the same linebreak-gate already running in your CI, unlocked with a license key. Every gated approval is then issued as an Ed25519 signature by the governance service (over the approver, their role, and the exact content hash), filed in git next to the code, and verified offline by the gate on every run. When the auditor asks, you open a folder, not an investigation.

  • Same tool you already installed: a license key unlocks it
  • The governance service signs; clients cannot forge an approval
  • Verified offline in CI · tamper-evident after any edit
See how the record works
El Notario firma · La Archivista archiva
LineBreak Console · the governance service

The whole Bureau, running as a service.

The authority behind every signature, running where you decide: hosted by us, or in YOUR cloud: BYOC, with signing keys generated on your volume and zero calls home; air-gapped works too. Its web runtime runs the agent server-side, so a browser can drive projects, approvals, and the record without a local clone.

  • Hosted · self-hosted BYOC · air-gapped
  • The server signs: clients cannot forge an approval
  • Projects, runs and approvals from a browser, no local clone
  • Web console: in progress, shaped with design partners
Talk to us about the console
La Archivista: keeps the whole Bureau
Ready when you are

AI writes. Humans approve.

Free gate in your CI in ~5 minutes. No account, no credit card: the Bureau only asks for a repo.

Add the free gate to your CI