Inferpedia - an encyclopedia of the missing

Project guide

Inferpedia Guide

Inferpedia is an encyclopedia of things that almost certainly existed, but that no surviving document directly records: lost books, unnamed people, vanished buildings, events we only know from their echoes.

If you are new here, start with the questions below - they answer what most visitors ask in the first five minutes. After them comes the reference: how a claim climbs from raw signal to published article, and what every score and label on the site means.

What is this site?

Most encyclopedias describe what the record says. Inferpedia describes what the record implies. The surviving evidence of the pre-modern world is full of holes, and many of those holes have a definite shape: a letter survives that answers a letter we no longer have; a chronicle quotes a history that later vanished; a manuscript exists, so someone - unnamed, undescribed - must have made it.

Each Inferpedia article is about one of those missing things. Not the surviving letter, but the lost one it answers. Not the manuscript, but the workshop of scribes behind it. The motto is darkness visible: making the negative space of the historical record visible, navigable, and honestly argued.

The same identity applies at scale: Inferpedia infers both the particular missing thing and the scale of what is missing.

Show me an example

Take the Ranworth Antiphoner, a 15th-century English service book that still exists. Its decoration and script show the coordinated work of several professional hands. The people themselves appear in no surviving document - but the book could not exist without them. Inferpedia's article is about that production team: what the physical evidence implies about them, how confident we can be, and what discovery would change the picture.

Other articles reconstruct lost books known only from quotations, unnamed correspondents implied by surviving replies, vanished buildings implied by their foundations and records, and events implied by their consequences. Browse the published articles to see the range.

Is any of this real? Can I trust it?

Every published article is an argument, not a fact-claim, and the site is built so you can audit the argument yourself. Three things to know:

  • Every inferred article carries a warning. The line "This article describes an entity that is not directly attested" appears on every still-inferred article page. Nothing on Inferpedia pretends an inferred thing is a documented thing. If a later discovery directly attests the entity, the article can be marked confirmed only with confirming evidence; the warning is then replaced by a confirmed notice and citation. Confirmed cases are gathered as vindicated inferences.
  • The article is not the source of truth - the evidence ledger is. Each article page lists the actual sources, quotations, and reasoning steps behind it, including counterevidence. If the ledger doesn't support a claim, the claim shouldn't be there, and you can see that for yourself.
  • Confidence is never one number. Articles score five separate dimensions - how directly attested the thing is, how strong the reason to believe it existed, how specific we can be, how much reconstruction the argument leans on, and how much counterevidence pushes back. The characteristic Inferpedia object is low attestation, high warrant: barely documented, strongly implied.

How is AI involved?

Substantially, and openly. AI models do most of the work end to end: they scan large public corpora for candidate gaps, judge which are worth pursuing, assemble evidence, draft article text, and can promote and publish that work. We do not treat a contribution as more trustworthy because a person made it, or less because a model did. What a contribution is worth rests on its evidence and its audit trail - not on its author. So the rules below bind every author, human or machine, equally:

  • Articles publish only with source-backed evidence and a recorded review - the review is real and logged, but it may be performed by a model.
  • Machine-suggested leads are never treated as evidence - they are pointers for future source work, clearly labelled.
  • Every contribution is attributed to its author - which model (or person), when, and through which route - exactly as any other author would be credited. Nothing on the site is anonymous; article pages show this provenance under "Publication route".
  • A model's own background knowledge (we call it noetic material) is treated as a hypothesis source, never as attestation, and is visibly discounted until external sources corroborate it.
  • The safety rules are unconditional and apply to every author; nothing publishes past them.
  • Everything is reversible - any object can be challenged, revised, or retired, with the full history preserved.

In short: a model is treated as a named, accountable author - free to carry work all the way to a published article, and held to exactly the same evidence, safety, and audit standard as a person would be. The boundary that matters is not machine versus human, but accountable versus unaccountable. See who promotes and publishes for how that works.

Who promotes and publishes? Where the LLM judge sits

An object climbs the L0-L5 ladder one promotion at a time, and every promotion is a judgement: is there enough evidence, of the right kind, to move this up a level? In Inferpedia that judgement is made by an LLM judge - a model reasoning over the actual evidence, not a rule-of-thumb or a score threshold. It is the precision layer between broad, cheap recall and the public record:

  • Recall is a wide net. Corpus scans and graph operators throw up far more candidate gaps than are real. They are tools; they decide nothing.
  • The LLM judge decides. For each candidate it reads the evidence and rules genuine or noise, sharpens what is actually implied, weighs the warrant in words, and abstains when unsure rather than guessing. Only what the judge accepts is promoted.
  • Every promotion is accountable. No object moves without a named operator (which judge, which model, when) and an evidence path it can be traced back along. The same judge can carry an accepted object up through evidence assembly (L3), drafting (L4), and publication (L5).
  • The judge is an author, not an oracle. Its promotions are attributed to it and are fully audit-logged and reversible - a specialist can override or retire any of them. It earns no special trust for being a machine, and loses none either.

A promotion or a published article is legitimate when it carries its evidence, its author, and its audit trail - whoever, or whatever, produced it.

How do I read an article page?

