store.sgit.ai / admin · the shop · the ledger · this page as markdown noindex · not in the sitemap
Produced with model assistance. Every page on this site, and every document in the dev packs area, was drafted with a large language model and reviewed by a person before publication.

/ work / who-does-the-work

Who runs the review

2 of 5 units done. The two upper levels are somebody's work and the store has never said whose. A buyer spending £1,500 on a security review is buying a person, and the site asks them to buy it from nobody in particular. First reviewer named 16 September; the surface is built for several, because there will be.

This workstream came out of a memo. £10, a commercial licence, and a name on the review, 2026-09-16 — kept verbatim, read into a brief, and broken into the units below.

Queued1

WD-3Let the buyer choose their reviewer at £500 and £1,500

A selection, carried in the order reference the way the shape already is. With one reviewer it is a statement rather than a choice, and it is already on both level pages, because what it says is that there is a name behind the work.

Blocked on WD-4 — a second name.memo 2026-09-16

Up Next2

WD-4Recruit the rest

The project lead is contacting security professionals they know and negotiating rates, so they can take some of the work at £500 and £1,500 and eventually above. The page is worth being listed on now, which was the whole reason WD-2 came first. Adding one is adding a record to data/reviewers.yml; the frozen list in the gate moves with it, on purpose, so a reviewer cannot appear by accident.

The project lead, in conversation · memo 2026-09-16
WD-5Say what happens when the chosen reviewer cannot take the work

Two of the four levels are one person's time, and the page does not say what happens if that person is unavailable. The delivery estimates are from your reply and depend on a calendar; the page explains why and stops there.

This was blocked on WD-3, which is blocked on a second name. It does not need to be: the answer for one name is a sentence, and not having it is what makes a reader at £1,500 hesitate. The reader who went to that page first, before anything else, is the reader who would buy the most. Raised by the five-reader journey of 16 September at /admin/reviews/.

In Progress0

—

Done2

WD-1Build the reviewer register and a page per reviewer

Shipped in v0.2.9 as data/reviewers.yml and /who/. Built for a list on the day it had one name on it — adding the second is adding a record; the page, the twin, the register entry and the links from the level pages are generated.

memo 2026-09-16
WD-2Write the first reviewer's page

Shipped in v0.2.9 at /who/dinis-cruz/. Every line read off open-source.sgit.ai's published author page and the vault catalogue, both named on the page with the date they were read. No count of years: the published record starts in 2008 and a reader can do that arithmetic and check every step of it.

memo 2026-09-16

← every workstream

An operations surface for the people building this store, public because every page here is. It is not a selling page and nothing on it is an offer. The shop is here · every claim, with its state · the reviews