Bluerook products
Small systems. Yours to run.
Four packages. Each one shows its boundary before you trust it.
01 · Process to SOP
Someone explains it once.
The process survives.
-
It lives in one person's head
Told out loud, out of order, with the exceptions buried in asides.
-
Structured, not summarised
Purpose and owner first. A summary loses the thing that made it runnable.
-
The holes become questions
What it cannot infer, it asks about, instead of quietly inventing.
-
It leaves as a document you own
With a completion condition, so "done" is a state and not a feeling.
Untitled
- Purpose
- Empty
- Owner
- Empty
- Exceptions
- Empty
- Done when
- Empty
02 · Follow-Up Gap Detector
Find the leads
nobody owns.
-
Nobody has looked at these in weeks
Not because anyone is careless. Because no system was watching.
-
Deterministic checks, not a hunch
No owner. Overdue. No next action. Rules you can read and argue with.
-
Healthy records stay out
A queue that flags everything is a queue nobody opens.
-
It hands you a digest and stops
No message is drafted, queued or sent. A person decides what happens next.
The library
Every package states where it stops.
A product you cannot inspect is a promise, not a system.