01. The current environment
The dashboard is a local simulation. It does not create a confidential virtual machine, remotely verify a GPU, sign a production receipt, submit a chain transaction or execute a real payment.
02. Trusted execution is a boundary
The intended TEE design protects execution from the host, cloud operator and co-tenants. It does not protect against malicious behaviour in approved code running inside the enclave. Hardware vulnerabilities and weaknesses in attestation, firmware, serving images or policy management can affect that boundary.
03. Provenance is not correctness
A receipt binds execution to measurements and hashes. Even a valid production receipt would not establish that the model output is true, safe, unbiased, legally sufficient or suitable for a financial or other consequential decision.
04. Payment visibility
Confidential transfer amounts are intended to be shielded while addresses remain visible. Timing, metadata, counterparties and selective disclosures may still reveal information. A view key deliberately grants access to a defined scope.
05. External dependencies
The architecture depends on hardware vendors, attestation roots, infrastructure availability, chain services, contract correctness, wallet controls and measurement policy governance. Outages, compromise or changed specifications can interrupt operations.
06. Roadmap and tokens
Milestones are plans and may change. References to $ENCL do not establish token availability, liquidity, value or returns. No investment or staking product is offered by this preview.
07. Production readiness
A live launch requires deployed and reviewed infrastructure, tested contracts, verified current network addresses and APIs, operator disclosures and an appropriate security and legal review. The current website is not evidence that those steps are complete.