Skip to main content

Fixed-Term Systems Repair

AI Agent Workflow Repair

We find the boundary where an AI workflow can technically pass while producing the wrong business outcome, then repair and test that boundary.

SHOW US THE FAILURE
Semantic scan / approval case Contradiction found
Passed Correct
RecommendationREJECT DecisionAPPROVE JournalWRONG ACTION
Shape valid Semantics contradictory Boundary repaired
101 renderer tests passed after the approval repair
12 backend tests passed against the same decision boundary
0 journal actions written by the blocked contradictory packet
4 internal failure classes exposed in this review cluster

The contradiction lab

Four ways green workflows fail

Each case starts with a guarantee the business believed it had. The useful work begins where the recorded outcome contradicts that guarantee.

Showing Reject became approve

Control Room regression receipt with exact override assertions and fresh test results
01 / redacted internal receipt Inspect the full case ↗

Reject became approve

Expected invariant
A Reject recommendation controls the default decision unless a reviewer records a distinct, explicit override.
Observed contradiction
The editable packet carried decision=approve while its rationale and recommendation both said Reject. Shape validation still allowed the contradiction to approach the journal boundary.
Boundary repair
Both renderer and backend now reload the authoritative recommendation, present rejection first, and block repeated or stripped override evidence.

The transfer packet

What survives after we leave

A repair has value when the owner can replay the contradiction, rerun the acceptance test, understand the stop condition, and recover without us in the room.

A

Contradiction trace

One real redacted record mapped from source input through review, authorization, durable action, and recovery.

B

Boundary repair

The smallest authoritative seam that can block the wrong outcome without flattening the useful creative work.

C

Adversarial acceptance tests

Repeated rationales, stripped provenance, stale packets, missing evidence, partial handoffs, and replay attempts.

D

Owner transfer

Runbook, logs, stop conditions, rollback path, test command, and the next safe change.

Proof from internal development

The failures behind the service

These are internal product-development cases, not client case studies. Each article exposes the invariant, contradiction, repair, tests, and remaining limits.

01
Internal case note

When Reject Became Approve

A semantic approval contradiction survived shape validation until both boundaries were rebound to the source decision.

101 renderer tests · 12 backend tests
Read case 01 ↗
02
Internal case note

Selection vs Authorization

Why creative exploration and deterministic authority need separate rooms, owners, and receipts.

CreativeHandoffV1 · independent release gate
Read case 02 ↗
03
Internal case note

The Task Never Arrived

The session existed. The reviewed work packet did not.

payload diff · semantic hash · receipt
Read case 03 ↗
04
Internal case note

Qualify Website Leads With Evidence

Recency, technical weakness, buyer fit, and lawful public routes before a lead enters the queue.

5 audited · 4 retained · 0 outreach
Read case 04 ↗
05
Internal case note

When Prospecting Should Stop

Missing diagnosis now stops the system instead of generating owner-facing fiction.

9 retained · 0 external actions
Read case 05 ↗
06
Internal case note

The Zero-Context Buyer Test

Source-backed copy still fails when a new buyer cannot identify the problem, work, deliverable, risk, and next action.

V1 invalidated · V2 unsent
Read case 06 ↗
07
Internal case note

Prove the Music Video Reacts

Static pixels, motion, audible audio, lyric alignment, and accountable reactivity need different evidence.

0/10 rejection · six proof gates
Read case 07 ↗

The actual finish line

Change the outcome, not the badge

Tests tell us whether the repaired boundary behaves under pressure. Receipts tell the owner what happened. The business result stays separate from both.

01 PASS

shape and transport checks

02 WRONG

business outcome before repair

03 BLOCK

contradictory action at the authority boundary

04 REPLAY

the exact failure from durable evidence

Start with one contradiction

Bring the workflow that passed and still failed.

Send one redacted record, the expected result, and the contradictory outcome. We will identify the first boundary worth testing and whether a fixed-term repair is enough.

SHOW US THE FAILURE