Accountability
Trovensa is being designed so that every consequential action has a scope, a permission, an actor and a record.
Programs as the working scope·Permission-gated actions·Audit of every change·Agent action records·Approval records·Version history
What the records are for
The records it would keep are evidence your quality process consumes. They do not certify a record, validate a therapy or stand in for a reviewer; an authorised person reviews and decides.
Findings, audit entries and approval records are inputs to your own procedures. They make no statement about a record being certified or a therapy being validated; those judgements stay with the people and processes responsible for them.
The capabilities
A program is the scoped workspace of one development effort. Every record is intended to carry its organisation, program and stage, so scope is a property of the data rather than a filter.
organization · program · stage on every record
Actions are being designed to check a named permission before they run, with roles assigned at organisation or program scope. Agents would act only inside the permissions of the program that invoked them.
permission string · scope · role assignment
Creates, updates, approvals and deletions would be written to an audit trail with the actor, the time and the record concerned.
actor · action · record · time
Each agent run is intended to keep what it read, what it produced and where the output went, marked agent-generated and waiting for a person.
inputs read · outputs proposed · reviewer decision
Plans, protocols, reports, hypotheses and milestones would carry approval requests with the decision, the deciding person and the rationale. "Approved" is a record, never a default.
request · decision · decided by · rationale
Protocols, reports and procedures are being designed as versioned records, so a review always names the version it examined.
version · changed by · previous version
Agents propose, people decide
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.
Agents would compare sources, prepare drafts and check records against approved procedures, inside the permissions of the program.
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.
An authorised scientist, reviewer or program lead accepts, rejects, dismisses or resolves each item. Approval records carry the decision and its rationale.
Agent action records, version history and audit entries are intended to remain readable after the work moves on.
Record shapes
The record types below are the ones a quality process would ask for first. Each is shown as its intended fields; the values would come from your program.
Illustrative record shapes; the platform is designed and has not been built or validated.
Connections
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.
None available today.
None.
Read on