Where did it come from?
Open the database, identifier, URL and retrieval trail.
Ask where a claim came from, what ran, what failed and what left your environment. Perslis keeps those answers with the research record—not buried in a promise.
Open the database, identifier, URL and retrieval trail.
Inspect inputs, outputs, parameters and job state.
See refusals, missing evidence and unresolved paths.
Choose local records and optional external models, or a hosted floor.
Drag to pan. Zoom in. Select a node to see what it does. Keyboard: Tab between nodes, Enter to inspect; arrow keys pan when the diagram is focused.
Keep execution bounded and access scoped to the work. The Airtight chapter explains the local posture, while hosted account details are covered in the account privacy notice.
Explore SecurityLocal deployments keep their research record on your machine. Hosted accounts store account and floor data for the web service; read the privacy notice for what is collected and retained.
Explore PrivacyKeep source identity attached to every accepted record. A citation makes a claim traceable, but the source itself can still be mistaken or incomplete.
Explore ProvenanceInspect released artifacts, recorded evaluations and the scope of each result. Public prototype evidence and proposed bioscience applications are clearly distinguished.
Explore VerificationExplore locally held records and opt-in external models, or use the hosted research floor. Offline operation covers retained records; new online database queries require network access.
Explore Deployment optionsA recorded demonstration of the local research experience.
Recorded on a research prototype. The recording shows the scope demonstrated at that time.
Explore the research floor yourself →Start with a target, a dataset or a research question. Inspect what the evidence supports, what it rejects and what remains unknown.