Your first DataRoom
Bring a hard problem or a hypothesis that matters. Start with enough real context to ask a better question, then decide what belongs in the room.
A DataRoom is the working context for your problem: its evidence, assumptions, questions, relationships and decisions. The installed plugin keeps project material locally. Your Claude host and any connected tools have their own data policies.
Before you start
Complete installation verification. Have one useful starting document ready: research notes, a problem statement, an experiment result or a short brief. Choose material you are allowed to share with the tools you use.
Open the guided setup
In your project folder, start Claude Code:
claudeThen enter the MindrianOS command inside Claude Code:
/mos:igniteThe setup asks what you are working on. You can arrive with an existing project, a question or a hypothesis. Describe the decision that makes it important.
Example starting point
Review the proposed structure
The setup proposes a blueprint: the sections your DataRoom will start with and where the starting material belongs. Review the problem statement, the assumptions and the proposed scope. Approve, adjust or defer before the room is created.
The section set depends on what you bring. A hypothesis may need supporting evidence, assumptions and possible tests. A venture may need market, solution and financial context. You do not need to fill every section before making progress.
Keep a proposal separate from a finding
Review each proposed claim before accepting it. Check the source and what the source actually supports. A useful hypothesis can remain provisional; accepting a proposal does not make its underlying claim true.
Choose one next move that could change your understanding. It may be a source to inspect, a contradiction to investigate or a test that distinguishes competing explanations.
Recognize a useful first outcome
Before leaving, you should be able to explain what changed: a clearer problem statement, an assumption made visible, a relationship worth examining or a better next test. If the next move is still vague, say what remains unclear and narrow the question.
Check the room and return to it
Use the status command inside Claude Code to review the current room:
/mos:statusKeep the DataRoom location shown during setup. Open its project again for the next session, review what was kept and add the result of your next test. A failed test is useful context too.
Bring the evidence back
Record what happened, which source supports it and which assumption needs revisiting. The room should help you revisit earlier reasoning, including a path you chose not to pursue.