Start in Observe on one route. Use the deployment URL and installed package version supplied for your workspace. Historical host examples and source capabilities do not establish a live service or published release.
Hosted recipes
All normal protected browser actions use hosted Gate authority. Install the
reviewed unpublished kit packages described in SDK overview.
Local crypto examples are restricted to DEADMAN and bounded legacy/test use.
Keep the original request method/target, opaque proof and authenticated response
updates intact; no manual snippet should reconstruct them from parsed body data.
| Runtime | Supported recipe |
|---|---|
| Express | mandateHosted or mandateManagedMiddleware; authenticate user first |
| Next.js App Router | withMandateHosted or withMandateManaged |
| Go net/http | HostedMiddleware.Handler or ManagedMiddleware.Handler |
| Python Flask | require_mandate_hosted or require_mandate_managed |
| Python FastAPI | hosted response helpers or managed_route_class |
| Cloudflare | vendored connector; first-party collector and canonical hosted/Reroute lane |
| Vercel | vendored Observe sensor/collector; server hosted adapter enforces actions |
| Fastify/Hono/Gin/Django | use the original request with supported hosted helper; framework-specific adapter not claimed |
| NGINX/Envoy | supported-runtime hosted sidecar or explicitly commissioned Managed ingress; no generic bundled local verifier |
See complete Backend, Node, Go,
Python, and Edge guides. Set an
explicit HTTPS Gate endpoint and a server-only tokens:validate API key. Trusted
Subject/accountKey must come from your authentication, not a browser account
header. Observe proceed does not authenticate a user or prove verified trust.
Customer-owned wait rooms
The kit includes Express, Next.js, Go net/http, Flask and FastAPI examples under
examples/queue-wait-room/. Return configured queue responses as
202 with opaque queueToken/retryAfterSeconds; retry only the explicit customer
request after the wait. Never parse/store queue tokens as authorization or
automatically resend a business action after response loss. Throttle returns429;
fresh proof and customer-owned step-up stay within their documented adapters.
Native sessions
iOS and Android candidates adopt complete authenticated rotation atomically and
refresh explicitly over HTTPS. Native state cannot be treated as a browser
cookie or partial token replacement. Adapters preserve state even when an
admitted operation later refuses; ambiguous state fails closed. Binary pipelines
and synthetic transport/vendor tests do not establish real-device readiness.
Reroute
The default-off candidate supports 1–8 explicitly enrolled actions, with exact
raw-body proof, Gate Verify/Limit admission, private origin guard and intent/result
reservation. Application authentication stays mandatory. Receiver readiness is
an operator attestation, not liveness. See Edge.
Testing and rollout
Source unit vectors and isolated package consumers are supplemental proof.
Start Observe, review grouped Activity and false positives, enforce a single
route, and preserve a rollback plan. Laptop frontend production builds/E2E are
not accepted project verification; release workflows own those checks.