QNFO Papers
PapersAsk the corpusIdeasArchiveAboutWork with me

Quick read · plain language

Fixing Gaps in a Big Science Project

A plain-language version of “A Consilient Gap Synthesis of the QNFO/QWAV Research Portfolio”

3 min readNo jargon, no mathematicsAI & knowledge

The short version

A huge research project had 42 unfinished tasks. The author sorted them into five types and made a plan to fix them in order. A few key tasks block many others, so fixing those first saves work.

The project and its problems

The QNFO/QWAV research project is very large. It has 95 smaller projects, over 900 papers, and many tracking systems. The author looked at seven information sources to find what was missing or broken. These sources included a knowledge graph, a paper database, project handoff notes, and memory records.

The author found 42 gaps. A gap is a missing piece — like a broken tool, an unpublished paper, an unchecked science claim, a missing rule, or work not shared with the public. Each gap got a severity level: blocking, high, medium, or low. Each got an effort size: small, medium, large, or extra large. The author also recorded which gaps must be fixed before others can start.

How the gaps connect

The gaps form a chain of dependencies, like building a house: you need a foundation before walls, and walls before a roof. The longest chain has three steps. One key gap sits at the start: a "consistency engine" that would automatically find mismatches between systems. Without this tool, problems are found only by accident. Another early gap is recovering lost files from backup storage after a code repository was destroyed.

The author checked that no loops exist in the chain. A loop would mean two gaps each block the other, making a straight-line plan impossible. No loops were found.

The five-part fix plan

The plan has five releases over about eight weeks, though some parts can run at the same time to save two weeks.

First, build basic tools. This unblocks about two in five later gaps. Second, fix paper records and cross-references. Third, finish governance rules. Fourth, check physics claims. Last, share work publicly.

A risk remains: one social media login expired. Until the owner refreshes it, the final sharing step cannot finish. But this blocks nothing else.

What this means more broadly

The same patterns appear in other fields. In physics, classifying problems by type predicts how to solve them. In computing, sorting build steps by dependency gives the best order. In biology, some species support whole ecosystems — remove them and many others fail. Here, fixing the right early gaps helps many later ones. In society, shared upkeep suffers because no single person gains enough from doing it. This project treats cross-checking as its own task, solving that problem.

What this work does not show

The claim that early phases fix most blockers with less than one fourth of total effort is an educated guess, not a tested fact. The author says this openly. The plan might fail if new gaps appear that fit none of the five types, if hidden loops exist in dependencies, or if early work unblocks fewer gaps than expected. About forty old draft projects were excluded and might hold recoverable work. Backup storage was not fully checked due to technical issues. The plan itself can be tested within four weeks of starting.

Words used here

consistency engine
a tool that automatically checks whether different parts of a system match each other, like a spell-checker for data
dependency
a task that must finish before another task can start, like waiting for paint to dry before hanging a picture
directed acyclic graph
a one-way chain with no loops, like a family tree where no one is their own ancestor
gap
a missing piece or unfinished task in a larger project
knowledge graph
a way to store facts as connected points, like a map showing which ideas link to which
Pareto-optimal
getting the biggest result from the smallest effort, like fixing one leaky pipe that was flooding three rooms
topological sort
putting tasks in order so no task comes before something it needs, like packing a bag with socks on top of shoes

Learn more in plain language

This plain-language version was written by an AI model from the text of the paper and checked against plain-language rules: everyday words, no mathematics, no unexplained names. It leaves details out and can still be wrong; the paper is the source of record. To report a problem, open the paper, select the passage and choose Report.

For specialists: the technical digest, quoted from the paper

In the paper's words

A consilient gap synthesis of the QNFO/QWAV research portfolio cataloging 42 gaps across 5 structural categories (Infrastructure, Content, Physics Validation, Governance, Dissemination) with a phased version roadmap v2.0-v2.4 spanning 8 calendar weeks.

The abstract, verbatim, and its opening sentence is the claim. Every line below is quoted from the text.

