The working A prototype: use its controls to test the build question.
Decide which repeated service steps should become software, remain expert judgment, or disappear.
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 005-A
Service-to-Software Discovery
Map the work people actually repeat. Then decide whether each step looks like a software candidate, expert judgment, or waste that should disappear.
Do not automate the service. Separate the steps first.
Describe what actually happens. Then test each step for value, recurrence, rules, judgment, consequence, ambiguity, fragmentation, and exceptions.
02 / CLASSIFY THE STEP
Collect intake details
Gather the same structured facts before the expert begins.
AUTOMATE
Decision-gap signal inherited from Build 003: 49/100 · investigate
- The step repeats and its rules are explicit enough to encode.
- Most of the work does not depend on expert judgment.
- Build 003 inheritance: the decision-gap signal is investigate (49/100), so software may be premature.
Software is only one possible outcome.
AUTOMATE
KEEP HUMAN
REMOVE
Boundary: this is a product-discovery instrument, not an automatic software business case. “Automate” means the step has characteristics worth prototyping and validating. It does not establish demand, ROI, safety, legal permission, or implementation readiness.