Platform documentation

This area is written for scientists, quality reviewers, program leads and operators. The console, Evidence, Plans and Review carry the status word preview (a private preview for design partners, discovery and preclinical scope, since 2026-09-15); Progress, the persona twins of R3 and the clinical and manufacturing objects are designed, and the roadmap names the gates each must pass. Everything runs locally with a development identity, fake connector servers and an illustrative program. The pilot is positioned as “non-GxP decision support with a light validation package”: the ELN stays the scientific record, the QMS stays the SOP record, Trovensa is the record of what agents proposed and what people decided.

• Learn: Get started runs the database, the API and the web app on your machine and opens the illustrative program trv-101; Ask the agent opens the console, approves a plan and accepts two proposed findings.
• Do: the how-to guides cover one task each, from connecting a source, an ELN or a QMS to launching from your notebook, accepting a requirement set, approving with a signature and exporting the audit trail; the R3 guides cover enabling your twin, deciding from your inbox, sending a hand-off, delegating while away and reading the program board; the phase-4 guides (designed) cover choosing your workbench role, pinning evidence to your board, showing the source behind a claim and reading what your twin remembers. Each step names the permission it needs.
• Look up: Products, Permissions (87), Personas (version 3), Twins, Workbench roles (15, designed), Harnesses, Skills, Memory, the Evidence panel, Statuses (tone map 61), the API (189 routes; 206 as the R4 target), the Console, Connectors, Licence codes, Signatures, Agent versions, Assertion kinds and Brand and theme.
• Understand: About pillars and stages, About programs, About evidence and assertions, About agent actions and records, About the console, About personas and twins, About stage playbooks, About records and signatures, About SOP binding and About licences.

Navigation vocabulary used throughout: the rail on the left lists Home, the four products, Console, Setup and Organization; the panel next to it lists the sections of the selected area. UI paths are written with ›, for example Evidence › Questions. Agent output is always “agent-generated” or “proposed”; seeded and fake-server data is labelled “Illustrative”.