Private Intelligence · Invite-Only

Central File Registry

PRIVATE
INVITE‑ONLY

The whole public record. One honest file.

Dossier assembles a purpose-scoped brief on a person — sourced, upfront about what it can’t verify, and something the subject can claim, correct, or scrub.

Access by invitation only

File status: open Refresh · monthly Every claim cited

A–F G–M INVESTORS FOUNDERS OPERATORS WATCH
  • 01

    Purpose-scoped brief

    Built for the reason you state — one relationship question, not a general data dump.

  • 02

    Every claim cites a source

    No field without a citation, or an honest gap marker in its place.

  • 03

    Clearance, not character

    We verify identity and record — never a verdict on someone’s worth. There is no score anywhere in the system.

  • 04

    Claim, correct, or scrub

    The subject can claim their file, fix what’s wrong, or have it removed.

Where every line in a file actually comes from.

Dossier does not crawl the web for whatever it can find. It runs a fixed pipeline against named public sources, attaches a citation to every claim it keeps, and labels the confidence of everything it can’t stand behind. Here is the whole of it, in order.

  1. 01

    You declare a purpose — before we look at anyone

    The purpose gate runs first, before the subject is even looked up. Five purposes are permitted: investment diligence, partnership, introduction, business development, general professional.

    Four are refused outright — employment, tenancy, credit, and insurance — because those are consequential eligibility decisions about a person. An unknown purpose is refused too, rather than assumed. Every decision, accept or reject, is written to an audit record with your stated reason verbatim.

    “Dossier does not serve employment, tenancy, credit, or insurance decisions — this is a structural refusal, not a policy toggle.”

  2. 02

    The intake gate decides whether a file opens at all

    A subject qualifies only if discovery finds at least two independent anchors from different classes of source — today that means corporate filings and authored work. One anchor per source: two mentions in the same registry is still one anchor.

    Personal-life signal never counts as an anchor. If the threshold isn’t met, no file is opened and you get a refusal instead of a thin, speculative profile.

    The point, stated plainly in the spec: an envious ex or a fixated stranger cannot get a file on a private person, because there is no file to get.

  3. 03

    We query the public record — these sources, by name

    Only registries, filings, and publications that are already public.

    Corporate & registry

    • SEC EDGAR
    • Companies House
    • GLEIF
    • OpenCorporates
    • USPTO
    • IRS Form 990
    • ProPublica Nonprofit Explorer

    Scholarly & identity spine

    • Wikidata
    • Wikipedia
    • OpenAlex
    • Crossref
    • PubMed
    • Semantic Scholar
    • DBLP
    • arXiv
    • OpenReview
    • Zenodo
    • VIAF
    • Open Library
    • Google Books

    Public expression & activity

    • GitHub
    • Hacker News
    • Reddit
    • Stack Exchange
    • Substack
    • Bluesky
    • Mastodon
    • personal sites & RSS
    • Internet Archive

    Clearance — gated, run only on explicit request

    • OpenSanctions
    • CourtListener
    • GDELT

    Evaluated and refused

    • data brokers
    • consumer reports
    • username-enumeration tools
    • scraped private accounts

    The username-enumeration tool cluster was rejected on inspection: it is built on password-reset side channels and violates the terms of every provider it touches. We don’t buy broker files, and we don’t scrape accounts that block automated access.

  4. 04

    Identity is resolved before anything is attributed

    A name is not an identity. A candidate profile only attaches to a subject if it points back at something already confirmed — it links to a known domain, reuses a confirmed handle, or names a confirmed alias in its own title.

    Anything that can’t be tied back stays labelled as a lead rather than quietly folded in as fact.

  5. 05

    Every claim carries its source — and disagreements survive

    Provenance attaches at collection, not afterwards: each fact stores its source URL, source type, a confidence score, an evidence quote, and a timestamp.

    When sources conflict on the same field, the most recent observation wins and confidence is only a tiebreak — deliberately, so that a stale high-confidence “no match” can never outrank a newer true one. The value that lost still keeps its citation in the ledger.

  6. 06

    Every field is state-labelled

    You always know which tier of confidence you’re reading. Nothing is presented flatly as fact.

    • DiscoveredFound in an open source, not yet tied back to this subject. The default for every new fact.
    • CorroboratedA second independent signal points at the subject — but not yet promoted.
    • ConfirmedCross-confirmed to this subject. The only state that earns the verified badge.
    • DisputedSources contest the claim. The value is suppressed; only the fact of the dispute shows.

    The label on the unverified column, verbatim: “Found in open sources, not yet cross-confirmed to this subject — may include namesakes. Shown as leads, not established facts.”

  7. 07

    A failed check is never published as a clean result

    This is the rule we are proudest of. Sanctions and litigation lookups return one of three things: a result, no result, or unavailable — and “unavailable” is never allowed to collapse into “nothing found.”

    If a clearance source fails, the file records only that the screening did not complete, and the dossier carries a visible SCREENING INCOMPLETE stamp.

    “sanctions screening did not complete — no conclusion may be drawn from its absence”

    And a name that matches a sanctions list is recorded as a candidate for human review, never a verdict — stored at lower confidence, flagged as needing date-of-birth and nationality cross-validation before anyone treats it as real.

  8. 08

    Scout answers follow-ups — or says nothing

    Scout is the analyst on the file. It may only render a claim whose source is an exact member of the set of sources fetched before the model was ever called — no prefixes, no normalisation. An invented or altered citation is dropped, not corrected.

    If nothing survives that check, Scout’s summary is suppressed too. It gets quieter as the evidence thins, instead of more confident.

    Four things Scout will not do, at any clearance level

    • Protected traitsIt will not infer health, sexuality, religion, politics, race, or genetics. It reasons from what the subject has said or done, never from what a model guesses they are.
    • Risk from personalityIt will not predict risk, criminality, or trustworthiness from personality. A name or a profile is never a verdict.
    • Vulnerability strategyIt will not build an approach that keys on financial distress, grief, addiction, cognitive decline, or job loss. The objective is mutual upside, not leverage.
    • Regulated decisionsIt will not advise on employment, tenancy, credit, or insurance — and will not answer around the refusal at the gate.

    A refusal is always a stated reason, never silence.

  9. 09

    The subject gets the last word

    Anyone with a file can claim it, correct it, or have it scrubbed. A correction from the subject outranks an inference from us, and the deletion path preserves the record of what was wrongly asserted rather than quietly erasing it.

