Finding → Fix Spec → PR. We write a constrained change and open a reviewable pull request. We will not auto-merge, and this is not a public SKU.
Need SOC 2 or EU CRA programmes instead? UnitOne Compliance.

Findings wait in triage while investigation, a constrained Fix Spec, and a reviewable PR stay the bottleneck. That Finding → Fix Spec → PR path is the scoped work a remediation POC covers.
Finding → reachable path → what must stay true → Fix Spec. The graph keeps developer intent attached as the pipeline walks the issue.

Name the issue in the repo, agent, or MCP server where it lives — the sink or tool, the reachable path, and the function it sits in.
Write what will change and what must stay true: API shape, which tool an agent may still call, tests to run, files that are out of scope.
A focused diff that cites the finding and spec, runs existing CI, and stays inside the same review path as product work.

Tell us the repo, agent, or finding you want constrained. Primary next step is a conversation — not Start free.