System architecture

The engine, end to end.

TWOG moves from inspectable proof records to durable validation packets, approval-gated compute, and lab-ready confirmation plans. Simulations prioritize hypotheses; lab confirmation decides what survives. Evidence enters through deterministic rails — claims leave as testable records.

The loop — evidence in, testable records out
01
Ingestdeterministic

Source APIs and research signal enter without LLM mutation.

02
Normalizeschema-validated

Records, chunks, citations, entities, provenance, and lineage.

03
MaterializeDagster assets

Ingestion, synthesis, validation, health, embeddings, and compute lanes.

04
StoreNeon + SQLite

Hosted runtime state plus local reproducibility from the same inputs.

05
Arguerecommend-only LLMs

Agents critique citations, confounders, gaps, and weak claims.

06
Publishpublic records

Versioned methods, content hashes, JSON payloads, and decisions.

07
Triageoperator gate

Preview routes first. Writes require approval and dry_run=false.

08
Computeapproval-first

GPU/Docker compute jobs are ledgered, artifact-backed, and gated.

Source rails
PubMedEurope PMCPMC OAOpenAlexCrossrefClinicalTrials.govPubChemChEMBLUniProtRCSB PDBOpenFDA animal eventsresearch social signal

MCP-compatible service boundary for future agents, tools, and external review systems.

Proof → lab: the durable testing framework

Public proofs become validation packets, then confirmation work — without pretending simulation is proof.

Proof recordinspectable substrate

The candidate record captures mechanism, citations, risks, methods, decision history, payload links, and known gaps.

Autonomous cruxfalsification-first loop

TWOG proposes the next test most likely to kill the leading hypothesis, pre-registers a hashed kill-criterion before compute, and resolves its own target/therapy inputs. Confound and provenance gates must pass; nothing is auto-promoted.

Validation packetexplicit test plan

A promising record becomes a bounded question with required inputs, readouts, controls, blockers, and success criteria.

Simulation laneartifact-backed compute

Approval-gated Docker and GPU jobs can produce docking, MD smoke, plots, logs, and reproducible configuration artifacts.

Review gatespecialist critique

Agents and operators decide whether simulated findings are coherent enough to justify more evidence or lab discussion.

Lab handoffconfirmation-ready

The system prepares assay context, controls, thresholds, materials, and metrics for humans or partners to review.

Result updaterecord revision

Wet-lab confirmation, failure, or ambiguity feeds back into the candidate record and decision log.

Three deliberate gates
Evidence boundary

Deterministic ingestion, LLMs for synthesis and critique only, never for silent data mutation.

Public boundary

Public submissions do not mutate candidate state. Contributions enter intake; writes require operator action.

Compute boundary

GPU jobs are approval-first and ledgered. Public contribution does not trigger compute.

Current rails
DagsterNeon PostgresTypeScript / Next.jsPython research bridgeModalDocker workersMCP service boundary