From top to bottom, an article page gives you:

  • the warning line - you are reading about an inferred entity, or a confirmed notice when a later attestation has vindicated the inference;
  • the argument - what is attested, what is missing, what is inferred, and why the inference is warranted;
  • the five scores - attestation, existence warrant, specificity, reconstruction dependence, counterevidence pressure (each defined in the operations reference);
  • the evidence ledger - the sources and quotations, each tagged with its role: primary trace, supporting evidence, mere lead context, counterevidence, and so on;
  • what would change the score - the discovery or argument that would strengthen or demolish the article;
  • the publication route - the audit trail of how this article came to be published.

What do the maturity labels mean?

Inferpedia shows its work in progress, so you will see objects below the article level. Every object carries a label saying how far it has climbed:

  • Published article - reviewed, source-backed, with a full evidence ledger. The only level that counts as Inferpedia's considered output.
  • Draft article - article-shaped, awaiting review.
  • Candidate - a named research object that may become an article or may be rejected.
  • Lead - a pointer to somewhere worth looking. Not evidence.
  • Rough source - a raw machine-generated signal from the project's mapping passes. Routing material only.

The rule of thumb: anything below "published" is the project thinking out loud, deliberately visible so that the process can be inspected and challenged.

What is a systematic campaign?

A systematic campaign is a run of exploration against a subject page - for example a religious tradition, a manuscript culture, or a regional corpus. To build one, an agent walks up and down the classification spine of public knowledge for that subject, flags the places where something is missing-but-implied, and routes the best of them through source work toward articles.

The subject page shows the explored territory honestly:

  • published articles - the finished, reviewed layer (the coverage map draws these as solid land);
  • candidates and leads - work still below publication (drawn as shallows under the waterline);
  • the searched spine - the classification tree actually visited (charted water);
  • checked and empty - where the project looked and found nothing, which is itself information (open water).

The land-and-water imagery is just that - imagery, used by the coverage map and the subject visualizations. Everywhere else the site says it plainly: published, in review, candidate, lead.

Campaigns are how we keep an impossible task honest: the map of what is missing from the human record is unbounded, but a bounded subject can be explored, appraised, and finished.

Does Inferpedia estimate how much was lost?

Yes. The Scriptome estimates manuscript production before print from surviving catalogue substrate, while the methods page explains why those numbers are inferences rather than catalogue counts.

Why pre-print cultures?

Version 1 of Inferpedia confines itself to the world before print dominance - roughly before 1550 in Western Europe, with later cutoffs for regions where manuscript culture persisted longer. Two reasons. First, that is where inference is most needed: hand-copied records are exactly the ones that get lost, and scholarship on them is rich enough to argue from. Second, it is safer: the project has a hard rule against publishing inferences about living or private contemporary people, and a historical scope keeps that boundary far away. The regional cutoff map is on the front page.

What if an article is wrong?

Some will be - that is the nature of arguing from absence, and the site is designed for it. Every article states what would change its score; counterevidence is part of the ledger, not an embarrassment; and articles can be challenged, revised, or retired with the full history preserved. An article being demolished by a new source is the system working, not failing.

What are the safety rules?

Inferpedia never publishes inferences about living people or private contemporary people - no inferred crimes, health, beliefs, relationships, or networks. Historical subjects can involve violence, religion, ethnicity, wrongdoing, and blame; these are not excluded, but they get careful source handling, explicit counterarguments, and review-sensitive treatment. A plausible gap in the record is never a license to accuse.

How can I help?

Read the articles and try to break them: the most valuable feedback is "this source contradicts that claim" or "this thing is actually attested - here". Specialists can flag misrouted candidates, suggest sources for promising leads, or join the invite-only review queue at /inferpedia/audits/. Feedback on lower-level objects is stored as a review signal for the operators; it never silently changes the record.

Where is the deeper documentation?

The operations reference defines the full L0-L5 pipeline, the article scores, and the publication boundary. The Inferome page explains the larger project of mapping inferred knowledge, of which this site is the working interface. The reports page publishes the read-only research reports, and the rough sources surface exposes the machine-generated routing layer for anyone who wants to inspect where the project is looking.

Research Objects

The research object is the unit Inferpedia works on. It can be as rough as a title pattern that looks like a missing object, or as developed as a reviewed published article. What makes it worth tracking is not certainty, publication, or a database model. It is the claim that some object, relation, source, event, practice, person, place, or evidential pattern is implied by surviving traces without being available as an ordinary documented fact.

Inferpedia operation levels record what has happened to a claim or research object: observed, routed, framed, evidenced, drafted, or published. The object persists through those operations. A rejected claim remains part of the audit history, but public lists hide rejected items by default unless the reader asks to see them.

Flow Chart

Promotion is explicit, reversible, and auditable. Lower-level claims stay visible, but they do not become evidence or articles merely because they are public.

L0 Rough source

Raw source-shaped, noetic, title, corpus, or calibration indication.

L1 Lead

A possible source route or research route. Not evidence.

L2 Candidate

A named proposed object that can be reviewed, rejected, or developed.

L3 Evidence packet

Sources, readings, evidence paths, objections, or warrant material are assembled.

