Compare findings
Agents would examine authorised literature, internal documents, historical experiments and datasets to compare findings and surface contradictions.
The platform
Three pillars outside. Four stages inside.
Trovensa is being designed as one platform for a drug-development program: evidence in context, work with continuity and decisions with a record, across discovery, preclinical development, clinical development and manufacturing planning.
Programs as the working scope·Permission-gated actions·Audit of every change·Agent action records·Approval records·Version history
Three pillars outside
Three pillars outside, four stages inside.
The pillars are how the platform is described. The stages are the lifecycle the records move through. Every product belongs to one pillar and would work from the same records, permissions and evidence.
| Pillar | What it means | Products | Status |
|---|---|---|---|
| CONTEXT | Evidence in context Keep sources, findings, interpretations and open questions connected. | Designed | |
| CONTINUITY | Work with continuity Carry context between approved tools, plans, records and reviews. | Designed | |
| RECORD | Decisions with a record Preserve reviewer decisions and the history of agent actions. | Designed |
01 / Discovery
Turn a question into evidence-supported next steps.
Trovensa is being designed to help researchers investigate questions, identify knowledge gaps and develop evidence-supported research plans.
Intended outcomeA research question with its sources, findings, gaps and proposed hypotheses connected and labelled.
Propose hypotheses
Each proposed hypothesis links back to its supporting and contradicting evidence for scientific review.
RecordsResearch questionsSourcesFindingsHypothesesKnowledge gaps
02 / Preclinical development
Keep the plan, the protocol, the data and the interpretation connected.
During research execution Trovensa would connect with the tools scientists already use rather than replace them: protocols, electronic lab notebooks, approved analytical and design tools, and report drafting.
Intended outcomeA plan whose protocol, experiments, results and interpretation remain linked as work repeats and branches.
Prepare a draft
Agents would prepare protocol and report drafts for a scientist to review, edit and approve.
Carry context
Context would move between activities so a question, its plan, the resulting data and the interpretation stay connected.
RecordsResearch plansProtocolsExperiment recordsDraft reports
03 / Clinical development
Review records against approved procedures, with the source in view.
Trovensa would compare research records with approved standard operating procedures and document requirements, presenting each finding with its source, the requirement and an explanation for review.
Intended outcomeReview findings a quality reviewer can accept, dismiss or resolve, each traceable to a record and a requirement.
Surface potential gaps
Missing metadata, unsupported conclusions, inconsistent entries and potentially undocumented deviations would be surfaced for review, never treated as proof.
Record the decision
Reviewer decisions, versions and agent actions would be kept as a record without silently changing approved scientific records.
RecordsStandard operating proceduresReview checksReview findingsDeviations
04 / Manufacturing planning
See the program as one connected picture.
Across discovery, preclinical and clinical development and manufacturing planning, Trovensa would maintain a connected view of program progress.
Intended outcomeMilestones, dependencies, responsibilities, supporting evidence, outstanding questions and approvals in one place.
Track progress
Teams could track milestones and dependencies while accommodating parallel activities and repeated experiments.
Reduce lost context
The long-term ambition is fewer manual handoffs and less lost context between stages and teams.
RecordsMilestonesDependenciesOpen itemsApproval records
Agents propose, people decide
Agents prepare, compare, propose and flag. An authorised person decides.
Nothing an agent produces would become a scientific record on its own. Every proposed item is intended to wait for a named person with the permission to decide.
- 01
Agents prepare
Agents would compare sources, prepare drafts and check records against approved procedures, inside the permissions of the program.
- 02
Every statement is labelled
Each finding, hypothesis and proposed step carries an assertion kind and an origin, so a reader can tell an observation from a suggestion and a person from an agent.
- 03
A person decides
An authorised scientist, reviewer or program lead accepts, rejects, dismisses or resolves each item. Approval records carry the decision and its rationale.
- 04
The record stays
Agent action records, version history and audit entries are intended to remain readable after the work moves on.
The connected program view
See the program as one connected picture.
Progress is being designed to show milestones, dependencies, open items and approvals by stage, each linked to the evidence behind it. The lanes below are an illustrative sketch of that view.
Illustrative program TRV-101Illustrative
01 Discovery
- Question: candidate pathway
- Finding comparison (agent-generated, labelled)
- Hypothesis: accepted
02 Preclinical development
- Plan A
- Protocol v2 (draft)
- Experiment 14 and repeat
03 Clinical development
- SOP check: sample handling
- Finding: open
- Deviation: none recorded
04 Manufacturing planning
- Milestone: planning question
- Dependency: blocked
- Open item: owner needed
Illustrative example; the view is designed and has not been built.
Illustrative flows
Flows that end in a decision.
Each flow is an illustrative example of how the products would connect. Agent steps are labelled; the last step is always a person deciding.
Investigate a question
- Register the question
- Attach authorised sources
- Compare findings (agent-generated, labelled)
- Accept or reject hypotheses
Run the plan
- Write the plan
- Prepare a protocol draft
- Record experiments and repeats
- Approve the report
Trovensa PlansTrovensa Progress
Illustrative flowReview against an SOP
- Choose the SOP and the record
- Run the check
- Decide each finding
- Track deviations to closure
Connections
The tools scientists already use stay where they are.
Trovensa would connect with the systems a program already runs on rather than replace them. Nothing is connected today; every connection is a design target.
Available today
None available today.
Next
None.
Designed forDesigned
- Electronic lab notebooks over REST
- Literature search services
- Document libraries
- Approved analytical and design tools
- Enterprise identity providers such as Microsoft Entra ID
Read on