Separate implemented controls from roadmap commitments and future integrations.
Trust by design
Feature status
Use one public register to distinguish available capabilities, early-access workflows and planned integrations before relying on them.
Create a free projectWhat this changes
Clear controls and clear boundaries
Keep human accountability visible when AI proposes text, structure or checks.
Make portability, review state and product status understandable before adoption.
A practical working pattern
- 01Understand
- 02Configure
- 03Review
- 04Control
Current public register
Product status
Reviewed 9 August 2026
| Capability | Availability | What the status means |
|---|---|---|
| Research design | Available | Implemented in the current product. |
| Sources and evidence | Available | Implemented in the current product. |
| Methodology and protocol | Available | Implemented in the current product. |
| Data, analysis and findings | Available | Implemented in the current product. |
| Manuscript Studio | Available | Implemented in the current product. |
| Research Copilot | Early access | Usable with visible limitations and active validation. |
| Team collaboration | Available | Implemented in the current product. |
| Readiness and export | Early access | Usable with visible limitations and active validation. |
| Readiness and export | Planned | Roadmap direction, not an available capability. |
Important boundary
Statuses describe product availability, not scientific quality, uptime commitments or entitlement for every account.