Operating artefacts, not slide theatre.

Decide Then Build

Name the decision → Name the constraint → Build the smallest loop.

When to use

When building is cheap and the failure mode is shipping the wrong thing, faster.

Example

The sequence used on HealthTech and EdTech work. Three moves, in order, before a line of product code. Not a pitch. A working loop.

1. 01 · Name the decision

   AI made execution cheap without making deciding easy. The failure mode moved upstream: shipping the wrong thing, faster.

2. 02 · Name the constraint

   Clinical, regulatory, ethical, or a hiring manager’s bar. The constraint is the brief — not a backlog of features.

3. 03 · Build the smallest loop

   One artefact that would change that decision. Specs without a prototype are theatre; prototypes without a decision are toys. Humans stay on the hook.

Coming soon as a SKU. No Gumroad, no PDF, until a URL exists.

Start in the constraint

The constraint is the brief — not a backlog of features.

When to use

When the real brief is clinical safety, GDPR Article 9, CDSCO/MHRA process, or a hiring manager’s bar.

Example

Aksh Health: special-category health data stays on site. Ingestion (HL7 / FHIR), local inference, append-only audit. Cloud chat APIs are a non-starter for this class of problem.

No download. The artefact is the case.

Keep a human on the hook

AI assists. It never replaces the reviewer.

When to use

When you are building in CDSCO, MHRA, or NHS-adjacent environments.

Example

Vigil-MODI was framed that way: Modular Orchestrated Digital Intelligence — privacy-first anonymisation, document intelligence, regulation-as-code, FHIR-native architecture — with a person still accountable for the call.

No download. The artefact is the case.

Practice the job

Practise the actual work. Certificates are a receipt, not the skill.

When to use

When a career product still sells inventory: modules, badges, a PDF at the end.

Example

Elevare is being tested in public as a personalised accelerator — AI-guided workflows and role-specific simulations. Until there is a published outcome study, treat that as a product thesis, not a measured lift.

No download. The artefact is the case.