DemosIntegration evidence

Don't take our word for it. Break it yourself.

Each route exercises a real Atlas pattern with working, in-memory behavior. Use them to validate the architecture — not to browse a component catalog.

Demo mode active

All data is mocked with in-memory storage. No external backend is required. Changes reset on reload.

Authentication

Sessions that break SSR hydration or leak tokens into client storage.

useSession, server session reads, and httpOnly cookie boundaries.

useSession hookServer-side sessionSign in/out flow

Data fetching

UI drifts from the API and every screen invents its own loading/error handling.

OpenAPI types, central API client, React Query hooks, and state primitives.

React QueryOpenAPI typesMode switching

Forms and validation

Client and server validation rules diverge until users hit opaque failures.

Zod schemas, useZodForm, and applyServerFieldErrors.

Zod schemauseZodFormapplyServerFieldErrors

Feature flags

Releases are all-or-nothing deploys with no safe rollback path.

useFlag, FeatureGuard, and kill-switch patterns.

useFlag hookFeatureGuardKill switch

Observability

Production errors arrive without context or a way to correlate requests.

Normalized errors, correlation IDs, Sentry, and structured logs.

Sentry integrationStructured loggingCorrelation IDs

Themes and accessibility

Theme and keyboard behavior are bolted on after the product ships.

Design tokens, ThemeToggle, focus-visible, and ARIA patterns.

Light/dark/systemFocus visibleKeyboard navigation

Consent

Analytics fire before consent and privacy controls are inconsistent.

Consent provider, useConsent, and analytics gating.

CookieConsent v3useConsent hookAnalytics opt-in

Want the architecture behind the demos?

The platform page is the technical due-diligence surface.

Read the platform Start with data