Shift Islands
Survey in progress

Tools built to the shape of the work.

A small archipelago of software. Each island is one app, built for a job a real team actually does, and no bigger than that job needs.

Islands
03
In use
02
In survey
01
Descend

The register

Surveyed / 03
01N 04°10' · E 073°30'1 240 mIn use

Daybook

Plan the day. Sign it off in ninety seconds. That is the timesheet.

Planning lives in one tool and tracking lives in another, so the same information gets entered twice and the second entry quietly stops happening. Daybook keeps a single record that carries both the plan and the actual. The timesheet becomes a by-product of having planned, and the variance between intent and reality falls out for free.

The part that earns its keep

There is no live timer to keep up with. A running clock only tells the truth if you remember to switch it every time reality changes, and one missed switch bills two hours to the wrong task while looking authoritative.

Next.jsPostgresDrizzletime-appInternal
02N 03°02' · E 072°55'980 mIn use

Interview Record

Hiring scorecards and audit walkthroughs, running on one engine.

A panel interview and a control walkthrough are the same shape. A fixed set of questions is put to a subject, assessors record what they heard and rate it, and the ratings roll up into a decision. Only the vocabulary and the scale differ, and both of those are data rather than code.

The part that earns its keep

The headline index is deliberately not the point. Divergence is. When two assessors who sat in the same room rate one answer two points apart, an average buries the only thing worth reading.

Next.jsPostgresDrizzleinterview-appOpen
03N 01°55' · E 073°04'SoundingIn survey

Assurix

A register of risks and controls that stays current between audits.

Early survey work. The intent is a working record that carries forward, so an engagement starts from what is already known rather than rebuilding the picture from scratch each time.

Status

Charting in progress. Shape and scope are still moving, and nothing here is settled enough to describe with confidence.

ReactViteassurix-grcNot yet charted

How these are built

Four things held in code, not in good intentions.

i

One record, not two.

The moment a fact has to be entered twice, the second entry stops happening. Design so it never has to.

ii

Divergence before the average.

An average is a decision about what to ignore. Show the disagreement first, then the number.

iii

No guilt mechanics.

No streaks, no scores, nothing red. A gap in the day is a question, not an error.

iv

State the cost plainly.

Every choice buys something and spends something. Both belong in the same paragraph, not one in the pitch and one in a footnote.

  • Charted from the Maldives
  • Next.js · Postgres · Drizzle
  • No trackers, no cookies, no analytics
  • Not a product, not for sale

End of chart

Nothing to sign up for.

These are built for one team's real work rather than packaged and sold. There is no waitlist, no trial and no pricing page. If something here is useful to you, write and I will tell you how it is put together.