Anatomy of a dossier

Every section of a real file, and why each one earns its place.

This is the full structure of a Dossier brief — every section a file can contain, in the order it is assembled, from the cover sheet through the evidence ledger. The numbered notes explain what sits in each section and what it actually tells you before a meeting.

Synthetic subject · Elena Voss and every value below are fabricated for illustration. No real person, company, or record is represented.

TOP · SECRET  ·  CENTRAL DOSSIER REGISTRY  ·  SYNTHETIC SAMPLE  ·  TOP · SECRET
1

Cover & File Meta

The file’s own paperwork

File no.
DX‑04471
Subject codename
HALCYON‑VOSS
Clearance
Tier III — Network
Purpose on file
partnership
Last indexed
2026‑09‑14
Source count
9 sources · 31 fields
Registry hash
Q00SYNTH
Next refresh
monthly
2

▦ Known Aliases

3 / 7 masks on file

GH
GitHub
BS
Bluesky
SS
Substack
NO MASK
Instagram
NO MASK
TikTok
3

Subject Block

Identity spine

Legal name
Elena Voss confirmed
Preferred
Elena self-maintained profile
Pronouns
she/her self-maintained profile
Born
1986 Wikidata
Citizenship
no public record
Resides
Lisbon, PT Wikidata
Languages
EN, PT discovered
4

Screening Status

Process state — not a finding about the subject

SCREENING INCOMPLETE
Sanctions
did not complete unavailable
Litigation
complete · no match CourtListener
Adverse media
not run — requires authorization gated

No conclusion may be drawn from a screening that did not complete.

5

Quick Contact

Reachable channels only

Email · work LinkedIn Website Call — not on file Text — not on file Signal — not on file
6

Recent Changes

Rolling 60-day window

  • New filing · Series B, Halcyon Robotics SEC EDGAR
  • Two new preprints posted arXiv
  • Prior employer corrected by subject subject correction

———— RESTRICTED · BELOW THIS LINE ————

Everything above is the cover. The remainder of the file — cross-identifiers, operational history, psychological synthesis and source provenance — is gated. A reveal requires a stated purpose and a reason, and every access is permanently logged.

  • Tier III clearance required
  • Reason must be supplied
  • Access audited monthly
7§ 01

Cross-Identifiers

Public handles & IDs

✓ Cross-Verified
Registry
Q00SYNTH Wikidata
Research
0000-0002-SYNTH ORCID
Code
@evoss-halcyon GitHub
Filings
CIK 000SYNTH SEC EDGAR
Unverified

Found in open sources, not yet cross-confirmed to this subject — may include namesakes. Shown as leads, not established facts.

Social
@evoss_synth discovered
Forum
evoss discovered
8§ 02

Operational History

Employment · Education · Founding

Current posting

Role
Founder & CEO, Halcyon Robotics SEC EDGAR
Since
2019 Wikidata

Known appointments

  • Board observer, Meridian Automation SEC EDGAR
  • Technical advisor, two seed companies discovered

Education

  • MS, Mechanical Engineering Wikidata

Companies founded

  • Halcyon Robotics · 2019 · active Companies House
  • Kestrel Systems · dissolved disputed — date contested
9§ 03

Expression & Themes

Writing · Talks · Voice

Voice
Technical, low-promotional, numbers-first inference

Recurring themes

  • Manufacturing reshoring Substack
  • Compliant actuation control OpenAlex
  • Skepticism of end-to-end autonomy claims Hacker News
