Curator Research
Menu

Home / ChangeProof · Specified MVP under internal evaluation — not a hosted product

When the law changes, everything it touches.

A new rule does not stay in the circular. It reaches policies, procedures, code, controls and the people who own them. ChangeProof traces it everywhere it lands, drafts what must change, routes it to its owners, and proves what was done.

Talk to us about ChangeProofFollow a change
  1. A dark plane of concentric rings holding cards for policy, procedure, code, controls, dashboards and tests, an outer ring in outline, and owners at the rim.

    01 / 07

    The company at rest

    An organisation's obligations are spread across policies, procedures, code, controls, dashboards, tests — and the people who own each of them. Most of the time nothing connects them.

  2. A paper circular falling into the centre of the rings: complaints to be resolved within 21 days, reduced from 30.

    02 / 07

    A change arrives

    In our working demonstration, a fictional lender receives a fictional regulatory circular: complaints must now be resolved within 21 days instead of 30.

  3. A copper ripple spreading across the plane; the cards it reaches rise and their edges glow.

    03 / 07

    Scan

    ChangeProof scans the workspace and finds every artefact the obligation touches — the policy, the procedure, the code constant, the escalation schedule, the control, the dashboard, the tests — recording the file, line and column as evidence. It is analysis at run time, not a lookup of known answers.

  4. Small copper badges above each affected card: 30 to 21 days, escalate on day 14, expect 21.

    04 / 07

    Draft

    For each affected artefact it drafts the change: a redline for the policy and procedure, a patch for the code and configuration, an updated test.

  5. Owners at the rim — compliance, operations, engineering — lighting green in turn, with checks above the changed cards.

    05 / 07

    Review

    The owners review: approve, reject with a reason, or revise. An approval counts only for the exact plan that was displayed — its fingerprint must match both what the reviewer saw and a fresh read.

  6. The outer ring of outlined cards pulsing without lighting: product documentation, business strategy, risk register, audits, the organisation.

    06 / 07

    Designed to reach

    ChangeProof is designed to reach every part of the company — product documentation, business strategy, risk, internal and statutory audits, the organisation as a whole. Those are not demonstrated yet, so they stay in outline In development

  7. Green threads from every changed card converging on a slab at the centre: a proof manifest with its hash.

    07 / 07

    Prove

    Approved changes are applied to an isolated workspace, the tests run, and every record — source span, obligation, change, approval, verification — is sealed into one hash-addressed proof manifest.

How far it reaches today.

Demonstrated in the offline fictional-lender scenario, and what it is designed to reach next.

Artefact classes ChangeProof reaches
ArtefactStatus
PoliciesDemonstrated
Procedures and SOPsDemonstrated
Code and configurationDemonstrated
Controls and compliance registersDemonstrated
Dashboards and reporting labelsDemonstrated
OwnersDemonstrated — ownership schedules accountable review
Risk managementPartly — the control register is the closest today In development
Product documentationDesigned to reach In development
Business strategyDesigned to reach In development
Internal, statutory and regulatory auditsDesigned to reach In development
The organisation as a wholeDesigned to reach In development

The record it keeps.

Append-only: a correction is a new record that replaces the old one, never an edit.

  1. Source document and version
  2. The exact span
  3. The obligation
  4. Each impact, with its evidence
  5. The proposed change
  6. The approval decision
  7. The run that applied it
  8. The new version of the artefact
  9. The verification run
  10. The proof manifest

Every record is connected to its files by a SHA-256 fingerprint, and the manifest can only be issued once those fingerprints verify.

One change, traced and proved.

From our offline demonstration: a fictional lender and a fictional circular. The values are the demonstration's own.

Source
“Regulated lenders must resolve customer complaints within 21 calendar days of receipt.”A fictional circular
Obligation
Complaint resolution: 30 days → 21 days
Impacts found
8 — policy, procedure, control register, backend constant, escalation schedule, dashboard label, regression test, ownership
Evidence
File, line and column for each impact, found by analysis at run time
Approval
Bound to the exact eight-artefact plan the reviewer was shown
Proof
Approved changes applied in isolation, a regression check and a residual scan run, one hash-addressed proof record written

What you can engage us for today

  • Walk-throughs of the working demonstration, and conversations with prospective design partners.

In development

  • Reach into product documentation, strategy, risk, audits and the organisation as a whole.
  • Deployment, integrations and live customer workspaces.

Talk to us about ChangeProof.

Tell us about the last regulatory change that took longer than it should have. We will show you how ChangeProof traces one, and be plain about what the demonstration covers.

Talk to us about ChangeProoffounder@curatorresearch.com