Skip to main content
← MAIN GALLERYBUILD 010 / 100 · IN THE LAB
BUILD 010
PHASE 01
2026

Give the Idea a Skeleton

Turn ambiguous concepts into validated entities, fields, relationships, constraints and source rules.

WHAT IT IS

A paired public prototype: A is the working tool; B turns the same question into a film, motion argument and interactive web experience.

WHY IT MATTERS

Turn ambiguous concepts into validated entities, fields, relationships, constraints and source rules.

RN'S ROLE

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

WHAT IT CANNOT CLAIM

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

WORKING PROTOTYPE

You can use and explore this build now. Its public evidence record is still being completed, so treat the experience as a demonstration—not a certified institutional system.

CLAIM CLASSIFICATION COMPLETE — QUALIFIED DESIGN PROPOSITION

Source: W3C Shapes Constraint Language (SHACL), Recommendation (20 July 2017). W3C — SHACL. Exact locator: §§1–2. Limit: Defines RDF graph constraints and validation only. It does not establish that every ambiguous concept becomes testable or that this prototype's domain model is valid. This status does not validate real-world effectiveness, safety, compliance, representativeness, cultural authority, professional suitability, or outcomes.

010-A / THE THING

Use it

Turn loose language into stable entities, typed fields, relationship constraints, and explicit source rules—then validate the skeleton.

OPEN THE TOOL →
010-B / THE STORY

Watch + explore it

Move the same idea from unresolved nouns to named entities and a validated, explorable graph.

ENTER THE VISUAL BUILD →
THE WORK BEHIND THE ARTIFACT

The build is more than the interface.

Research, planning, evidence, rejected approaches, technical decisions, audits, media, source paths and forward dependencies are retained as part of the build—not left behind in conversation history.

THE QUESTION

Build 010 asks what are the things, rules, and relationships inside this idea? That question came first and the artifact second, which is the order everything on this page follows. Each section below is either an attempt at the question or a statement of where the attempt stops, and the two are kept visibly apart so you can weigh them separately.

WHICH ROUTE TO TAKE

A and B are two routes into one question rather than a product and its trailer. Open A when you would rather reach your own judgement by operating something and seeing what it returns on your own input. Open B when you would rather understand why the question takes this shape before you touch a control. The two cards below describe each side in its own words, and most people get more out of the pair than either half alone, in whichever order suits them.

WHAT IT LEAVES BEHIND

This is build 010 of one hundred, in phase 01, and it is built to be inherited. What it hands to later builds is concrete rather than thematic: cap:010. That is what makes the sequence compound instead of repeat, and it is why the lineage view is worth reading alongside any single build.

HOW TO CHECK IT

Every claim on this page is meant to be inspectable rather than taken on trust. The public record sets out what changed, what another person can reuse, what supports the system and what the build is not entitled to claim, and the archive retains the research, rejected approaches and technical decisions behind it. A status on this page saying a review is still open is a factual report on the state of that evidence record, and it stays visible until the review closes.

WHERE IT SITS IN THE HUNDRED

Reading one build in isolation gives you the artifact; reading it in sequence gives you the argument. The gallery lets you enter at any number, and the archive holds the syllabus, feasibility audit and release standard that govern the whole programme. If this build interests you, the neighbouring numbers are usually the fastest way to see the reasoning that led into it and the capability it hands forward.

What this build is testing

Turn ambiguous concepts into validated entities, fields, relationships, constraints and source rules.

What it leaves behind

cap:010