The working A prototype: use its controls to test the build question.
Turn disciplined human research into a repeatable intelligence workflow before automating it.
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.
IN THE LAB
Manual Intelligence Engine Method
Turn disciplined human research into a repeatable intelligence workflow before deciding what deserves automation.
Collect sources under an explicit protocol, separate source facts from analyst claims, verify each claim, preserve contradictions and uncertainty, then generate a brief only from material that has actually cleared review.
Make the method explicit before adding more sources.
Capture the source itself, issuer or author, publication/version, dates, location, relevant section or page, and why it belongs in the research set.
Write the analyst claim separately from the source record so interpretation never masquerades as provenance.
Resolve each claim as verified, contradicted, uncertain or still unverified before it can enter a brief.
Collect evidence as evidence.
A source needs a title and checked/retrieved date before it can enter the register. Other provenance fields remain explicit so “unknown” is visible rather than buried in a note.
Example primary source
https://example.org/source
Replace this demonstration record with the source you actually reviewed.
Claims do not inherit credibility from proximity to a source.
This is a demonstration claim and is not verified evidence.
Source: Example primary source
A verification note is required before this claim can be marked verified.
Only cleared claims become findings.
Verified findings
No verified findings yet.
Contradictions
No contradictions recorded.
Uncertainty
No uncertainty recorded.
Open verification
- This is a demonstration claim and is not verified evidence.
Boundary: this tool structures research work; it does not verify a source for you, infer that a claim is true, or convert an analyst judgment into evidence. A claim reaches the brief only when a human reviewer records what they checked and explicitly marks it verified.