Skip to content
Counterproof live ledger
Offline showcase

Authored examples are enabled so every claim state and decision path works without external services.

Fixture data is labelled AUTHORED
Founder intelligence · evidence weighted

M. O.

Why this founder surfaced, what the evidence supports today, and the next fact that would most reduce uncertainty.

FIXTUREpseudonymized
Northgate Settle →
per_mocontact form onlyfirst observed 2026-07-07 00:00Z
The simple version

Why is this person worth attention?

A solo US operator with no repo, no funding and no network. Fourteenth on raw, second once access is regressed out.

1
How we found them

A self-filed intent-to-use trademark suggests someone is building before they have lawyers, funding, or a public launch.

uspto tm 1b
2
What the evidence says

3 claims verified, 0 contradicted, and 6 still need evidence.

9 claims checked
3
What we do not know

2 expected artifacts are missing. This increases uncertainty; it does not automatically make the founder bad.

3 harmless absences were not penalized
Fair discovery signal79.4access advantages removed
Raw visibility signal60.8before neutralization
Credibility61range 48–74
Build capability57.4range 41.2–73.6
Evidence mapWhat should exist if the founder’s story is true
Evidence map

Expected artifacts

Found artifacts, meaningful gaps, and harmless absences are kept separate.

Reading absencenot expected for this profile — costs nothingexpected and not found — widens the interval, never lowers the score
5found2expected, not found3not expectedabsence bought +4.6 of interval width — and nothing off the score
Expected-evidence manifest: what we looked for, what we found, and how each absence was priced.
ArtifactStatusP(findable) if it existedEffect on the estimate
company domain live
Resolves, serves a real page, TLS certificate issued 2026-05-28.
found
0.83n=21
informs the estimate
checkout endpoint
A live Stripe checkout endpoint. Transacting today. Everyone tracks that a domain was registered; nobody fetches the page, and transacting-vs-parked is the highest-value bit in the whole domain signal.
found
0.46n=21
informs the estimate
pricing page
Three tiers, named, with figures. Feeds the ARPU consistency check on the paying-user claim.
found
0.62n=21
informs the estimate
trademark filing
Self-filed, 1(b) intent-to-use, TEAS Plus, attorney field empty. This is the row that opened the file.
found
0.31n=21
informs the estimate
forum acquisition thread
Not expected for this profile — found anyway because she named it, and the named thread exists on the stated date. Unexpected presence informs the estimate; unexpected absence would not have cost her anything.
found
0.18n=21
informs the estimate
dated changelog
Expected at P=0.38 for an operator with a live company domain and a checkout endpoint. Absent, and a direct fetch returned 404. This widens the interval by 3.2 points. It does not lower the score.
expected · absent
0.38n=21
widens the interval +3.2 — score unchanged
open roles posting
Weakly expected. Absent. Widens by 1.4.
expected · absent
0.29n=21
widens the interval +1.4 — score unchanged
public github repo
Not expected for a solo non-technical operator with a company domain. P=0.11 from our own crawl. Absence costs her nothing — this is the row that stops the system re-encoding the network gate.
not expected for
this founder profile
0.11n=21
not penalised — costs nothing
funding announcement
Not expected. She filed a 1(b) intent-to-use mark, which means the product is pre-launch and therefore pre-fundraise by construction. Absence here is the thesis, not a gap.
not expected for
this founder profile
0.07n=21
not penalised — costs nothing
press coverage
Not expected. Most early-stage press is a rewritten founder self-report anyway; our reliability table prices it at +0.2 for that reason.
not expected for
this founder profile
0.14n=21
not penalised — costs nothing

Missing evidence widens the interval and never lowers the score. Hatched rows are absences — the graphite ones our findability prior already predicted for this resource class, so they cost nothing. That asymmetry is what keeps this from re-encoding the network gate: a founder is never marked down for lacking artifacts that someone in their position would not be expected to have.

Detailed founder profileCredibility, build capability and persistent history
Persistent founder memory

Founder evidence profile

Credibility and build capability stay separate.

Two components, both persistent, both append-only. Splitting them is why a credibility problem does not silently erase a build record.

Credibility — claim-verification posterior▲improving
61[48, 74]n=4
0lower bound 48 below 55100
Build Capability — artifact-derived, resource-adjusted▲improving
57.4[41.2, 73.6]n=6
0lower bound 41.2 below 55100
never resetsStored as append-only versions keyed to the person, never to the company. There is no UPDATE and no DELETE anywhere in the worker, so there is no code path that could reset it.
Decision axesFounder, market and idea-versus-market stay separate

Founder

?insufficient data·1pts
55.5[28, 83]n=5
0lower bound 28 below 55100

5 direct observations at this asof, 3 claims verified and 0 contradicted. Prior weight 55% — that share of this number is the reference class, not the person. The persistent Founder Score is one of four inputs here, not a substitute for the axis. 3 absent-but-expected item(s) widened the interval without lowering the point.

Market

?insufficient data·0pts
neutral

Categorical on purpose. There is no number here to average with the other two axes.

0 market row(s) at this asof, stance index 0 from the terms listed, plus a sector prior of 0 carried over from 0 previous Market verdict(s) in b2b_fintech_infra. Categorical on purpose: there is no number here, so there is nothing that could be combined with the other two axes even by accident.

Idea vs Market

?insufficient data·1pts
47.1[18.3, 75.9]n=2
0lower bound 18.3 below 55100

2 scored input(s) at this asof against a NEUTRAL market read. Prior weight 71%. The pivot clause reads build capability out of Memory — the one declared cross-axis link in the system.

