Knowledge Gap Register¶

Register — instantiates Knowledge Map Navigation

A maintained list of the known holes in a body of knowledge — each gap named, evidenced, owned, and scheduled for revisiting so the blank spaces don't stay invisible.

A Knowledge Gap Register is a living log of what a group knows it doesn't know. Each entry names a specific gap, records the evidence for believing it's a gap (and how confident that belief is), assigns an owner responsible for it, and carries a revisit rule — when the gap will be re-examined or the entry retired. Its defining trait is that it is a governed worklist, not a picture: where a landscape map shows gaps in spatial context to reveal opportunity, the register manages them over time so they get closed rather than admired. It exists to keep the map's blank spaces from quietly disappearing — an unrecorded gap is one nobody owns, nobody revisits, and everybody eventually forgets was ever a hole. The register is the mechanism that makes "we don't know this yet" a tracked commitment instead of a fleeting worry.

Example¶

A medical-device company's safety team keeps rediscovering the same unknowns late and painfully. They stand up a Knowledge Gap Register. One entry reads: "No data on device performance in patients under 12." Attached to it: the evidence note ("trials enrolled ages 18+, confidence high that pediatric data is genuinely absent, not just unfound"), an owner (the clinical-affairs lead), and a revisit rule ("re-examine at each trial-design review; retire when a pediatric study is scoped"). Following the discipline of tracking known unknowns explicitly,^[1] the register does something the team's collective memory never did: at the next design review the entry surfaces automatically, the owner reports status, and the gap either advances toward closure or is consciously re-deferred. Nothing about the entry describes where the gap sits in the field — that's not its job. Its job is to make sure this particular hole is owned, evidenced, and revisited until it's filled.

How it works¶

Record each gap as an entry. State the specific missing knowledge concretely enough that "closed" is checkable.
Attach evidence and confidence. Note why it's believed to be a gap and how sure — distinguishing "we've looked and it's genuinely absent" from "we haven't checked."
Assign an owner. Every entry has a named steward accountable for its status; an ownerless gap is one that will rot.
Set a revisit rule. Each entry carries a trigger — a date, a cadence, an event — for when it's re-examined, advanced, or retired, so the register stays current instead of accreting stale entries.

What distinguishes it from its siblings is stewardship over time: the register isn't a snapshot of gaps, it's the governance loop that carries them from noticed to owned to closed.

Tuning parameters¶

Entry threshold — logging every suspected gap gives full coverage but buries the important ones; a high bar keeps the register actionable but lets small gaps slip unrecorded.
Ownership model — a single accountable owner per gap drives closure but concentrates load; shared ownership spreads effort but diffuses accountability.
Revisit cadence — frequent review keeps the register live but costs attention; slow cadence is cheap but lets entries go stale and lose trust.
Confidence rigor — demanding evidence for each "this is genuinely a gap" claim prevents phantom entries but slows logging; loose entry admits guesses that may not be real holes.

When it helps, and when it misleads¶

Its strength is turning fleeting "we don't know that yet" worries into tracked, owned commitments that actually get closed — it is what keeps an organization's known unknowns from silently becoming forgotten unknowns, and it concentrates limited investigation on the gaps that matter.

Its failure modes are the register going stale (entries logged and never revisited, so it becomes a graveyard nobody trusts) and false comfort — the dangerous unknowns are the unknown unknowns, and a tidy register of the ones you've thought of can breed misplaced confidence that you've mapped your ignorance. The classic misuse is using it defensively — logging a gap to document that someone raised it rather than to close it, converting a worklist into a liability shield. The discipline is to keep every entry owned with a live revisit trigger, retire closed and stale entries honestly, and treat the register as a queue to work down, not an archive to point at.

How it implements the components¶

A Knowledge Gap Register fills the archetype's gap-governance slots:

gap_marker — each entry is an explicitly recorded, named gap in the body of knowledge.
confidence_or_evidence_note — every entry carries the evidence for the gap and how confident that judgment is.
map_steward — each gap has a named owner accountable for advancing it.
map_update_rule — the per-entry revisit trigger that keeps the register current and drives entries toward closure or retirement.

It does not display gaps in spatial, contextual relation to the field (gap_marker as located terrain, cross_reference_bridge — that's Research Landscape Map), or test whether people can navigate the map (navigation_validation_loop — that's Map Navigation User Test).

Instantiates: Knowledge Map Navigation — the Knowledge Gap Register is the governed worklist of a domain's known gaps.
Consumes: Research Landscape Map is a common source of candidate gaps — the register takes the frontier the map displays and puts owners and revisit rules on the entries worth closing.
Sibling mechanisms: Research Landscape Map · Map Navigation User Test · Concept Map · Ontology Map · Knowledge Graph · Domain Map · Documentation Navigation Map · Learning Path Guide · Curriculum Map · Prerequisite Tree

Notes¶

The register handles the maintenance and governance side of the archetype — ownership and update discipline — for gaps specifically. Those same stewardship components (owner, revisit rule) apply to keeping any map current; here they are scoped to the worklist of known holes, which is what keeps this mechanism distinct from the spatial Research Landscape Map that merely displays them.

References¶

[1] The "known unknowns" framing — things one is aware of not knowing, as distinct from "unknown unknowns" one isn't even aware of — is a useful way to scope a gap register: it can only ever hold the former, which is precisely why a clean register must not be mistaken for a complete map of one's ignorance. ↩