Toolkit

Everything is on the page

Each one is a short explanation, a worked illustrative case, a table you can fill in, what it does not cover, and one question to take into your next review. All of it is on the page.

Start with the cost-ceiling worksheet All resources

3 resources are published. Nothing is listed here before it is written.

What is published

Open worksheets and checklists

The page is the resource. Everything is here to read, fill in or print, and nothing asks for an email address.

LC-R01

Cost-ceiling worksheet

Five boundaries, eleven columns, one workflow at a time.

Decide what one workflow is allowed to spend or repeat, what happens when it reaches that boundary, and who reviews the result.

Reach for it when A workflow is about to be allowed to retry, call tools or run in the background, and nothing yet stops it.

Reviewed by: Not yet reviewed
Companion file: cost-ceiling-worksheet.csv

Read it Download the spreadsheet

LC-R02

Evaluation-gates worksheet

One row per requirement, thirteen columns, no pass percentage.

Connect one requirement to the evidence for it and to a release decision, with the coverage gaps and the decision owner written down beside it.

Reach for it when A release meeting is coming and somebody is going to ask whether the evaluation results mean the system is ready.

Reviewed by: Not yet reviewed
Companion file: evaluation-gates-worksheet.csv

Read it Download the spreadsheet

LC-R03

Deployment checklist

Thirteen areas, eight columns, one release record.

Make a release operable: for each area, the action, the owner, the evidence and the recovery path — before the release and after it.

Reach for it when A release is going out and the question "who would notice if this silently stopped working" has no answer yet.

Reviewed by: Not yet reviewed
Companion file: deployment-checklist.csv

Read it Download the spreadsheet

How to use them

Read it here, or take the table away

On the page The whole resource — explanation, worked case, the tables and the limits. Nothing is held back for a download.

As a spreadsheet A comma-separated file whose columns are the table you just read, ready for Excel, Sheets or anything else. It downloads straight from this page.

On paper Each resource prints as a form, rules and all. There is no PDF file to download — your browser's own print dialogue will save one if you want it.

Nothing here is scored. There is no grade, no percentage, no readiness level and no certificate — the columns exist so that a decision can be read and challenged by somebody else, not added up.

What is not here

Planned, and not written

More worksheets are planned, on the questions these three keep running into: what to do with an uncertain result, how to decide where work should run, what to measure once a system is live. They are briefs at this stage rather than written documents, so there is nothing to link and no date to give. They will appear here when they are written, and not before.

The templates and the guides are the same idea in two other shapes — a blank artefact with a worked example beside it, and the long-form reasoning behind the decisions these tables ask you to record. The agent design check asks a related set of questions one at a time, in the browser.

If the resource you needed is not here, say so — an unanswered question is how the next one gets chosen.