Pasted text, TXT and Markdown
Use UTF-8 text for specifications, test notes and source excerpts. Formatting is treated as text, not executable content.
Getting started
From a product brief to a claim you can review.
Start with one capability, its supporting evidence and the people responsible for checking it. Studio gives your team a shared place to ask questions and develop a precise draft.
Open Studio- 01
Set up your workspace
Create a company workspace with a verified work email. Personal email providers are not accepted for signup. Your owner invites authors, reviewers and viewers. A new workspace starts with advisory models for evidence analysis, adversarial review, brand review and drafting. The owner can change them in Settings → Models. A solo founder needs another qualified person to approve their own claim.
- 02
Describe the product
In Studio, enter the product, release version, audience and a short description. This brief supplies context. It does not become verified evidence merely because it appears in a conversation.
- 03
Register supporting evidence
Paste text or upload a supported document in Evidence. Inspect the extracted text, correct reading-order errors, give it a title and set an expiry where appropriate. Save it as an evidence version before selecting it in Studio.
- 04
Work through the claim in chat
Create a conversation and select up to five current evidence sources for each message. Ask what the evidence supports, which conditions matter and what is missing. Replies and exact supporting excerpts stay in the workspace. Colleagues with workspace access can read the conversation.
- 05
Save a draft, then obtain approval
A proposed claim includes the product version, conditions, limitations and evidence references. Saving creates an ordinary draft. Submit it for independent review; high-risk claims need two independent reviewers. AI cannot approve or publish.
- 06
Publish and keep the evidence current
An owner publishes the approved current version to a hosted claim page or a configured CMS connector. Revised, revoked or expired evidence invalidates dependent approvals. External delivery and withdrawal follow the connector queue.
Accepted inputs
Know what the system reads.
Text-based PDF
Up to 50 pages. Text is extracted with page markers; images and scanned pages are not interpreted. Check tables and reading order against the original.
DOCX
Main-body text, including text in tables. Headers, footers, images, comments and deleted tracked changes are omitted. Macro-enabled and encrypted archives are rejected.
CSV
Retained as literal text. Formulas are not executed, and spreadsheet calculations are not imported. Export the relevant values and include units and column definitions.
Limits and provenance
One file up to 4 MB and 50,000 extracted characters. Evidence retains the saved text, original-file fingerprint and extraction metadata. Original files are not retained. Unsaved previews expire after 24 hours and are cleared by scheduled maintenance.
Other media
Scanned PDFs, images, audio, video, XLSX, PPTX and automatic website crawling are not supported by this intake. Export readable text and review it before upload. Source URLs are references; they are not fetched.
Working boundaries
A useful assistant, with an accountable reviewer.
Chat requests include your product and brand context, recent conversation history and the evidence versions selected for that turn. Selected evidence is limited to 60,000 characters across five sources. Conversations support up to 30 turns; start another when you need to continue.
Exact-quote checks establish that an excerpt appears in a selected source. They do not establish that the source is true or that the claim follows from it. Qualified reviewers make that assessment. Check data suitability and provider terms before submitting sensitive information.
Read the security and capability register →Start with one claim
Bring the statement. Bring the evidence.
Scope a pilot around a real review process, named reviewers and an agreed publication destination.