The Research Map
Connect questions, claims, evidence, experiments, and results, and distinguish authored reasoning from the derived Knowledge Map.
The Research Map records the reasoning of your project: what you are asking, what you expect, which evidence or experiment bears on it, what happened, and which claims you intend to publish.
It is authored project state. A card means you or Kosmo deliberately recorded something; a planned card is not proof that the work happened.
Research Map and Knowledge Map
Project Map contains two related views:
| View | What it represents |
|---|---|
| Research Map | Questions, hypotheses, evidence, experiments, results, claims, and reviewed dependencies you maintain |
| Knowledge Map | A derived Knowledge Graph extracted from files, papers, authors, citations, tables, and notebook cells |
The Knowledge Map is rebuildable discovery. It helps you find relationships in project content, but an extracted or inferred connection remains a lead until you review it. The Research Map is where confirmed reasoning and research status live.
Cards and states
Cards represent units such as a research question, hypothesis, dataset, method, experiment, run, metric, figure, claim, or citation. Each kind asks for the fields needed to interpret it. A hypothesis can record how it would be tested; a run can record a value, unit, seed, and revision.
Cards also carry status. Planned, active, completed, stale, and abandoned work remain distinguishable so a future agent does not treat an intention as a result or repeat work that already failed.
Use containers to group a phase of work. Double-click a container to enter it, and return to the parent view when you need the wider argument.
Directed evidence
Links state how one card supports, tests, derives, contradicts, or depends on another. Direction matters because changed evidence can make downstream claims stale.
When an experiment is rerun or a source changes, inspect the affected claims and figures. Confirm that the relationship still holds or update the downstream card. Staleness is a request for review, not an automatic conclusion that the claim is false.
Working with Kosmo
Kosmo receives a compact relevant briefing and can query the Research Map or Knowledge Map when a task needs more. It can propose cards and connections, focus a relevant node, and relate agent work to project state.
Mutations remain reviewable. Creating a claim, recording a citation, linking evidence, or marking work complete requires the normal permission and role checks. Suggested content stays identifiable as a proposal until you accept it.
Related
Research history and iterations
Research History separates captured work from a researcher's confirmed interpretation. File changes can supply evidence, but they do not automatically prove a result or become a confirmed research iteration.
Choose Record iteration to review a set of your sealed changes with Kosmo. Discuss what the work means and which Research Map cards it belongs to, then explicitly confirm the iteration. The record preserves its evidence and contributors; a collaborative iteration keeps every authenticated contributor as a co-author. Live collaboration continues while you review.
You can clear unassigned work from the timeline and immediately undo that action. Clearing removes it from the next review candidate set while retaining the underlying evidence.