Refract workflow overview
A visual summary of how Refract connects document work, saved evidence, and statistical analysis inside the same research session.
A compact explanation of the operating model
This diagram is useful because it shows the project before implementation detail takes over. The session is the coordinating object; literature work and statistical work branch outward from it and reconnect through interpretation.
The image already appears at the top of the record. The purpose of the text below is to explain how to read it, not to restage it at full size.
The workflow can be read in two directions
Both readings matter because they show different aspects of the same design.
From top to bottom, the diagram explains how the session acts as the frame that keeps the work coherent. The research goal, the papers, the saved evidence, and the later analysis all remain parts of the same ongoing object.
From left to right, the diagram distinguishes literature work from quantitative analysis while still showing where they reconnect. That distinction is important because the point of the system is not to collapse those activities into one surface. It is to keep them separate enough to be usable while still preserving the shared context that makes later interpretation possible.
This is the fastest route into the project
The artifact matters because it exposes the architectural intention without requiring a full code-level reading first.
A diagram like this is useful because it clarifies the logic of the system before implementation details take over. It explains where reading happens, where analysis happens, and why both need to remain within the same research frame. For someone trying to understand the project quickly, this artifact is one of the fastest ways to see what the application is designed to hold together.