01Source APIs and research signal enter without LLM mutation.
System architecture
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.
01Source APIs and research signal enter without LLM mutation.
02Records, chunks, citations, entities, provenance, and lineage.
03Ingestion, synthesis, validation, health, embeddings, and compute lanes.
04Hosted runtime state plus local reproducibility from the same inputs.
05Agents critique citations, confounders, gaps, and weak claims.
06Versioned methods, content hashes, JSON payloads, and decisions.
07Preview routes first. Writes require approval and dry_run=false.
08GPU/Docker compute jobs are ledgered, artifact-backed, and gated.
MCP-compatible service boundary for future agents, tools, and external review systems.
Public proofs become validation packets, then confirmation work — without pretending simulation is proof.
The candidate record captures mechanism, citations, risks, methods, decision history, payload links, and known gaps.
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.
A promising record becomes a bounded question with required inputs, readouts, controls, blockers, and success criteria.
Approval-gated Docker and GPU jobs can produce docking, MD smoke, plots, logs, and reproducible configuration artifacts.
Agents and operators decide whether simulated findings are coherent enough to justify more evidence or lab discussion.
The system prepares assay context, controls, thresholds, materials, and metrics for humans or partners to review.
Wet-lab confirmation, failure, or ambiguity feeds back into the candidate record and decision log.
Deterministic ingestion, LLMs for synthesis and critique only, never for silent data mutation.
Public submissions do not mutate candidate state. Contributions enter intake; writes require operator action.
GPU jobs are approval-first and ledgered. Public contribution does not trigger compute.