API Status
Treat the current API surface as application routes, not a final public developer platform.
Document only routes that exist and are used in the product. Avoid publishing broad v1 API claims until authentication, versioning, rate limits, and support policy are ready.
Receipt Pack
The receipt workflow should return enough metadata for review:
json
{
"metric": "Revenue",
"periods": ["2024-10", "2024-11"],
"sql": "SELECT ...",
"source": "demo-trust-loop.csv",
"rowCount": 4,
"sqlHash": "...",
"evidencePackHash": "...",
"generatedAt": "2026-05-16T00:00:00.000Z",
"reproducible": true
}Trust Report
Trust reports should explain the verification boundary:
- What was verified
- What was projected
- What diverged
- What was not verified
- What data was used
- What SQL was run
- Whether the answer can be reproduced
Developer Caveat
Do not promise SDKs, public keys, embedded analytics, or unlimited API access until those capabilities are implemented and supported.