Numbers it reports

  1. The top five gaps (12% of the total) block approximately 40% of remaining gaps transitively, validating the hypothesis that the portfolio's maintenance debt is deeper but narrower than a surface-level audit would suggest.

    from Abstract

  2. As of 2026-07-29, the ecosystem comprises: 95 projects tracked in the Knowledge Graph 3,109 KG nodes with 1,502 edges across 39 node labels 917 papers in the D1 living-paper database (662 published, 254 backfilled from KG) 25 OpenItems actively tracked 13 R2 buckets serving as durable storage 12 active projects with ongoing development Prior portfolio-level audits (KIF-22, KIF-23 in systemwide audit 2026-07-25) identified specific classes of drift: registry-extension mandates that fail silently, KG–D1 dual-write desynchronization (257 of 887 papers missing from KG), and backup schedules that lapse without detection.

    from 1.1 The Portfolio at Scale

  3. Sequencing these gaps by blocker-dependency and expected value produces a Pareto-optimal roadmap where the first two phases (Infrastructure + Content Remediation) resolve over 60% of known blockers with less than 25% of total estimated effort, because the dependency graph is predominantly a directed acyclic graph with depth $\leq 3$.

    from 1.2 The Core Claim

  4. This claim would be disconfirmed if (a) gap classification failed to converge to five or fewer categories, (b) the dependency graph contained cycles making linear phase sequencing impossible, or (c) Phase 1–2 execution resolved fewer than 40% of transitively blocked gaps. [speculative] — the 60/25 claim is an informed prior based on portfolio familiarity, not an empirically calibrated baseline.

    from 1.2 The Core Claim

  5. Calibration: The 60%/25% Pareto claim in C1 is an informed prior, not an empirically calibrated baseline.

    from 2.5 Limitations

  6. Sessions Cumulative Impact v2.0 Infrastructure Foundation 5 HIGH + 5 MEDIUM 4 Unblocks ~40% of downstream gaps v2.1 Content Registry Remediation 2 HIGH + 5 MEDIUM 3 All cross-reference gaps closed v2.2 Governance Completion 1 HIGH + 3 MEDIUM 5 QNFO.GOV complete v2.3 Physics Validation Pipeline 1 MEDIUM + 4 LOW 8 All claims triaged v2.4 Dissemination Closeout 2 MEDIUM + 1 LOW 1 All papers disseminated Total: 21 sessions over 8 calendar weeks.

    from 4.1 Sequencing Principle

How it is done

  1. Section 2 describes the methodology — sources queried, cross-reference protocol, classification system.

    from 1.3 Paper Structure

  2. Governance (G): Incomplete policy/procedure — QNFO.GOV tasks, program-level audits, compliance automation.

    from 2.2 Classification System

  3. Priorities: (1) formalize the project lifecycle state machine (DEC-020) — the current DRAFT/ACTIVE/PUBLISHED/ARCHIVED taxonomy is underspecified for edge cases like recovered projects; (2) codify the Core Distribution Stack verification protocol (GitHub→the QNFO archive→R2→D1/KG) as a mandatory publication gate; (3) complete program-level Phase 0 audits for the Kepler Program (5 sub-projects with unknown Phase 0 status).

    from 4.5 v2.2: Governance Completion

What would falsify it

  1. This claim would be disconfirmed if (a) gap classification failed to converge to five or fewer categories, (b) the dependency graph contained cycles making linear phase sequencing impossible, or (c) Phase 1–2 execution resolved fewer than 40% of transitively blocked gaps. [speculative] — the 60/25 claim is an informed prior based on portfolio familiarity, not an empirically calibrated baseline.

    from 1.2 The Core Claim

  2. Classification by universality class (gap category) predicts macroscopic behavior (remediation sequence) independent of microscopic detail.

    from 5.1 Physics: Phase Classification

  3. This claim would be disconfirmed if classification failed to converge.

    from 5.1 Physics: Phase Classification

Where the claim stops

  1. We identify 42 distinct gaps, classify them into exactly five cross-domain structural categories (Infrastructure, Content/Publication, Physics Validation, Governance, Dissemination), map their blocker-dependency graph (which is a DAG with depth $\leq 3$), and produce a Pareto-optimal version roadmap sequencing remediation into five phased releases (v2.0–v2.4) over approximately eight weeks.

    from Abstract

  2. The top five gaps (12% of the total) block approximately 40% of remaining gaps transitively, validating the hypothesis that the portfolio's maintenance debt is deeper but narrower than a surface-level audit would suggest.

    from Abstract

  3. As of 2026-07-29, the ecosystem comprises: 95 projects tracked in the Knowledge Graph 3,109 KG nodes with 1,502 edges across 39 node labels 917 papers in the D1 living-paper database (662 published, 254 backfilled from KG) 25 OpenItems actively tracked 13 R2 buckets serving as durable storage 12 active projects with ongoing development Prior portfolio-level audits (KIF-22, KIF-23 in systemwide audit 2026-07-25) identified specific classes of drift: registry-extension mandates that fail silently, KG–D1 dual-write desynchronization (257 of 887 papers missing from KG), and backup schedules that lapse without detection.

    from 1.1 The Portfolio at Scale

Where to read

  1. Abstract214 words · 1 min
  2. §1. Introduction337 words · 1 min
  3. §2. Methodology366 words · 2 min
  4. §3. Gap Inventory339 words · 1 min
  5. §4. Version Roadmap701 words · 3 min
  6. §5. Cross-Domain Consilience223 words · 1 min
  7. §6. Conclusion and Priority Execution Plan382 words · 2 min

Read from the paper itself: 36 sections, 2,641 words. Nothing in this digest is written by a model; a line that is not a sentence of the paper is not shown. Have a specific question? Ask this paper.

The full text · Ask the whole corpus