The deterministic engine is the core of TriloDocs — in production on live studies today. Every document type below states exactly which architectural layer produces it, its validation status, and what is guaranteed.
TriloDocs reads your source outputs — TFLs, SAP, protocol, synopsis — and drafts the CSR the way an experienced regulatory writer does: rule by rule, signal by signal, with every numerical claim transcribed from source and traced to its exact table. There is no probabilistic inference anywhere in the data path, which means the output is reproducible, auditable, and validatable.
TFLs · SAP · Protocol
Rule-based signal identification. Values transcribed, cross-checked, and traced — never generated.
Narrative readability. Architecturally prevented from producing numerical or safety-critical content.
Every sentence traceable to source. Re-verified by Layer 1 before release to your writers.
Different documents carry different risk profiles, so they use different layers of the platform — and we say which, on the tin. Your AI governance committee should never have to ask.
Comprehensive investigator information for trial sites and ethics submissions, built on the same traced data layer.
Summary of clinical safety, synthesised across the full safety dataset with the same traceability guarantees as the CSR engine.
Summarise sections. Compare runs. Surface related findings across documents.
Summary of clinical efficacy, built on the same deterministic core as the rest of the Module 2.7 set.
Summary of clinical pharmacology studies.
Summary of biopharmaceutic studies, completing the Module 2.7 Clinical Summary set.
2.5.2 Biopharmaceutics · 2.5.3 Pharmacology · 2.5.4 Efficacy · 2.5.5 Safety.
Existing customers get early access to each release and their validation documentation is extended, not repeated.