e eDossier v0.1 · in development

The people behind esports · ownership, capital, governance

Evidence before narrative.

A dossier platform where every sentence is a claim with a source, a locator and a lineage — not a paragraph someone typed and hoped you would trust.

Design prototype, no login. Every record in it is fictional sample data — see the notice at the end.

Method

The order of operations

Most “intelligence” products start with a conclusion and work backwards. This one has a fixed pipeline that cannot be skipped — each stage is a table, not a vibe.

01

Sources, with provenance

Originals and derivatives are separate records: retrieval state, original language, translator, locator, SHA-256, licence. A URL is not proof; it is an address.

RuleTen translations and reposts of one article are one source. Unknown dependence is not independence.
02

Claims, not paragraphs

Every durable statement is a typed claim — fact, reported, allegation or assessment — with attribution, valid time, record time and evidence links. Published claims are append-only: a correction creates a new version.

Rule“Reported” proves that X said Y, never that Y is true.
03

Composition by reference

A dossier is a sequence of typed blocks pointing at canonical claims and entities. Nothing is copy-pasted, so a corrected claim flows into every dossier that cites it — and flags the ones that go stale.

RuleFour axes stay independent: relevance, evidence quality, impact, analytic confidence.
04

Review, then publication

An agent can file a research batch into staging. A human accepts or rejects it. Accepting means “may enter the knowledge base” — verification and publication are two further, separately logged acts.

RuleNo tool lets an agent approve, verify or publish. Ever.

Screens

Three views of one record

Brief for reading, Casefile for structure, Evidence for provenance. Same data, three densities — captured from the working prototype. Click any screen for full size.

Research Inbox: a research batch submitted by an agent, its source lineage tree, and three claim proposals awaiting a human decision
Research Inbox agent batch · lineage tree · per-claim decision, keyboard-driven open live →
Dossier editor: EIDS-01 outline on the left, typed blocks in the document, evidence inspector on the right
Dossier editortyped blocks · evidence inspectorfull size ↗
Published brief with key judgments and an evidence drawer listing supporting and contradicting sources
Published briefkey judgments · footnotes to evidencefull size ↗

The dossier standard · EIDS-01

Twelve sections, fixed anatomy

Same structure for every subject, so a reader always knows where a judgment lives and where its evidence is. Conditional sections may say “not established” — never filler invented to look complete.

00Document controlcore
01Executive intelligence briefcore
02Identity & backgroundcore
03Chronology & milestonescore
04Organizational affiliationscore
05Ownership & control — equity, votes, beneficial ownership, operational controlconditional
06Capital & financial interestsconditional
07Relationship & influence network — evidenced links only, never inferredcore
08Significant events & controversiesconditional
09Analytic assessment — alternatives, reasoning, confidence, limitscore
10Evidence registercore
11Research gaps & revision logcore

EIDS-01 is an internal convention that synthesises public analytic-tradecraft and investigative practice. It is not an official intelligence-community standard and carries no classification markings.

Status · 2026-10-23

What exists today

Stated plainly, because a dossier platform that overstates its own provenance would be a joke.

Working

  • Design system and token set (docs/DESIGN.md)
  • Interactive prototype: inbox, editor, reader + evidence drawer
  • Specification v0.3.0 — data model, agent contract, acceptance tests
  • Two architecture decisions: stack & editor; the agent boundary
  • This site, deployed to Cloudflare at edossier.tech

Not yet

  • PostgreSQL schema and migrations
  • Authenticated API and an agent staging endpoint (how a researcher files a batch)
  • Review log, canonical commit, immutable published snapshots
  • Any real dossier — every record here is fictional sample data

Sample data notice. The screens and the prototype use invented entities — Periphery Gaming, Dahlia Holdings, and people who do not exist — so that no real person is described by an unverified claim. Nothing on this site is reporting, and no claim shown has been through review.

A dossier you can audit, or no dossier.

The first real casefile — an esports ownership and control chain built from corporate filings — is the next milestone. Until it passes its own review gate, it does not get published.

Corrections, source tips or a takedown request: hello@edossier.tech. A correction to a published claim starts a revision, not an edit.