The version the board can read

“Can I have this in a form my board can read?” Every vault should already contain one — the policy re-cut for the people who have to sign it off. Not a paid extra and not an add-on: every vault, including the ones anybody can download for nothing.

0 of 5 done. Status: next.

From the memo Five audiences, decoupled views, and the version the board can read (2026-09-16) — https://store.sgit.ai/admin/memos/2026-09-16-five-audiences/↗

• BR-1 · Specify what a board-readable cut actually is — next — Length, what it leads with, what it leaves out, and what a reader is expected to do with it. It is the whole deliverable, so specifying it badly is worse than not shipping it.
• BR-2 · Decide who writes it, per vault — next — Fifteen shapes. Generated, written once per shape, or written per sale — the answer changes what the entry level costs to fulfil and therefore whether £10 is the right number.
• BR-3 · Say on the site what is inside a vault — next — The memo's own diagnosis: the store never explains this well. It is the gap the board-readable cut sits in, and it is worth closing on its own even if BR-1 takes a while.
• BR-4 · Put it in the free vaults first — queued — “Including the ones you can download for free.” Doing the free ones first is the harder order and the right one: it proves the cut is generated rather than hand-finished for a paying customer. Blocked on: BR-1, BR-2.
• BR-5 · Re-read the entry level once it carries one — queued — A £10 pack that contains a version the board can read is a different argument from a £10 pack that does not. It also earns a row on the comparison table, which is where the difference between the levels is now legible — and it is kept off that table until it exists. Blocked on: BR-4, PL-2.

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).