PaveKeep Book a walkthrough

What can be shown, not just said

8 things about PaveKeep can be demonstrated on a working network rather than described. Each one below names the artefact behind it — a screen of the running product, or a document it produced — and you can open the artefact.

The documents are the real output, not illustrations of it: the three booklets are the files a council would file, and the two evidence packs are the same report generated as at two different dates. Every one is committed to the repository with its SHA-256, so the file you download is the file that was reviewed.

P1 · Every number can be traced back

which survey, which setting, which piece of arithmetic. The software explains itself rather than asking to be trusted.

P1, shown on screen: method statement

P2 · A sealed road, a sprayed-seal road and a gravel road are scored by different methods, because they fail in different ways

P2, shown on screen: unsealed rating

P3 · A road nobody has surveyed is reported as unknown, never as zero and never quietly averaged away

This is the one councils test us on.

P3, shown on screen: booklet page

P4 · Heavy vehicle traffic changes how fast a road is expected to wear out, and the change is visible rather than buried in a model

P4, shown on screen: method esal

P7 · It sits beside the systems a council already has rather than demanding they be replaced

The artefacts, to open or download

These are files, not pictures of files. Their hashes are published with the pack: see docs/PROOF_EXECUTION_MAP.md and the manifest beside it.

None of this is a customer reference

Every artefact above was produced on the demonstration network. No council has put its own data through PaveKeep in service, so there is nothing here that a council said about us — only things the software did, which you can open.

Watch it happenWhat PaveKeep cannot do yet