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

Test whether a tracker or process should become software, service, dataset, company—or stay simple.

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 006 — Form Gate Field

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.

Read the transcript
BUILD 006 — Form Gate Field

SCENE 1
BUILD 006. SOFTWARE IS NOT THE DEFAULT. The problem must earn it.

SCENE 2
FORMS. SOFTWARE. SERVICE. DATASET. COMPANY. SIMPLE. One idea has many futures.

SCENE 3
GATES. VALUE. BUYER. ADVANTAGE. MAINTENANCE. Then test judgment, data, and scale.

SCENE 4
EVIDENCE. THE FORM SHOULD MOVE. More judgment may mean service.

SCENE 5
CEILING. MORE TECH IS NOT BETTER. Choose the strongest appropriate system.

SCENE 6
RESULT. KEEP SIMPLE IS VALID. Sophisticated evaluation can reject software.

FINAL PROPOSITION
Build the form the problem earns.

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 006. SOFTWARE IS NOT THE DEFAULT. The problem must earn it.

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 006-B
IN THE LAB

Form Gate Field

Move the conditions around an idea and watch its most defensible candidate form shift across software, service, dataset, company, and keep-simple.

FORM FIELD / BASELINE

What form does the opportunity actually deserve?

Software is only one possible destination. Change the conditions and watch the candidate form move.

VALUE
4/5
SOFTWARE ADVANTAGE
4/5
DATA ASSET
3/5
BUYER CLARITY
3/5
MAINTENANCE
2/5
EXPERT JUDGMENT
2/5
NETWORK SCALE
2/5
CURRENT CANDIDATE

SOFTWARE

Use when software materially improves a recurring job and the ownership/maintenance burden is justified.

ALTERNATIVE FORM

SERVICE

Use when expert judgment is still the main source of value.

ALTERNATIVE FORM

DATASET

Use when the durable asset is structured evidence or data rather than an interface.

ALTERNATIVE FORM

COMPANY

Use when product, buyer, delivery and network scale imply a larger operating system.

ALTERNATIVE FORM

KEEP SIMPLE

Use when extra product structure would create more burden than value.

THE POINT

Build the form the problem earns.

A sophisticated product decision can end with “keep it simple.” The technological ceiling is not the maximum amount of software you can add; it is the most appropriate system the problem can justify.