Step 1
Daily Notes and connected blocks vs a current decision record
Roam Daily Notes make chronological capture fast, while pages and nested blocks can connect a company to industries, sources, catalysts, and prior dec...
Keyword: roam research investment notes
KeepRule vs Roam Research: Investment Notes Comparison
Compare KeepRule and Roam Research for daily notes, block references, backlinks, graph research, exports, privacy, and thesis reviews.
Roam Research can be a strong investment research graph database when Daily Notes, pages, block references, and backlinks help you connect companies, filings, industries, and prior judgments. Networked notes still may not reveal which thesis is current: a referenced block can appear in several contexts, graph density can reward confirmation, and a useful query can surface evidence without testing it. Compare both workflows with six checks: thesis owner, source date, downside boundary, invalidation trigger, action rationale, and next review date. Keep Roam when a required decision page makes those fields easy to audit; add KeepRule when discovery is strong but decision accountability becomes inconsistent.
30-second action
Turn this page into one decision step
Pick the smallest next action now: test your bias pattern, run a scenario, or copy a prompt before making a portfolio move.
Quick Take
- Daily Notes and connected blocks vs a current decision record
- Block references and backlinks need source discipline
- Graph navigation, queries, and extensions do not validate a thesis
Visual Playbook
Step 2
Block references and backlinks need source discipline
Block references and linked references can reduce duplication and reveal every context in which a claim appears. They can also blur provenance when a...
Step 3
Graph navigation, queries, and extensions do not validate a thesis
Graph navigation and queries can expose relationships, unresolved tasks, or all mentions of a company, while Apps, API connections, and extensions can...
Tool Comparison Breakdown
1) Daily Notes and connected blocks vs a current decision record
Roam Daily Notes make chronological capture fast, while pages and nested blocks can connect a company to industries, sources, catalysts, and prior decisions. That network answers where an idea appeared, not whether it is ready for action. Require one clearly marked current thesis with an owner, dated evidence, downside boundary, invalidation conditions, action rationale, and next review. KeepRule supplies that judgment structure by default; Roam requires a convention you maintain.
2) Block references and backlinks need source discipline
Block references and linked references can reduce duplication and reveal every context in which a claim appears. They can also blur provenance when a block is edited later or reused under a different argument. Keep the original URL or document owner, publication and access dates, the claim supported or contradicted, and a stable decision identifier. Preserve a dated snapshot of decision-critical evidence so a later block edit cannot silently rewrite the rationale for an earlier action.
3) Graph navigation, queries, and extensions do not validate a thesis
Graph navigation and queries can expose relationships, unresolved tasks, or all mentions of a company, while Apps, API connections, and extensions can automate capture or review queues. A dense cluster, successful query, or automated status is not proof. Use these tools to surface sources and deadlines, then require a person to verify current filings, seek disconfirming evidence, and reassess thesis, risk budget, and invalidation conditions before any portfolio action.
4) Public and private graphs, collaborators, exports, and recovery
Roam offers private or public graphs, collaborators, API access, and Apps, so the data boundary depends on graph settings and every connected service. Review who can open or edit the graph, what integrations can read or write, and which pages contain unpublished judgments or personal constraints. Export a representative graph and test whether dates, block identifiers, references, attachments, and current-thesis markers survive recovery. Never store brokerage passwords or API secrets in either product.
5) Run a two-to-four-week hybrid trial before migrating
Keep Roam as the networked research graph, then run one active holding and one watchlist idea through KeepRule for two to four weeks. Compare time to retrieve the current thesis, dated source evidence, contrary evidence, invalidation triggers, action rationale, and completed reviews. Preserve the original graph and a tested export throughout the trial. Migrate only the judgment layer if Roam remains better for associative research while KeepRule makes decisions easier to audit under pressure.
Template Snapshot
Decision fields to lock before execution
- Thesis in one sentence
- Invalidation trigger and evidence threshold
- Risk budget and position-size boundary
- Review date and expected catalyst window
Action Checklist (Shareable)
- Daily Notes and connected blocks vs a current decision record.
- Block references and backlinks need source discipline.
- Graph navigation, queries, and extensions do not validate a thesis.
- Write one invalidation trigger and one review date before you act (use: Browse Principle Library).
- Double-check the common pitfall: Is Roam Research suitable for investment research notes.
- Do one follow-up in 10 minutes: Use prompts for pre-trade and post-trade review.
Share Kit
Why KeepRule
- Structured decision system across Scenarios, Principles, Masters, and Prompts.
- Built for repeatable execution, not one-off opinions.
- Designed for long-term investors who want fewer emotional mistakes.
Recommended KeepRule Paths
FAQ
Is Roam Research suitable for investment research notes?
Yes. Roam is useful when Daily Notes, pages, blocks, and backlinks help connect filings, companies, industries, catalysts, and earlier judgments. The boundary is decision consistency: a rich graph can still hide the current thesis, downside limit, invalidation evidence, or next review. Use one required decision-page template and audit recent ideas before treating the network as a complete investment process.
Can block references and backlinks replace an investment thesis record?
Not by themselves. They make claims reusable and their contexts discoverable, while a thesis record must identify the current claim, dated sources, assumptions, downside boundary, contrary evidence, invalidation conditions, action rationale, and review date. Mark one canonical decision record, link referenced blocks to it, and preserve dated evidence so later edits do not change the historical rationale.
How should investors use Roam queries, the API, and extensions safely?
Use them to collect sources, flag missing fields, or schedule a human review, with a named owner for stale inputs and failures. Document what each connection can read or write and test the result against the source. A query or automation should never independently buy, sell, or resize a position; it should lead to verification of the thesis, contrary evidence, and risk budget.
What privacy and export checks matter for a Roam investment graph?
Confirm whether the graph is private or public, review collaborators and integrations, separate reusable research from personal constraints, and minimize sensitive data. Export a representative set of Daily Notes, pages, blocks, references, and attachments, then restore or inspect it before calling it a backup. Do not place brokerage credentials, API secrets, or restricted nonpublic information in the graph.
When should I use Roam Research and KeepRule together?
A hybrid setup fits when Roam remains the associative source and research graph while KeepRule owns pre-action checks, invalidation triggers, and post-decision review. Link both with one stable company or decision identifier and define which system owns the current thesis. Avoid duplicating every block in both systems, because parallel copies become stale and make the active rationale harder to identify.
Audit one Roam investment decision before migrating
Check its canonical thesis, source dates, block provenance, downside boundary, invalidation evidence, graph access, export path, and next review, then compare it in KeepRule.