Most AI systems ask you to trust them. We would rather show you the arithmetic.
Seven of the ideas the system is built on, with toy numbers so you can check them
yourself. The production versions combine several of these and use parameters we do not
publish.
01–07Seven ideas
01 · Uncertainty and sizing
When the system is less sure, it commits less.
The size of every position is tied to how certain the system is. When
uncertainty rises, exposure falls automatically, without anyone having to notice.
What this means for you: when the system is unsure, you are
automatically less exposed.
02 · Correlated agreement
Five analysts agreeing is not five opinions.
If your analysts all read the same news, their agreement is worth less
than it looks. The effective number of independent opinions falls as their errors
become correlated. The system measures how correlated its own AI analysts are and
discounts their agreement accordingly.
Saying 80% should mean being right 80% of the time.
A forecast is only useful if its confidence is honest. Group every
forecast by the confidence it was made with, then check how often each group was
right. A well-calibrated system sits on the diagonal.
A good forecast is right and appropriately unsure. The continuous
ranked probability score (CRPS) grades both at once. Lower is better, and it punishes a
confident wrong forecast hardest.
If the source does not say it, it does not get in.
This one is a rule rather than a formula. When the AI reads a filing or a
news article and extracts a fact, it must point to the exact characters it read.
Ordinary code, with no AI involved, checks that those characters really say what the
AI claims.
“A human approves every decision” means nothing if the human
has stopped reading. So we measure whether human review is actually working, and treat
any decline as a problem to fix.
What this means for you: human oversight becomes something you
can check, not a sentence in a brochure.
07 · Honest uncertainty
Knowing when to say “I don’t know”.
Every automated check in the system reports two numbers, not one: how
often it declines to decide, and how often it is wrong when it does. For example:
“declines on 12% of cases, and is wrong on 4% of the rest, against a 5%
target.” This lets you compare every safeguard on the same scale.
What this means for you: you always know how reliable each
safeguard is, in plain terms.
See the arithmetic on your own numbers.
Request access and a founder will walk you through it. Design partners get more of the maths, and the production versions are discussed in conversation.