What ResearchArchitect does, in the order you'll actually do it — from a research question to a set of hypotheses that know their own limits.
An influence network: the variables that bear on your research question, and the links between them. It is not a finished analysis — it is the design you would otherwise carry around implicitly, made explicit enough to argue with.
Six steps. You can stop after any of them, and you can loop back at any point — the graph is saved as you go and every action is recorded.
On the setup card, give your research question. That is the only required field. If you already know your data and your scope — the area, the time window, the resolution — add them now; if not, add them later and re-run.
You get a first network of variables and directed links. Expect it to be too broad and partly wrong — that is the point. It is faster to delete a bad variable than to think of a missing one.
Say what is wrong in your own words — a variable that conflates two things, a link pointing the wrong way, a mechanism nobody in your field would accept. You can also add and delete nodes directly, or ask a question in the chat panel without changing anything.
Every link gets classified by the kind of role it plays — necessary, driving, or modifying — and the graph is redrawn accordingly. See reading the graph below.
Two different questions, often confused. Scope asks whether a variable will even move inside your observation window and act within your study area. Coverage asks whether you can measure it with the data you have. A variable can be perfectly measurable and still useless, because it is constant across everything you sampled.
Check for cycles first — a feedback loop changes which hypotheses are even statable, because a variable inside one cannot be treated as simply upstream of the outcome. Then generate hypotheses, each tied to the variables and links it depends on.
Three encodings, each answering a different question. They are independent — an edge can be necessary and out of scope and uncovered.
A literature review is not a web search with citations attached. Every source a review cites is tagged with the role it plays for your study, and the reference list is ordered by it.
Actions that call out to a model cost credits. Editing, deleting, exporting, and asking a question in the chat panel are free.
| Action | What it produces | Credits |
|---|---|---|
| Generate causal graph | Turn a research question into a structured causal DAG. | 5 |
| Refine graph | Iteratively improve nodes and edges based on your feedback. | 3 |
| Data coverage | Find which variables have data and which need collection. | 4 |
| Edge importance | Score each causal relationship by strength and evidence. | 4 |
| Scope assessment | Evaluate the boundaries and assumptions of your model. | 4 |
| Generate hypotheses | Discover testable hypotheses from the graph + literature. | 8 |
| Detect feedback loops | Identify system dynamics and reinforcing cycles. | 5 |
| Literature review | Edge-by-edge literature evidence with citations. | 6 |
The things people ask in the first session.
These open in the workspace with everything already run, so you can see the finished shape before building your own.