Trovensa documentation
From evidence to progress. Trovensa is being designed to connect scientific evidence, research workflows, and the decisions that advance drug-development programs. Inside one program, four products are intended to hold the work: Evidence (questions, sources, findings, hypotheses), Plans (plans, protocols, experiments, reports), Review (SOP checks, findings, deviations) and Progress (milestones, dependencies, approvals). Agents prepare, compare, propose and flag; an authorised person reviews and decides, and the record shows who did what. This site describes how the platform is designed to behave, how it is built and what the first release needs.
Status of every product
The four hosts answer since the first release on 2026-09-13, but nothing is available to customers yet: sign-in is not configured, and every product carries the status word designed: the screens, routes and
records express intended workflows against the API contract, and every seeded record is labelled
“Illustrative”.
| Product | Role | Pillar | Status |
|---|---|---|---|
| Evidence | Questions, sources, findings, hypotheses | CONTEXT | designed |
| Plans | Plans, protocols, experiments, reports | CONTINUITY | designed |
| Review | SOP checks, findings, deviations | RECORD | designed |
| Progress | Milestones, dependencies, approvals | CONTINUITY | designed |
The full table with icons, entry routes and stages is the products reference; the reasoning behind pillars and stages is in About pillars and stages.
What the kit says Trovensa is for
The brand line is “Evidence -> Plans -> Review -> Progress”. In the kit’s words, the three core messages are Evidence in context (findings that keep their sources), Work with continuity (plans, protocols, experiments and milestones that stay connected across a program) and Decisions with a record (review findings and approvals that a person decides, with a rationale that stays attached). Agent output is always “agent-generated” or “proposed”; a success colour never certifies a scientific conclusion.
How the documentation is organised
Every page has one job. Knowing the four types tells you where to look.
Learning by doing. One path with no options, for example Get started, which runs the platform locally with the illustrative program.
Steps for one task, titled “How to …”, each naming the permission a step needs and the path through the rail and the panel.
Neutral description of the machinery: products, permissions, personas, statuses, API routes, tokens. Tables that mirror the code and end with a Source line.
Background and reasoning, titled “About …”, for when you want to understand why it is designed this way.
Start here
- New to the platform: Get started.
- Working in a program: How to connect a source, How to run an evidence comparison, How to review a record against an SOP, How to request an approval, How to switch programs.
- Looking things up: Permissions, Personas, Statuses, API.
- Joining the team: Contract summary, Decision log, Roadmap.
Where things are designed to live
Hosts are design targets recorded in the contract; nothing answers on them yet (ADR 0010).
| Surface | Host | Local |
|---|---|---|
| Marketing site | trovensa.com | static server on 4300 |
| This site | docs.trovensa.com | static server on 4310 |
| Web app | console.trovensa.com | http://localhost:3100 |
| API | api.trovensa.com | http://localhost:8100 |