How the estimate was formedCold-start prior, history and score definitions

Three different things get called a founder score. They are not the same and we label which is which.

Founder Score (persistent · belongs to the person)1 of 4 inputs into →Founder axis (this opportunity only)1 of 3 axes →never averaged with the other two
inputs to the founder axis: 4n=4

The Founder Score is an input to the Founder axis, not a substitute for it, and neither of them is a single number for the opportunity — because there is no single number for the opportunity.

Cold-start bench

How much is direct evidence, how much is a reference-class prior, and what would narrow the range.

No track record found. Scoring on 4 proxy signals. Prior weight 71%. Interval [42, 79]. Here is what would narrow it.

Prior weight
71%
Direct observations
4n=4
Point
61
Interval
[42, 79]
What this estimate is made of
direct evidence 29%reference-class prior 71%

w = k/(n+k) with k=10 and n=4 direct observations → 10/14 = 0.714. Seventy-one percent of this number is her reference class, not her.

Interval narrowed[48, 74]by 11n=4

This is the bench at first scoring. After the elicitation response landed, the interval narrowed to [48.0, 74.0] with the point unchanged — the evidence bought certainty, not a higher score.

Reference class — contains no pedigree field
Dimensions
two, declared at hour zero: technical-vs-operator × has-company-domain
Technical vs operator
operator
Has company domain
true
N cell
21
N population
63
Thin cell
false
Contains no pedigree field
true
Note
Deliberately two dimensions, not five. A five-dimension class over 63 people gives every cell n=0 or n=1, and a marginal rate wearing a conditional's clothes is worse than an honest marginal rate.
Here is what would narrow it
  • A Stripe payout export covering the three months claimed — resolves the paying-user count outright.
  • A dated changelog on the company domain — expected at P=0.38 for this class and currently absent, which is what is widening the interval by 3.2 points.
  • A second elicitation round on domain experience — the first one moved the width 11 points on three atoms.
  • Any third-party observable naming her as operator: a partner announcement, a directory listing with a date, an integration page.
And what would not
  • A GitHub repository. Not expected for this profile at P=0.11, so its absence is already priced and its presence would tell us little.
  • A larger follower count on any platform. We do not collect it and would not weight it if we did.

Founder score history

Append-only versions preserve the person’s record across ventures.

3059872026-07-18 · 57.3 [38, 76.6] · Northgate Settle · First scored on the trademark filing and the domain probe. Two observations, so the interval is nearly the whole scale.2026-07-18 · 61 [42, 79] · Northgate Settle · Checkout endpoint and pricing page found. Prior weight 71%.2026-07-18 · 61 [45.5, 76.5] · Northgate Settle · Elicitation response received; named acquisition channel verified against a dated public thread.2026-07-18 · 61 [48, 74] · Northgate Settle · Payout receipt fetched. Interval narrowed from 37 points to 26. The point did not move — the evidence bought certainty, not a higher score.2026-07-182026-07-18
  1. 2026-07-1857.3[38, 76.6]· Northgate Settle— First scored on the trademark filing and the domain probe. Two observations, so the interval is nearly the whole scale.
  2. 2026-07-1861[42, 79]· Northgate Settle— Checkout endpoint and pricing page found. Prior weight 71%.
  3. 2026-07-1861[45.5, 76.5]· Northgate Settle— Elicitation response received; named acquisition channel verified against a dated public thread.
  4. 2026-07-1861[48, 74]· Northgate Settle— Payout receipt fetched. Interval narrowed from 37 points to 26. The point did not move — the evidence bought certainty, not a higher score.

Founder–market fit

Domain-exposure evidence with an interval, not a personality guess.

Named in the brief as a soft-skill assessment that should carry a prediction interval. Here is ours, and here is what it is made of.

64.5[49.1, 79.9]atoms: 7n=7
0lower bound 49.1100

Evidence basis: Lived-domain-exposure atoms extracted from her own written text — named counterparties, named settlement windows, a specific failure mode described in the first person. Never the karma, never the follower count.

refusedSeven atoms is a thin basis and the interval says so. This is a construct we score, not a construct we have calibrated.

Milestones

Timestamped observations from the same ledger.

  1. 2026-07-07Self-filed 1(b) mark, no attorneytrademark filed
  2. 2026-05-28Domain live with TLS issuedshipped
  3. 2026-07-16Stripe payout, $412first revenue

The brief says the score sharpens with every milestone. These render as ticks on the history chart; each one is an observation row with a date, not a label someone typed.

Complete recordEvery remaining field, for auditability
Person id
per_mo
Display name
M. O.
Pseudonymized
true
Is real person
true
Refuter enabled
false
Refuter disabled reason
The Refuter is disabled on every real-person entity. We build scored dossiers on named private individuals from public records; running an adversarial generator against a real person is not a thing we are willing to demonstrate.
Provenance class
fixture
Provenance note
Discovered from committed USPTO bulk XML, badged FIXTURE. The filter, the $250 argument and the goods-and-services parse are real; the bulk file is dated and committed rather than pulled live, because the Open Data Portal key needs identity verification a Saturday cannot deliver.
Contact status
form_only
Channels
uspto_tm_1b, domain_probe
First observed at
2026-07-07T00:00:00Z
Sector
b2b_fintech_infra
Region
US
Founder type
operator
Opportunities
opp_northgate
Axes disagree
false
Point-in-time evidence, not company-level trust scores.No outbound message has been sent.