Platform Overview
The documentation model for TrialStack and how customer docs relate to internal repository knowledge.
Read TrialStack as a system
flowchart TD
A["Trial design and study start-up"] --> B["Trial record"]
B --> C["Connected context"]
B --> D["Specialized modules"]
B --> E["Governed review and history"]
E --> F["Structured AI and workflow actions"]
TrialStack is organized around a governed trial record that keeps the study anchor, connected context, specialized work, and reviewable execution in one system.
Follow the operating layers
Most teams experience the product in five layers:
- the core trial record and other governed records that keep study identity and key decisions explicit
- connected context such as organizations, sites, contacts, personas, systems, media, and related evidence
- specialized workflow modules for deeper design, planning, review, and study start-up work
- structured AI and workflow actions through templates, rules, actions, runs, and guided drafting
- governance and administration through history, approvals, restore, usage, and permissions
Use the right docs surface
Use this docs site for workflow guidance and product behavior. Use API reference for exact contracts. Use internal engineering notes only for implementation detail.
Keep the split intentional
The split exists so customer teams, integration owners, and engineers each get the level of detail they actually need without forcing one audience to read the other audience’s documentation model.