Beta walkthrough
Six steps, about twenty minutes. Each one says what to do and what should happen, so anything else is worth telling us about. Everything runs in this browser; nothing is sent anywhere and no account is needed.
Before you start
* The desktop application is not code-signed yet. Windows shows a SmartScreen notice; macOS asks you to right-click and choose Open the first time. Certificates are bought, not built, and that has not happened.
* Every page here works from a file on disk. Save one, turn your network off and open it again — that property is the product, and it is worth confirming rather than taking from this page.
Anything that does not match, send to hello@corobate.com. Step number and what you saw is enough.
The six steps
1 Build a receipt, and watch the arithmetic
- Do
- Work through the six steps. Change a value and watch the confidence move.
- Expect
- The confidence is the LOWEST of the required inputs, never an average. Raising a strong input does not lift a weak one.
- Why
- This is the whole engine in one page. If it behaves differently here, nothing downstream is worth testing yet.
2 Check a sealed record, then break it
- Do
- Read the record, then follow the link to the copy with one character changed.
- Expect
- The intact record passes every check that can run on it. The altered one FAILS, and the page names which checks failed and why.
- Why
- A tester should see the tool refuse something before trusting it to accept anything.
* None of the shipped samples is a clean sweep — each has at least one check that cannot run, because an older record does not carry what a newer check needs. The page counts those separately from passes and says which they are.
Open a sealed record →3 Verify a record with no account and nothing installed
- Do
- Paste in a record — the samples are on the page. Save the page to your desktop and run it again with your network off.
- Expect
- The same answer both times. Nothing is sent anywhere.
- Why
- The product’s claim is that you do not need us to check our own work. This is the page where that is either true or it is not.
* A record that declares an encoding this build does not compute is reported as "cannot check" rather than as altered. That distinction was added on 1 September and is worth confirming if you have an older record.
Open the verifier →4 Open your application, as the person who will use it
- Do
- Choose an application, then a role, and read what that pairing works in before you follow the link.
- Expect
- The page lists what that role works in, and opening the link carries the role into the console: the navigation shows only that role's pages, above a line naming how many and offering every page.*
- Why
- This is the front door a licensed user lands on, and the honest version of what a static site can do about roles.
* The role travels in the address, so it holds for the page you open and not for the next link you click — a static site has nowhere to keep it, and this build stores nothing in your browser on purpose. The landing page of each console is a directory; the controls are one level in — try `run` first.
Open the branching index →5 Drive a console
- Do
- Add a link, add an instrument, set an exposure, and press "Assess the chain".
- Expect
- A finding with the floor in basis points, the weakest link named, and the binding authority shown.
- Why
- Everything above demonstrates. This is the product doing its job on inputs you chose.
6 See what a refusal costs, at every setting
- Do
- Enter your own two numbers: what a wrong approval costs you, and what a delayed one does.
- Expect
- The break-even holds no matter where the dial sits. The page ships with both price boxes empty.
- Why
- The economics are yours, not ours. This page has no opinion until you give it one.
The five applications
One engine underneath. Each answers a different question and is entered separately.
What to send back
| If this happens | Send |
|---|---|
| It did something other than what the step says | The step number, what you did, what happened. |
| A page would not open, or a link went nowhere | The page you were on and the link you pressed. |
| A number looked wrong | A screenshot is enough — every figure on every page is recomputed from the record, so the inputs are on screen with it. |
| The wording made you stop and re-read | That is a finding. Quote the sentence. |
Built by 16-site/build-beta.js from the product register and the page register. 6 steps, 5 applications. Nothing on this page is legal advice.