Arbol is the assistant the other four audits make trustworthy. It runs on documents you already own, answers with the notes it used, and — because it is built on Nullius — can tell you whether its own retrieval evaluation means anything.
It makes the assertions, and shows its sources. Then it audits its own evaluation set, and withholds the score when that set cannot support one.
The layer that answers from your documents, and shows you which ones.
Every company that buys an internal assistant asks the same question six weeks in: is it actually right? The vendor shows a retrieval score. Nobody audited the test set that produced it. Arbol is the same product with that loop closed — the assistant and the instrument that checks it come from the same codebase, and the instrument was built first.
Four questions, asked in the same order every time.
This is the one page in the suite with nothing to prove yet. It indexes and answers over a single private vault and has never been run by anyone outside it. Listing it as shipped would be the exact move the other four pages exist to catch, so it is listed as what it is. It becomes a product when a client asks for it — the sequencing rule for this entire suite is that a surface gets built when someone needs it, not before.
The section a competent buyer reads first.
Every report this product emits ends with its own version of this list, generated from the run rather than written by hand. A report cannot be constructed without one — the validator refuses.
Fixed scope, fixed price, and a report you can argue with.
The documents surface, running in your browser — the real engine, installed into the page. Nothing is uploaded, because there is no server to upload it to. Or send one artifact and we will look at it: you get the finding either way, including if the finding is that nothing is wrong.
One product run against your artifacts, with a written report: measures, findings by severity, the resolution floor, and the limits. The price is fixed before the work starts and quoted from the size of your company, not from how the conversation goes.
Where it gets interesting — the findings on one surface routinely explain the numbers on another.
Five surfaces, one decision procedure. Each deploys separately, so one product's failure cannot take another down.
| Product | Surface | In one line |
|---|---|---|
| Nullius | documents | Your retrieval score is measuring your wording. |
| Auctus | growth | Most campaign wins are smaller than the experiment could see. |
| Fiscus | money | Finding the savings is the easy half. Proving one happened is the other. |
| Rima | code | Two checks, chosen because they are high-precision and commonly missed. |
One test set, one experiment, one statement export, one repository. The first look costs nothing and the finding is yours either way.
rishabh@op2ra.com