HOW IT WORKS

Follow the proof, one step at a time.

A four-part workflow shown on a verified AST migration pipeline. Upstream contracts, call-site mapping, deterministic patches, and fail-closed human review.

STEP 01

Start with a recorded change.

The prototype demonstrates a known breaking change using a bundled API fixture. Live provider watching is in development.

Admitted registry watch
BREAKING CHANGESTEP 01

mockpay · v1.0.0 → v2.0.0

Parameter rename advisory

Parameter renamed: source becomes payment_method in charge creation payload.

AST Engine ActiveSingle-use reviewable proof
THE VERIFIED BOUNDARY

Deterministic rules, fail-closed boundaries.

Here is what trypatchbay executes today and how safety is preserved across every step.

POINT 01

Recorded change

A structured change record defines the upstream API contract delta with verified parameters.

POINT 02

AST call-site mapping

Static TypeScript and JavaScript AST traversal maps matching call expressions across the codebase.

POINT 03

Isolated test proof

The proof loop validates baseline green, bump red, and patch green in an isolated execution runner.

A HUMAN REVIEW STAYS CENTRAL

Evidence is there to support a decision.

trypatchbay structures breaking change triage into an inspectable review gate. The platform pairs upstream change records with matched AST call sites and deterministic diffs before an operator signs off on delivery.

trypatchbay / review-cockpit/mockpay · v1.0 → v2.0
Human Gate Required
CAD-SPEC: REV 3.0b // LENGTH: 1045.2mURBAN GRID JUNCTION | STATUS: OPTIMIZED
01Change record verified
Advisory #ADV-2024-812
mockpay 1.0 → 2.0Parameter source renamed to payment_method
02AST call-site mapped
−source: source,
+payment_method: source,
03Operator sign-off gate
Delivery Mutex Locked
Fail-closed: Operator sign-off required prior to PR delivery
Sign-off Required⌘⏎