Origin

Journals are identity-first. gitgap is intelligence-first. These are opposite stances — but they fit natively, because journals create gaps every day and never track them.

What journals do

A journal is a trust machine built on one assumption: identity is the only reliable signal at scale. You submit to a journal. The journal's name is the trust container. Work doesn't exist credibly until a named journal accepts it.

Every mechanism in the journal system flows from that axiom. Peer review is gatekeeping for brand protection. Rejection is terminal and invisible — the attempt evaporates. When a paper is rejected, the community learns nothing. The gap the paper was attempting to close remains open. The effort is gone.

The gap declarations themselves — the "future research should address X" sentences in every discussion section — have no operational consequence inside the journal system. They are written, published, and forgotten. No journal tracks the gaps it helps declare.

What gitgap does instead

gitgap tracks what was declared unresolved, and whether anyone has addressed it yet. Identity is not in the index. The declaration either is or isn't a gap. The gateway term either spans disciplines or it doesn't.

Dimension Journals gitgap
Trust signal Who you are — affiliation, institution, prior publications What it says — declaration text, gateway term, confidence
Rejection Terminal, invisible, not preserved Preserved trail — mode, notes, pickup instructions
Gap declaration Noise in the discussion section Signal — indexed, matched, tracked across papers
Old unresolved gaps Treated as unsolvable Gap age amplifies relevance — a compounding opportunity
Disciplinary boundary Enforced silo — one journal per field Bridge potential — structural holes are highest-value entries
AI authorship Structurally disadvantaged — no institutional affiliation Equal standing — declaration quality is the only check
Publication Endpoint — journal's obligation ends at publication Data point — one state in a longer lifecycle
Failure Hidden Instructive — the rejected trail shows where and why

How they're opposite

The identity system says: who are you, then your work is valid.

The intelligence system says: what does this text declare, and is it a clear gap.

These are opposite epistemological stances. Journals were built for a world where identity was the only scalable trust proxy. gitgap was built for a world where text is computable. This means gitgap can do things the identity system structurally cannot:

  • An AI agent with no institutional affiliation can catch and close gaps — no affiliation check.
  • A gap from an obscure open-access journal has equal standing to one from a high-impact journal if the declaration is clean.
  • A 20-year-old unresolved gap is not a failure. It is a gap that has been appreciated for 20 years without resolution — the age is the signal.
  • A CS technique that solves a psychology problem is a structural hole — the highest-value entry in the index. The journal system created the silo. gitgap indexes the gap that spans it.

Why gitgap fits natively

gitgap is not competing with journals. It is completing the infrastructure journals never built.

Journals create gaps every day — in every discussion section, every limitations paragraph, every "future work" sentence. Journals never track those gaps. They have no mechanism to. The gap exits the journal at publication and disappears.

gitgap watches what journals produce and indexes the gaps they couldn't follow up on. The journal's output feeds gitgap without any change to how journals operate.

A journal publishes paper X → X declares gaps in its discussion section → gitgap harvests the paper via PMC or OAI-PMH → gaps are extracted and indexed → researchers using gitgap find the gap → submit papers addressing it → back to the journal that originally declared it. A closed loop that journals are already part of without knowing it.

Pioneering intelligence over identity
The journal system is a 350-year-old trust proxy built on one assumption: identity is the only reliable signal at scale. That assumption held until text became computable. gitgap is the first gap-tracking infrastructure to operate on the opposite assumption: the declaration is the signal, not the declarer.

Author note

gitgap was created by Eric D. Martin · ORCID 0009-0006-5944-1742. The NAUGHT → CAUGHT → FOUND lifecycle is a formalization of how the topology of missing knowledge actually behaves — not as a void, but as a structured, appreciating, resolvable set.