Trust
Follow the data.
Identify the boundary between this website and an intended Merism workflow.
Inspect every boundary.
The current website preview runs locally with synthetic values. The product flow below is a design model whose production configuration and retention still require verification.
The task begins with authorized inputs.
Conceptual Merism flow: a person supplies a task and data they are entitled to use. The public website does not collect a product prompt or upload.
Control: choose the task, context, and permitted scope.
What actually happens in this website preview?
Your browser requests the page and local assets through the hosting edge. The walkthrough uses values bundled with the page. It keeps its state in browser memory, calls no model or external tool, and writes no walkthrough state to browser storage. Reset clears that state. Ordinary page delivery remains subject to the hosting edge’s operational data handling.
This website
A page request reaches the delivery edge. The synthetic walkthrough runs locally; no model call, upload, account login, or connected action occurs.
An intended Merism workflow
A user supplies an authorized task. Merism prepares the request within its permitted scope. Approved infrastructure may route necessary data to an approved model or tool. The result returns for verification before being presented to the user.
Permission at each step
File access, provider processing, connected-service reads, and consequential writes require their own defined purpose and scope. A model output cannot grant new authority.
Retention and control
Actual retention, deletion, revocation, and provider data terms must be verified before a public feature uses that flow. This conceptual map does not claim those product controls are deployed.