TraceRookWhat Demo contains
Cloud Demo is a finished-looking product walkthrough backed exclusively by local fixture JSON. It includes a sample account, plan, usage values, sessions, incidents, and an interactive sample review.
Sample identities and statistics are synthetic. The dashboard and affected views identify them as Demo or sample data. The demo exists to make the native interaction testable before real integrations are available.
No analysis network requests
The demo provider and mock cloud API client read bundled resources and make no outbound requests. There is no TraceRook Cloud authentication, billing, metering, subscription, or production analysis backend in MVP1.
The public product website is also static. It never reads agent sessions, performs Claude analysis, or accepts API keys. Hosting access controls are separate from the native app’s Cloud Demo.
Keep real activity separate
A real session must never be passed to the fixture provider and reported as analyzed by Cloud. The intended live behavior when Demo mode is selected is local deterministic rules only for real sessions, with a clear provider indicator.
In the current development milestone, live ingestion and enforcement are not connected at all. Real sessions remain empty and Not integrated. Selecting a sample provider is not a way to enable protection.
Try a sample review
Simulate review creates a local synthetic pending action. Try Block, try Allow once on a fresh sample, and let another request expire. The sample exercise demonstrates terminal transitions and late-response rejection, without issuing a dangerous command.
The fixture flow does not test a real host waiting on a hook. That requires the separate MVP2 live-host acceptance gates.
The future Cloud contract
The architecture separates the analysis provider from the cloud account API. A future HTTPS implementation can replace the mock behind its protocol, but a future-facing data model is not an operational service.
The provisional API includes device registration, account, usage, plans, analysis, and incidents. Real auth, billing, account enrollment, and subscriptions are deferred. See protocol reference for the contract boundary.