The working A prototype: use its controls to test the build question.
Turn recurring approvals, consent, evidence, disclosures and records into reusable regulated components.
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 044-A
Reuse the Parts That Regulation Keeps Requiring
Turn recurring approvals, consent, evidence, disclosures and records into reusable regulated components.
ASSEMBLY VALID
Every declared component is bound to this exact synthetic context.
APPROVAL-1
Version 1.0
E-APPROVAL
CONSENT-1
Version 1.0
E-CONSENT
EVIDENCE-1
Version 1.0
E-EVIDENCE
DISCLOSURE-1
Version 1.0
E-DISCLOSURE
RECORD-1
Version 1.0
E-RECORD
Boundary: Context binding makes invalidation visible. It does not determine the law, approve reuse, validate consent, or establish that evidence and disclosures satisfy real duties.