What did we get for the money?
The aim is a shareable view of what you asked for, what was built, what you accepted, and what it cost. You send the link to your board or your funder. They do not need an account on your code host.
State: planned, not built
Nothing on this page exists yet. It rests on the five measures, which are not built, and on a new requirement agreed on 2026-10-13: a read-only view for a board or funder, in the workspace of the organisation's product owner. We say "planned", and we do not say "does".
What your board or funder would see
- What was asked. The goal and its done-when, in plain words. Planned, not built
- What was built. The accepted changes, and who or what checked them. Planned, not built That a person accepts every change is built and measured. Measured, with a recorded deviation
- Whether it was used. The "used after release" number, which you define for each project. Planned, not built
- What it cost. Cost per accepted change, rejected work included. Planned, not built
- What the records say. The change record and the evidence pack of the compliance page, for a period. Planned, not built
- A link for outsiders. A view with a passcode, and a warning to check what personal data it holds. Planned, not built
The passcode idea is borrowed from other product tools and adapted for an NGO. Until the view exists, this page invents no example of it.
The technical detail
The claims behind this page, with their states as the evidence page records them.
| No. | Claim | State | What it serves | Check or issue |
|---|---|---|---|---|
| 13 | Nothing is published or merged without a person. No self-approval. The recorded deviation: whoever holds a project's key (Temporal token) to the engine's workflow service can send a decision under any name. | Measured, with a recorded deviation | Human approval (F9, S9) | inbox_checks; #32 |
| 46 | Five standard reviewers, one per kind of review: security, documentation, compliance, Done when, architecture. | Not built | Review follows the risk (F22), compliance reviewer (C10) | #107; #299 |
| 47 | Your team chooses a human review level, shown on every change. Level A, with the line "no human engineer has read this code", is decided. | Not built | Review follows the risk (F22) | Level A decided 2026-10-13. #299 |
| 48 | A goal becomes an issue with a Done when, drafted by the engine and approved by you. | Not built | Goal to Done when (F23) | #287 |
| 52 | Five measures are recorded by the machinery and shown together. | Not built | The five measures (F27) | #290 |
| 61 | A shareable view for a board or funder: what was asked, built, accepted and what it cost. | Not built | Read-only view for a board or funder (F17, amended) | New requirement agreed 2026-10-13. #293 |
| 62 | Each change has a record: diff, test result, findings, risk note with rollback, approver, time. | Not built | Change record (C16) | #307 |
| 64 | You can export an evidence pack for a period, in open formats. | Not built | Evidence pack (C18) | #307 |
Tell us you are interested
B Team is not offered to anyone yet. NGOs come first. If you want to hear when that changes, or you would like to be one of our first pilots, write to us.
Write to: [contact address to be decided]
This draft has no form and collects no data. Once there is an address, what happens next is meant to be this: we tell you whether we can work with your organisation yet. We promise no date and no price.