Documents
Everything written about Provenance so far, readable in-app so nothing depends on a shared folder or an email thread. These open in a new tab and print cleanly.
Product requirements
What we are building and, more usefully, what we are deliberately not building yet. Contains the partnership structure, the phased scope including inventory, the business model, and the named risks.
Build plan
The database schema and how it is verified, every application route by phase, and the website page inventory. Section 01 covers the four rules enforced in the database rather than in code.
Brand and design system
How we arrived at charcoal and Carolina blue, with the measured contrast figures behind every colour. Includes the directions we rejected and why.
Start with the build plan if you want to see what actually exists, and the requirements if you want to see what we have committed to and what is deferred. The requirements document is the one to mark up: the open questions at the end are genuinely open, and several of them only you can answer.
The most useful thing you can do while clicking around is tell us where the checklist language is wrong. Every item in Walk & Tap is a guess at brand-standard wording, and you have actually run these inspections.
There is no login, no database and no real data. Everything is a fixed sample so the screens can be explored without setup. Taps in Walk & Tap are held in the browser and lost on refresh. The schema behind the real version is written and tested; it simply is not connected yet.