CHISAN · connected preview
Frontend and API.
Separate deployments, one connection.
This review checks a real cross-origin HTTP connection between Cloudflare Pages and a separate Cloudflare Worker. The private AI, Rust and Guardian runtimes remain offline from the public internet until their security acceptance is complete.
Checking API connection…Requesting the separate Cloudflare Worker.
Awaiting live response
Two deployed layers, one honest status
Live API request · static frontend
Frontend / Pages
CHISAN UI Review
Independent static web deployment. The original Chisom experience remains live on its existing production site, unchanged.
Backend / Worker
Checking…
The independent Worker API responds to real network requests. It is a public-safe operational interface, not the private AI engine.
AI / Private Ubuntu
Not verified
Rust mission services, device identity, Guardian and local AI remain protected from public Cloudflare access.
Backend readiness, directly from the API
R0 read-only edge status only
API transportChecking…
Independent Worker endpoint; browser must receive a valid schema response.
Private Rust backendNot verified
An HTTP 200 response from Cloudflare does not prove Rust is running on the Ubuntu server.
Guardian / identityNot accepted
Actual signed identity, scope, recovery, revocation and Guardian enforcement remain separate release gates.
24 Directors0 activated
All roles remain dormant while owner release and model gates are in force.
Model runtimeDownload hold
No inference endpoint or paid cloud-model fallback is connected by this preview.
Security boundary: This is a real frontend-to-edge-API connection, not a connection to CHISAN's private runtime. No mission records, personal data, identity tokens, Guardian approvals or device controls are sent to Cloudflare. If the API is unavailable, the UI reports a failed check instead of displaying fabricated live information.