How to review Analyticity product claims before publishing
Use the product claim ledger to decide whether a public Analyticity Tech claim should be kept, softened, sourced, or removed.
Analyticity Tech public copy covers Skrrol, Unitly, and SiteCue. The product claim ledger keeps that copy grounded: live Skrrol capabilities stay live, SiteCue stays prelaunch until readiness changes, and unsupported trust or company claims stay out of public pages. This checklist describes the review flow used for the website.
Walkthrough
- 01
Find the claim
Read the public sentence as a user would. Identify the factual claim inside it: product ownership, launch status, feature availability, pricing, compliance, company identity, or market positioning.
- 02
Match it to the ledger
Look for the claim in docs/product-claim-ledger.md. If it is not represented there, add it before publishing the copy.
- 03
Check the status
Keep verified and owner-provided claims. Use planned language only when the page clearly says the feature is not live. Treat source-needed claims as blockers for public copy.
- 04
Soften or remove unsupported copy
Remove unsupported claims about C2PA, consent-verified voice cloning, SOC 2, model cards for every shipped model, design partner programs, founding date, headquarters, stage, funding, or official launch dates.
- 05
Update the tracker
After the edit wave, update docs/website-update-continuity-tracker.md so the next person can see what changed and what still needs verification.