Innovation lab · Concepts

From idea to proof.

Conceptualization means turning a hunch into something testable. Every concept here has a problem, an idea and a smallest test, and an honest status.

IdeaConcept briefPrototypeEvidenceShip, park or stop

In use I use it today · In progress being built or run now · Concept an idea, not built yet.

In use

Resumable data mover

Problem. Long data moves fail halfway and nobody can prove what landed.

Idea. A reusable pattern: append-only audit log, rerun skips successes, progress report, read-only verify.

Smallest test. Package it as a small template other migrations can start from.

Read the write-up →
In use

Role-matrix test generator

Problem. Permission checks are too many to write by hand, so they do not get written.

Idea. Describe who may see what in one matrix and generate the specs.

Smallest test. Make the matrix format app-independent and add a matrix review checklist.

Read the write-up →
In use

Browsable backups

Problem. A backup you cannot read is a hope, not a backup.

Idea. A read-only export plus a small local app to search it.

Smallest test. One browse interface for exports from several SaaS tools.

Read the write-up →
In use

Company as code

Problem. Company setup lives in consoles and nobody can reproduce it.

Idea. CRM, hosting, DNS, brand, forms and sign-in defined in reviewed scripts.

Smallest test. Turn this repository into a starter anyone can fork.

Read the write-up →
In use

Tools that explain themselves

Problem. People distrust tools that act without showing what they will do.

Idea. Show the exact payload and SQL before a report runs.

Smallest test. Make a preview-before-run panel a standard for internal tools.

Read the write-up →
Concept

State-aware infrastructure as code

Problem. Scripts are repeatable but have no state, no drift detection and no preview before they act.

Idea. Port the AWS pieces to Pulumi or Terraform, with a preview of every change in code review.

Smallest test. Port one small stack, certificate plus DNS, and compare effort and safety with the scripts.

Read the write-up →
In progress

Upgrade kit for untested systems

Problem. Upgrades stall when there is no safety net.

Idea. A plan template, seam-map format, characterization-test recipe and status document.

Smallest test. Run it on the next phase and measure how many surprises it catches.

Read the write-up →
Concept

AI pair-review checklist

Problem. AI-written code arrives fast and can skip the habits that keep quality up.

Idea. A short checklist for reviewing it like a new teammate: tests, diff size, security, provenance.

Smallest test. Trial it on a month of AI-assisted pull requests and count what it catches.

Concept

Decision log as a habit tool

Problem. Decisions get made in meetings and lost.

Idea. A tiny form or command that writes a dated decision record into the repository.

Smallest test. Try it with one team for a sprint and see whether people reread the entries.

Concept

Usage-first SaaS review

Problem. Contracts renew on dates, not on evidence.

Idea. A script that pulls per-feature and per-seat usage for each tool before a renewal conversation.

Smallest test. Run it on two tools and compare the findings with what the contract assumed.

Concept brief

The one-page template.

  1. Problem: what is hard today, and for whom?
  2. Idea: the smallest version that could help.
  3. Hypothesis: what I expect to be true if it works.
  4. Smallest test: what I can try in a day or a week.
  5. Success measure: how I will know.
  6. Decision: ship, park or stop, and by when.

Open the ideas notebook