The working A prototype: use its controls to test the build question.
Turn ambiguous concepts into validated entities, fields, relationships, constraints and source rules.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
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.
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 010-A
Give the Idea a Skeleton
Define the things, their fields, how they relate, and the rules that make every fact traceable and testable.
02 / ENTITIES + FIELDS
The things that exist
How the things connect
many-to-many · required
Local plan
Authority: Responsible local public or community steward
Locator: Document, version, section and stable URL
Freshness: Recheck on every revision or at least annually
VALID SKELETON
Structural readiness 100%
Errors
None.
Warnings
None.
Boundary: a structurally valid skeleton can still be factually wrong, incomplete, misleading, incompatible, or inappropriate for the domain.