Unknowns and Assumptions Register¶
Assumption register — instantiates Problem Space Mapping
Keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.
An Unknowns and Assumptions Register is the cross-cutting ledger that keeps a problem-space map honest about what it does not know. Rather than representing states, options, or paths, it tracks the epistemic status of everything else on the map: which "facts" are actually unverified assumptions, which regions rest on missing evidence, and how load-bearing each unknown is — so that when a map is drawn confidently, the register records where that confidence is borrowed. Its defining commitment is separating what is known from what is assumed or unknown, and keeping that separation live: each entry carries how it would be tested and gets retired only when evidence arrives. This is what makes it a distinct mechanism rather than an annotation — it is the running instrument against false completeness, the failure where a neat diagram is trusted because nothing on it is visibly marked "we are guessing here."
Example¶
A two-person startup is mapping the business behind a meal-prep app, and the plan looks convincing on the wall — until they start a register. Every load-bearing claim gets an entry with its status. "Customers will pay $12 a week" — assumption, untested, high leverage. "We can acquire a customer for under $8" — assumption, no data, the whole model rests on it. "Grocery partners will grant wholesale pricing" — unknown, one informal conversation, medium leverage. Each row carries the cheap test that would resolve it and a flag for how much of the plan collapses if it turns out false.
The register changes what the founders do next. The pretty projection had drawn all three claims as if they were settled numbers; the register re-marks them as the evidence gaps they are and sorts them by leverage. The customer-acquisition-cost row rises to the top — not because it is most likely wrong, but because it is the most load-bearing unknown, the assumption the entire map silently depends on. The next sprint becomes a landing-page test aimed squarely at it. As results land, the validation loop retires resolved rows and re-flags any downstream claim the new evidence unsettles. Nothing was drawn as fact that had not earned it.
How it works¶
- Scan the map for load-bearing claims. Walk every state, constraint, and path and ask of each: is this known, assumed, or unknown? The register exists to force that question.
- Log each unknown with its status. Record whether it is an untested assumption, a partial-evidence belief, or a genuine blank, plus the source (if any) behind it.
- Tag leverage. Mark how much of the map depends on each entry, so the list sorts by what would hurt most if wrong, not by what is merely uncertain.
- Attach a resolving test. Note the cheapest evidence that would move each entry from assumed to known, or refute it.
- Retire and re-flag on evidence. As results arrive, close resolved entries and re-open any downstream claim the new evidence destabilizes — the loop that keeps the register current.
Tuning parameters¶
- Logging threshold — how significant an unknown must be to earn a row. A low threshold catches everything but buries the vital few; a high one stays focused but can miss a quiet fatal assumption.
- Leverage weighting — how aggressively entries are ranked by consequence-if-wrong versus mere uncertainty. Strong weighting points effort at what matters; weak weighting treats all unknowns alike.
- Evidence bar — how much proof retires an entry. A high bar avoids premature confidence but keeps rows open long; a low bar clears the list faster but risks re-freezing a guess as fact.
- Review cadence — how often the register is walked against the current map. Frequent review keeps it live; infrequent lets it drift into decoration.
- Assumption-vs-constraint strictness — how hard you interrogate whether a stated "constraint" is really an unverified assumption; strict interrogation reopens more of the space but costs meetings.
When it helps, and when it misleads¶
Its strength is being the one instrument aimed squarely at false completeness: it makes the map's borrowed confidence visible and, by ranking unknowns by leverage, points scarce testing at the assumption the whole structure rests on — the leap-of-faith assumption that, if wrong, sinks everything downstream.[n1] It is also the natural companion to every other map here, because any of them can be drawn too confidently.
Its failure mode is becoming a graveyard: a register that grows without pruning, where hundreds of trivial unknowns bury the few that matter and the leverage tags go unmaintained, so it decays into a checklist no one reads. A subtler misuse is logging unknowns to look rigorous while never attaching resolving tests — cataloguing doubt instead of retiring it. The guarding discipline is ruthless leverage-ranking and an insistence that every open entry names the evidence that would close it. Note the register records what is unproven; it does not itself hold the constraints, moves, or options — it only marks which of those are standing on assumption.
How it implements the components¶
evidence_gap_marker— its core artifact: the explicit, ranked ledger of unverified assumptions and missing evidence, tagged by how load-bearing each is.map_validation_loop— the retire-and-re-flag cycle that closes entries as evidence arrives and re-opens any claim the new evidence unsettles, keeping the surrounding map a working model rather than a frozen one.
It does not hold the moves or their transition structure (action_set, state_transition_map) — those are the State / Action Map's — nor the feasibility structure itself (constraint_set), which the Constraint Matrix owns; the register only marks which of those rest on assumption.
Related¶
- Instantiates: Problem Space Mapping — supplies the epistemic-honesty layer that keeps a map from presenting guesses as settled structure.
- Sibling mechanisms: State / Action Map · Constraint Matrix · Design Space Map · Search Space Diagram · Diagnostic Possibility Map · Strategic Option Map · Option Map
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Unknowns and Assumptions Register operates as a persistent ledger, log, register, or case record that preserves history and traceability because it keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.
Independent corroboration: The frozen evidence defines Unknowns and Assumptions Register as 'Keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Both independent reviews identify organizational management as the historical home of the operation—Keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.. The retained alternates document formative adjacent traditions; the reach field, not the origin field, carries later applicability.
Related originating lineages:
- Futurism & Strategic Foresight — Strategic foresight, scenario planning, and anticipatory governance supplies a parallel or contributing lineage for the mechanism's defining operation: keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.
- Statistics & Experimental Design — Statistics, experimental design, and measurement theory supplies a parallel or contributing lineage for the mechanism's defining operation: keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.
- Systems Thinking & Cybernetics — Systems science's feedback, boundaries, control, and regulation tradition contributes a separate formative lineage to the mechanism's unknowns and assumptions register logic.
Review resolution: Both blind reviewers independently place the defining operation—Keeps a running ledger of the map's unverified assumptions and evidence gaps, tagged by how load-bearing each is, so guesses are never drawn as if they were settled structure.—in organizational management. Their queued differences are secondary: alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement. Reviewer A uniquely contributes no additional alternate; reviewer B uniquely contributes ['futurism_foresight', 'statistics_experimental_design']. I preserve the full evidence-supported union of 3 alternate domain(s), without a numeric cap. origin_mode=single_lineage reflects the more specific lineage judgment in reviewer B's evidence, while domain_reach=universal separately records present-day portability. The affirmative encyclopedia-synthesis finding is preserved, and confidence=high uses the more conservative reviewer level.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The register pairs naturally with any sibling map as an overlay: a Design Space Map whose feasibility shading rests on an untested manufacturing assumption, or a Strategic Option Map whose paths assume a competitor stays put, each become far more trustworthy when their load-bearing guesses are logged here rather than absorbed silently into the drawing.
[n1] A leap-of-faith assumption (a term from lean-startup practice) is a belief a plan depends on most heavily yet has the least evidence for. Ranking unknowns by leverage is precisely the move that surfaces such an assumption early, so the cheapest possible test can be aimed at it before the rest of the map is built on top. ↩