Skip to main content
WHAT IT IS

The working A prototype: use its controls to test the build question.

WHY IT MATTERS

Test whether a tracker or process should become software, service, dataset, company—or stay simple.

RN'S ROLE

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

BOUNDARY

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

HOW TO USE THIS PAGE

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.

WHERE TO GO NEXT

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 006-A

Does This Actually Deserve to Be Software?

Start with the decision gap and the work itself. Then test whether the opportunity deserves software—or whether a service, dataset, company, or simple process is the stronger form.

01 / START WITH THE JOB

Software is a form. It is not the default answer.

Test the problem first, then test whether software creates enough advantage to deserve its own maintenance, ownership, and operating burden.

02 / PASS THE FORM GATES
CANDIDATE FORM

SOFTWARE

Inherited decision-gap signal: 58/100 · promising gap

  • The problem recurs, software materially improves the job, an owner is visible, and maintenance burden is not yet dominant.
  • Build 003 inheritance: decision gap 58/100 · promising gap.
03 / FIVE POSSIBLE FUTURES

SOFTWARE

A repeatable interface/system materially improves the recurring job.

SERVICE

Expert judgment remains the primary value and software should stay assistive.

DATASET

The durable asset is structured evidence, records, or data—not the interface.

COMPANY

The opportunity may require an operating system around product, buyer, delivery, and scale.

KEEP SIMPLE

A template, checklist, spreadsheet, or manual process is still the stronger answer.

Boundary: this tool chooses a candidate form for investigation. It does not prove product-market fit, willingness to pay, feasibility, defensibility, legal permission, or investment readiness.