Proof-Backed Repair Pilot

Repair operational data with proof, not scripts

After a Shadow Baseline proves the risk, a Proof-Backed Repair Pilot turns one path into a governed repair campaign: detect issues, compile safe repair plans, apply policy gates, route exceptions to review, verify approved writebacks, and produce receipts.

Why cleanup scripts fail

One-off scripts fix symptoms without policy, review, verification, or audit evidence. They break when enrichment conflicts, duplicate logic, or ERP sync rules change.

Refinery operationalizes repair as a governed loop: every change is policy-bound, verifiable, and receipt-backed.

Pilot deliverables

Timeline and pricing

Typical pilot: 6–8 weeks. Starting price from €15,000; range €9,000–€25,000 depending on connector and path complexity.

Production Trust Gateway follows successful pilots on certified paths.

Sample receipt outcome

{
  "record": "crm_account:acme-bv",
  "path": "web_form_to_crm",
  "decision": "normalized_and_escalated",
  "policy_version": "customer-master-v3",
  "issues": ["email casing", "possible duplicate", "missing industry"],
  "automatic_actions": ["normalized email casing"],
  "blocked_actions": ["duplicate merge", "industry overwrite"],
  "human_review_required": true,
  "writeback_status": "verified",
  "evidence_hash": "sha256:..."
}

FAQ

Can we run a pilot without a baseline?

A Shadow Baseline is the recommended entry. It proves issue rate and repair scope before production writeback.

Which connectors support production repair today?

PostgreSQL and MySQL are certified for the full repair loop. Other connectors require path-by-path certification — see the connectors page.

Related pages

Scope a repair pilot

Start read-only. No production writeback required. Do not submit secrets through public website forms. Privacy