Evidence
Retained text, exact excerpts, version hashes and optional expiry. Reviewers assess whether the source is credible and relevant; a hash establishes content identity, not truth.
Foundry platform
The evidence. The decision. The exact version.
A workspace for the people who write product claims, the experts who review them and the owners who publish them.
- 01
Register the evidence
Retain source text, a version and the exact passage a claim relies on. Add an expiry date when support is time-limited.
- 02
Define the claim
Record the product version, operating conditions and limitations alongside the statement you want to publish.
- 03
Review independently
An authorized reviewer checks the evidence and records a decision. High-risk claims require two independent reviewers.
- 04
Publish the approved version
Publish a snapshot of the current approved claim. Its evidence and decision history remain in the workspace.
- 05
Respond to change
Evidence changes, expiry or revocation invalidate dependent approvals. Hosted publications are withdrawn; configured CMS deliveries enter the withdrawal queue.
Workspace Studio
Bring your documents into the conversation.
Describe the product, import supporting text and select the sources for your next question. A shared AI conversation helps develop a proposed claim with explicit conditions and limitations. Saving it starts the existing draft and review workflow.
Accepted formats and the startup workflow →Inside the record
Enough context to review the promise.
Claim
The proposed statement, product and version, operating conditions, limitations, risk level and linked evidence versions.
Decision
Reviewer identity, exact claim version, mandatory attestations and rationale. When source text continues after a linked excerpt, approval is refused unless the reviewer attests that they read it. That attestation is recorded; it does not prove the reading. Authors cannot approve their own claim or version.
Publication
A snapshot of the approved current version, its delivery status and a retained link back to the claim.
Change
A revised or revoked source invalidates dependent approvals. A hosted page checks source validity when it is requested, including expiry.
History
Earlier evidence, claims and decisions remain available. Database controls reject ordinary application updates and deletions to protected history.
Connected delivery
Use one approved version at the destination.
Hosted claim pages are available in Foundry. WordPress, Webflow and Contentful delivery requires a configured connection and an agreed content model.
External publishing and withdrawal use a retry queue. A provider outage can delay an external update; the delivery status remains visible.
Measured outcomes
Keep observations alongside the work.
Experiment records accept review time, costs and commercial outcomes through direct entry or an authenticated ingestion API.
A separate visibility connector records prompts, answers and citations from its configured API surface. It requires provider activation and does not measure every consumer search experience.
How we interpret the measurements →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.