Questions teams ask about HoldUp.

HoldUp is a pull request check that compares code changes with engineering specs, requirements, API contracts, and architecture decisions to flag possible implementation drift before merge.

No. The goal is to work with the context your team already has instead of requiring a new format or process.

Tests usually verify that implementation behaves as the tests expect. HoldUp checks a different layer: whether the implementation still matches the written intent and decisions behind the change.

The product is being designed around evidence-first review. A team can decide how findings affect merge policy, but the core value is making drift visible and explainable.

The target is framework-agnostic context such as Markdown specs, ADRs, OpenAPI, GraphQL schemas, tickets, documentation, and spec-driven development artifacts.

Coding agents increase implementation speed and PR volume. That makes it harder for reviewers to reconstruct every decision and assumption that a change was supposed to preserve.

HoldUp is currently in an early pilot and customer-discovery stage.