Transparency
The product should say exactly what is live, beta, preview, and disabled.
Transparency is a conversion tool for technical buyers. It reduces confusion, prevents overclaiming, and makes the beta more credible.
Public truth table
| Area | State | What users should expect |
|---|---|---|
| Signup | Live | Creates limited workspace and dashboard session |
| Dashboard | Live beta | Onboarding, limits, demo workspace, artifacts |
| REST API | Live beta path | Video records, execution, artifacts, Ask Video, cost |
| MCP | Preview-only | Resource/tool design, no production authority |
| Checkout | Disabled | Paid plan reservation only until billing activation |
| Email/CRM automation | Disabled | No automated outreach from signup |
| High-risk actions | Blocked or review-required | No identity, emergency, physical access, destructive action |
Why this matters commercially
A technical buyer can forgive a small beta plan if it is clear. They cannot trust a product that hides disabled features, makes unsafe autonomy claims, or claims GPU-equivalent behavior without evidence. The product should show its boundary in the same place it shows its promise.
{
"live": ["signup", "dashboard", "REST beta", "artifact inspection", "cost reports"],
"preview": ["MCP resource catalog", "agent tool wrappers"],
"disabled": ["checkout", "email automation", "CRM writes", "destructive actions"],
"review_required": ["identity", "intent", "physical access", "emergency", "disciplinary decisions"]
}Transparency checklist
- Every CTA should match a working path.
- Preview features should not sound production-ready.
- Cost and limits should be visible before failure.
- Evidence and confidence should appear before answers become decisions.
- Disabled systems should remain explicitly disabled until verified.
Product boundaries are part of the product, not footnotes. Ayneye is not presented as a replacement for every GPU video foundation model, not a free-infinite-query engine, and not an autonomous surveillance decision system. The current beta path is controlled signup, dashboard, REST API, bounded processing, evidence artifacts, visible limits, and read-only agent/MCP-style evaluation. Hard scenes, identity-sensitive workflows, emergency response, physical access, discipline, and destructive actions require human review or remain blocked.