European · evidence-led delivery
Regbuild runs projects the way somebody auditing them would want them run. A change cannot be approved until the evidence for it is complete, no figure on any page is stored — they are all derived from what happened — and no metric is ever computed about a person.
This is a beta deployment being tested by the team building it. There is no marketing material behind this page yet; the effort is going into the product. Everything the page states about where it runs is read from the deployment itself.
Read from this deployment's own Trust facts when the page was served, not written here. The same numbers are in the machine-readable file below, and the Trust page shows how each was checked.
Being said plainly rather than left to be discovered: this deployment runs on a US-owned provider, and a US-owned provider is subject to US law wherever its machines sit. Production is planned on the EU-owned provider named above as planned — it holds nothing today, and this page says which is which rather than letting the two blur. It is also why this page will not tell you your data is beyond the reach of any government. Nobody's is.
Every change carries what has been proved about it and what has not. An approval is refused by the server while any acceptance criterion has no evidence against it, and the refusal names which — enforced where it cannot be walked past, rather than reported on afterwards.
Counts, cycle positions, forecasts and spend are derived from the underlying records every time they are shown. A stored count is a count that drifts, and one that has drifted is worse than none.
There is no per-person metric anywhere, by design. Facts people record — who is on something, who is away — are kept. Numbers computed about a person are not, because a delivery system that scores people gets the numbers it deserves.
Agents open changes and propose; they never merge, close, set a priority or approve their own work. Anything an agent wrote is marked as such, everywhere it appears.
Every decision appends to a ledger that is verified nightly and anchored, so a claim about what was approved and when is one you can check rather than one you take.
A monthly evidence bundle, signed, with the facts the Trust page states and the ledger's verification alongside them — the thing a procurement questionnaire actually wants.
Signing in happens at this deployment's identity provider. Regbuild never sees or stores a password, a passkey or a one-time code.
Sign in