Skip to main content
WHAT IT IS

The B experience begins with the social film, continues through its scene-by-scene argument, and ends with the original web interaction.

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

Watch the film first, then move through the scene-by-scene argument, then open the web interaction at the end. Each stage restates the same question at a different resolution, so the sequence matters more here than on the A side. You can leave at any stage and still have the whole argument.

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 — Consequence Propagation

DISTRIBUTABLE SOCIAL ARTIFACT

Watch the LinkedIn cut

This silent-first 4:5 film is designed for the LinkedIn feed. Its complete argument appears as on-screen text; captions, the visible transcript and the download preserve the same words.

Download LinkedIn MP4Download transcriptDownload captions
Read the transcript
BUILD 029 — Consequence Propagation

SCENE 1
BUILD 029. CHANGE DOES NOT STAY LOCAL. Every edit enters a system.

SCENE 2
BOUND. NAME WHAT CHANGED. Record actor, object, purpose, and prior state.

SCENE 3
TRACE. FOLLOW EVERY REGISTERED PATH. Map direct and downstream effects.

SCENE 4
TEST. EXPECTED. EDGE. FAILURE. MISUSE. Compare severity, scale, and reversibility.

SCENE 5
GOVERN. OWNER. MONITOR. STOP. REMEDY. Release requires observable controls.

SCENE 6
CONSEQUENCE. FOLLOW IT PAST THE CHANGE. Distance can make small edits large.

FINAL PROPOSITION
A change is not small when its consequences travel beyond its author.

INTERACTIVE MOTION STORY

Explore the motion argument

The film distributes the idea. This motion story uses the caption track as its source of truth, so every scene preserves the film text while letting you control the pace.

SCENE 1

BUILD 029. CHANGE DOES NOT STAY LOCAL. Every edit enters a system.

01 / 06

RICHER WEB MASTER

Explore the interactive version

The LinkedIn cut is the shareable social artifact. The original B build below is the fuller web experience: use its controls, change its state and test the idea for yourself.

BUILD 029-B

CHANGE DOES NOT STAY LOCAL

A semantic diff propagates consequences through a dependency graph.

  1. EXACT-VALUE DIFF / ADDRESS
  2. DECISION: not reached by this fixture
  3. NOTICE: review path registered
  4. FOLLOW-UP: not reached by this fixture
  5. REPORT: review path registered

ADDRESS

The exact address value marks NOTICE and REPORT as potentially affected through registered paths.

Registered review nodes: NOTICE → REPORT

Derived fixture. “Semantic diff” here means registered exact-value comparison; propagation means potentially affected through registered paths, not causation, legal effect, or complete discovery.