Inquiry Log¶
Artifact — instantiates Curiosity Gap Design
Records questions, provisional answers, surprises, sources, and next probes so the inquiry loop remains visible and cumulative.
A curiosity gap that opens attention and then forgets what it found has collapsed back into a hook. Inquiry Log is the living document that keeps an investigation from resetting itself: a running record of open questions, provisional answers, surprises, sources, and — always — the next probe. Its defining move is keeping the inquiry loop visible and cumulative across time and people, so a months-long or multi-hand investigation compounds instead of starting fresh each session. It differs from a Discovery Task, which pools evidence within a single activity — the log persists across sessions, and its unit is the question-and-its-status, not one dataset. It is more than a filing cabinet for findings: every entry closes with a next question or an explicit resolved, so the record drives inquiry forward rather than archiving it. That closing move is what turns a curiosity hook into a transferable, compounding line of inquiry.
Example¶
A reporter is chasing a months-long story about why a city's water bills suddenly spiked. She keeps an inquiry log — one running document. Each entry is anchored to an open question ("who approved the rate change, and when?"), the provisional answer so far (dated, because answers move), the source (a document or an interview, flagged for how reliable it is), any surprise ("the utility's own board minutes contradict its press release"), and the next probe ("file a records request for the meeting agenda; call the two dissenting board members"). Weeks later a lead she'd written off reopens — because the log preserved a contradiction she would otherwise have forgotten. When a colleague joins the story, they read the log and are current in an hour instead of re-interviewing everyone from scratch. The discipline that makes it work: no entry is closed without a next question or an explicit resolved, so the document always points at the live edge of the investigation rather than piling up inert notes.
How it works¶
- Record the question, not just the answer. Each entry is anchored to an open question and its current status, so the log maps what is still unknown, not only what has been settled.
- Timestamp and source everything. Provisional answers carry their date and source with a reliability flag, so later contradictions become visible and every finding stays auditable.
- Give surprises and contradictions a home. The anomalies that don't fit are the most valuable and the easiest to lose; the log captures them explicitly instead of letting them evaporate.
- Always end in a next probe. Every entry closes with the next question or action, so the record propels the loop rather than becoming a graveyard of notes no one revisits.
Tuning parameters¶
- Capture granularity — every micro-finding versus only decision-relevant ones. Finer is more complete but raises upkeep cost and buries the signal.
- Structure — free-form log versus strict fields (question / status / source / next). Structure aids review and handoff; too much of it discourages people from writing anything down.
- Review cadence — how often the log is re-read to regenerate questions. Frequent review keeps the loop alive; rare review lets it ossify into a dead archive.
- Sharing scope — private notebook versus team-visible. A shared log turns individual impressions into common knowledge but raises the bar for what people are willing to record.
- Provisionality marking — how clearly unconfirmed findings are flagged. Clear flags stop a guess from hardening into a "fact"; over-flagging clutters the record.
When it helps, and when it misleads¶
Its strength is making inquiry cumulative and shareable: the investigation is offloaded into an external artifact that remembers what individuals forget and lets a team think as one — the distributed cognition view, in which the record is part of the cognitive system, not merely its output.[n1] It is the exact component that converts a one-off curiosity hook into a transferable, compounding line of inquiry.
Its failure mode is the write-only log — dutifully filled, never re-read, so it archives instead of driving, and recording quietly becomes a substitute for thinking. The classic misuse is the compliance log kept only because a process demands it: no next-probe field, no review, accreting into documentation debt nobody consults. A subtler failure is the log that records answers but not the open questions, so it flatters progress while hiding how much is still unknown. The guarding discipline: every entry ends in a next question, and the log is re-read on a cadence to regenerate probes — a log that never changes anyone's next action has stopped being an inquiry loop.
How it implements the components¶
answer_capture— records provisional findings, sources, surprises, and contradictions in a durable, reviewable form rather than leaving them as individual impressions.inquiry_loop— closes each entry with a next question or probe, turning captured findings into the next cycle; this is the cumulative loop no sibling mechanism maintains.progress_signal— the accumulating record makes movement through uncertainty visible: questions resolved, hypotheses eliminated, contradictions surfaced, even before a final answer exists.
It does not open the gap or bind it to a stake — that is Provocative Question Prompt — nor does it bound and route the exploration, which is Guided Exploration Path's job.
Related¶
- Instantiates: Curiosity Gap Design — the log is the loop-keeping artifact that makes an inquiry cumulative instead of one-shot.
- Consumes: Discovery Task and Exploratory Prototype — their probe results and surprises are the raw findings the log records and carries forward.
- Sibling mechanisms: Provocative Question Prompt · Mystery Frame · Guided Exploration Path · Research Question Workshop · Discovery Task · Exploratory Prototype · Curiosity-Driven Onboarding Path
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Inquiry Log operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it records questions, provisional answers, surprises, sources, and next probes so the inquiry loop remains visible and cumulative
Independent corroboration: The frozen evidence defines Inquiry Log as 'Records questions, provisional answers, surprises, sources, and next probes so the inquiry loop remains visible and cumulative', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Education & Pedagogy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Recording questions, provisional answers, surprises, and next probes descends from inquiry-learning journals and reflective educational practice.
Related originating lineages:
- Cognitive Science — Distributed-cognition theory materially frames the log as part of a group's reasoning system.
- Library & Information Science — Source organization and retrieval materially shape cumulative evidence tracking and later handoff.
Review resolution: Both independent reviews place the primary lineage in education_pedagogy. The queued differences (origin_mode_disagreement, encyclopedia_synthesis_disagreement) concern secondary metadata rather than primary provenance. The final retains cognitive_science, library_information_science only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=cross_disciplinary_synthesis because the entry's present form deliberately composes methods from the documented lineages. domain_reach=multi_domain records application breadth separately from provenance.
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 inquiry log is the component that turns the whole archetype from a hook into a transferable solution. Without it, each inquiry's learning dies with the session and the next investigator starts cold — which is why "loops forward" is one of the archetype's invariants, and why a log that is never re-read has failed even if it is faithfully kept.
[n1] Distributed cognition (Edwin Hutchins, Cognition in the Wild) treats external artifacts — logs, charts, records — as genuine parts of a cognitive system rather than passive storage, which is why a well-kept inquiry log lets a group remember, reason, and hand off as a single mind. ↩