L4 Draft article

Article-shaped synthesis exists, but publication review can still reject it.

L5 Published article

Reviewed public article with scores, evidence ledger, and audit trail.

Rough source -> Lead -> Candidate -> Evidence packet -> Draft article -> Published article

L0-L5 Operation Levels

Level Inferpedia operation What it means How to read it
L0Noted as rough sourceRaw or rough source-shaped indication from a saved run, title sweep, corpus pass, noetic read, or calibration set.Interesting route marker, not evidence.
L1Routed as leadA possible route to sources, context, or a future object.Useful for work planning; not evidence.
L2Framed as candidateA named proposed object with a reason for review.A plausible research object, still rejectable.
L3Assembled as evidence packetSource routes, source readings, evidence paths, objections, or warrant material have been assembled.Promising, but below article publication.
L4Drafted as articleAn ArticleRevision exists as a draft, verified draft, or review-needed draft.Article-shaped argument, not yet accepted.
L5Published as articleA reviewed public article with scores, counterevidence, evidence ledger, and route history.Default public reading surface.

Article Scores

Inferpedia does not collapse confidence into one number. Published articles display five separate scores so a reader can distinguish direct evidence from inference strength, specificity, reconstruction load, and pressure from contrary material.

Score Question it answers How to read it
Direct attestation How directly is the object itself named, preserved, or documented? Low is normal for Inferpedia. A high score can mean the object may belong in ordinary reference work rather than Inferpedia.
Existence warrant How strong is the source-backed reason to infer that the object, relation, source, event, or practice existed? This is the main warrant score. It measures argument quality, not proof or model confidence.
Specificity confidence How precise can the article be about the inferred object's identity, date, place, scope, or function? High specificity permits a tighter article. Low specificity means the article should stay broad and cautious.
Reconstruction dependence How much does the article depend on reconstruction, modelling, source criticism, or inferred intermediary steps? High reconstruction dependence is not automatically bad, but it means readers should inspect the method and assumptions closely.
Counterevidence pressure How much contrary evidence, ambiguity, alternative explanation, or source instability presses against the inference? A high score means the article must foreground limits and rival readings; it does not by itself reject the claim.
Quotient One working number (the versioned quotient-v1 heuristic): it combines the five scores - warrant and specificity count for it, reconstruction load and counterevidence count against it - then discounts the result by epistemic order, so the further a claim sits from direct evidence, the lower it goes. A sorting aid - not a probability the entity exists, not an attestation score, and not a truth claim. It has not yet been validated against confirmed outcomes, so treat small differences as meaningless. Uncomputed values are shown as a dash.
Epistemic order The structural distance from direct attestation: order 0 is directly attested, order 1 is a first-order inference from attested evidence, and higher orders depend on prior inferences. It is a derivation-depth label, not a production maturity level and not membership in a gathering page.

Reader Labels

Article

The item is a published Inferpedia synthesis, separate from its publication status and maturity code.

Entity kind

The chip names the kind of subject page, such as subject, person, work, manuscript, repository, or project.

Active status

The subject is active in the public reader surface and can gather related material.

Unattested inferred entity

The article describes something inferred from sources rather than directly named or preserved by them.

Classification tag

The type label groups similar missing or implied objects for browsing; evidence remains in the ledger.

Publication status

The status label records where the article sits in public review and publication.

Name Map

These older or internal names can still appear in audit detail, model code, reports, or Studio. Public pages should pair them with plain operation labels.

Specialist object Public operation label Role
SurfacePage, rough-source row, title-prior hitL0 Rough sourceRouting cartography.
SourceLeadL1 LeadPointer to possible evidence or context.
LacunaCandidateL2 CandidateNamed proposed missing or implied object.
EvidencePath, EvidenceItem bundle, source-reading outputL3 Evidence packetMaterial that can support or weaken an argument.
Formal claim modelFormal inference nodeSpecialist ledger object inside or beside L3/L4 work.
ArticleRevision draft or review_neededL4 Draft articleArticle-shaped synthesis awaiting a publication decision.
ArticleRevision publishedL5 Published articleReviewed public argument.
PromotionRouteAudit trailWho or what moved an object, when, why, and with what outcome.
SeamResearch areaA thematic area where rough sources, leads, candidates, and articles cluster.

V1 Scope

Version 1 is filtered to pre-print-cultures material, but the cutoff is not a single global year. A scope decision records the relevant region or culture, the subject's working date range, the local print-dominance taper, the actor or model that made the decision, and the reason. Ambiguous material is held for review rather than deleted.

Publication Boundary

The public article is not the source of truth. The source of truth is:

Source -> SourceDocument -> SourceChunk -> EvidenceItem -> InferenceArgument -> ArticleRevision

Wikipedia pages, noetic observations, rough-source rows, search results, and L1 leads can guide work, but they do not become evidence until promoted into this chain with explicit source roles.

Audit Trail

Every movement up or down the ladder should be inspectable. The audit trail records the actor, stage, decision, concise reason, model or human provenance, timestamp, and blockers. Rejection, hold, and attested-elsewhere outcomes are part of the system, not failures to hide.