The scope of the demo and the actions it simulates.
Browse a fictional catalog, compare strategy evidence, simulate investments and exits, manage demo permissions, and run fixture-backed compatibility checks. Each browser session has isolated demo state.
The prototype does not send money, request transaction signatures, process identity documents, or issue investment credentials. A verified scenario selects a fixture; it does not verify a person.
Follow the demo journeysDemo wallets keep separate holdings, preferences, and receipts. Reloads retain server-held records while the mock process runs. Restarting the server or resetting this demo clears those records.
Scenario controls can intentionally introduce stale evidence, failed requests, rejected confirmations, and delayed responses. These demonstrate recovery behavior and do not describe a live service’s reliability.
Check this mock sessionProduction eligibility rules, provider arrangements, investment terms, custody responsibilities, fee schedules, and legal agreements need their own review and implementation. None are established by selecting a demo persona or confirming a simulated operation.
For product background, visit the Epoche documentation. Developer material lives at epoche.build.
Skip to content