Skip to main content
WHAT IT IS

The working A prototype: use its controls to test the build question.

WHY IT MATTERS

Show what changed between versions and what downstream records or decisions are affected.

RN'S ROLE

RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.

BOUNDARY

This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.

HOW TO USE THIS PAGE

Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.

WHERE TO GO NEXT

The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.

BUILD 029-A

Change & Consequence Explorer

Show what changed between versions and what downstream records or decisions are affected.

BEFORE / v1

pending

Island A

AFTER / v2
CHANGE TRACE / 029.2.0

TRACE GAPS

2 exact-value field changes · 0 registered potentially affected nodes

  • Record two distinct version identities.

Registered exact-value diff

REVIEW / CHANGED / SEMANTICS NOT ASSESSED

Service address (address)

Island A” → “Island B

CRITICAL / CHANGED / SEMANTICS NOT ASSESSED

Status (status)

pending” → “approved

Registered potentially affected nodes

Version-event evidence

Event: EVENT-029-01
Actor: Synthetic program reviewer
Authority: May correct synthetic case fields and initiate registered review
Reason: Correct the verified case status and service address.
Evidence: EVID-REASON-01 (change-reason), EVID-AUTH-01 (change-authority)

Boundary: the canonical phrase “semantic diff” is implemented as schema-bound exact-value comparison. Paths identify registered potentially affected nodes only; they do not prove causation, materiality, legal effect, or complete discovery.