10§ DEEP

Deep Brief

Curated from public sources

Career arc

Research track → hardware operator. Published before founding, and kept publishing after. inference

Top signals

  • Series B closed this quarter SEC EDGAR
  • Two preprints in eight weeks arXiv

Currently hiring

  • Controls engineer · mechanical lead personal site

Portfolio · notable projects

  • HX-1 actuator platform Zenodo

Academic output

  • 6 papers · compliant actuation OpenAlex
  • Cross-indexed Crossref DBLP

Code releases

  • 2 public repositories GitHub

Press coverage

  • 4 trade features · 1 keynote GDELT
11§ 04

Known Associates

Circle · Mentors

Business / circle

  • Co-founder, Halcyon Robotics Companies House
  • Lead investor · Series A & B SEC EDGAR

Connected to

  • Two co-authors · actuation research OpenAlex
Family / relatives
never collected
12§ 05

Recognition

Awards · Exits · Funding

  • Award · 2024 · hardware category Wikidata
  • Funding · 2026 · Series B SEC EDGAR
  • Exit · 2017 · Kestrel Systems discovered
13§ 06

Psychological Profile

Soul synthesis

Inference layer — not evidence. Read off public expression, labelled as inference, never promoted into a verified field and never a judgment of character.

Vibe →
precise · dry · unhurried inference
Role →
builder-operator inference
Risk →
conservative on claims, aggressive on scope inference
Core motivation
Wants the hard version to work inference
14§ 07

Interests & Approach Vector

Pre-brief

Hobbies

  • Long-distance cycling personal site

Subcultures

  • Open-hardware community GitHub

Not yet wired

  • Reading list — extractor pending
  • Music · films · sports — extractor pending
15§ 7B

Likes · Dislikes · Palate

Personal taste · surmised from public posts

Likes
Walking meetings Bluesky
Dislikes
no public signal
Food / palate
Vegetarian — stated publicly Bluesky
16§ 08

Appendix — Provenance

Evidence ledger · 31 fields

Evidence ledger: each field, its source, confidence, verification state and privacy tier
FieldSourceConfVerifiedPrivacy
career.title.currentSEC EDGAR0.94confirmedpublic
identity.legal_nameWikidata0.91confirmedpublic
identifiers.orcidORCID0.88confirmedpublic
expression.academic_papersOpenAlex0.86corroboratedpublic
handles.blueskyBluesky0.62discoveredpublic
career.companies_foundedCompanies House—disputedpublic
risk.sanctions_statusOpenSanctions—unavailablesensitive-public
Retention · 90 days Refresh · monthly Privacy · tiered Delete on request
  • Aggregates public-record and shared-network information only.
  • Sensitive-public fields require an authenticated reveal request, and every access is logged.
  • Identifiers are cross-validated against Wikidata.
  • The subject can request correction or removal at any time.

The most important part of the file is what isn’t in it.

These are excluded structurally — stripped upstream of anything that renders, by three separate passes that prune the data, its provenance, and then walk the whole document again to catch anything the first two missed. No purpose, clearance level, or price unlocks them.

  • Family & relativesNo family tree, no partner, no parents, children, or siblings. Household composition is not a business asset.
  • Home & mailing addressWhere someone lives is not business information, and it never counts as evidence a person is public.
  • Personal lifeRelationships, health, beliefs, and private circumstance never enter a brief.
  • Criminal & consumer reportsThe regulated-report line Dossier does not cross — refused in design, not merely switched off.
  • Any score or rankingThere is no per-person score, rating, or criminality prediction anywhere in the data model. There is nothing to leak, sell, or misuse.
  • MinorsExcluded by policy regardless of what happens to be publicly available.
✓ A brief may say

“She’s written about supply-chain resilience three times since March — lead with that.”

✗ A brief may never say

“She’s status-motivated; mirror her cadence and invoke scarcity.”

INSUFFICIENT PUBLIC RECORD
— NO FILE OPENED

And when the public record is too thin to support an honest brief, this is what comes back instead of a profile. No partial file, no “here’s what we found anyway.” A refusal is a valid, common, intended outcome.

The subject outranks the analyst.

Anyone who appears in Dossier can act on their own file, and a correction from the subject beats an inference from us permanently. Requests are recorded and reviewed — never acted on the corpus automatically.

  • Claim

    Verify you’re the subject and take ownership of the file — see everything it holds and where each line came from.

  • Correct

    Fix what’s wrong. The correction is recorded, outranks the inferred value, and shows up in Recent Changes.

  • Scrub

    Have the file removed — with the deletion itself recorded, so the audit trail of what was wrongly asserted survives.

If you believe there is a file on you and want to see it, write to us and say so. Subject requests are handled by a person, not a form.

Dossier is invite-only.

Access is granted to members of a contracted network, under a stated purpose. If that sounds like your table, ask for an invitation and tell us what you’d use it for — the purpose is the first thing we’ll ask anyway.

Every request is reviewed by a person · No self-serve signup