Prompt-aware local workspace
Study, math, writing, quiz, and planning modes assemble deterministic structures in the browser.
PRODUCT STATUS
What is active.
What is active.
What is not.
Boardesa AI is currently a local education-product preview. This page separates browser capabilities, public site availability, and future live services so users never have to infer whether a model, account, or payment system is running.
BOARDESA RUNTIME
ACTIVE BUILDLoading build…
Public site shellAvailable
Local workspaceAvailable
Live AI routingNot active
Accounts and billingNot active
No prompt is sent to an external AI provider in the current workspace.
LOCAL PREVIEW ACTIVELIVE MODEL OFFBILLING OFFNO FRONTEND SECRETS
Current productA usable local shell,
A usable local shell,
not a pretend live service.
The preview is designed to make interaction, accessibility, session controls, and future integration boundaries testable before any external model processes user content.
Portable local sessions
Users can export and validate integrity-checked recovery files without uploading them to Boardesa. Import uses bounded JSON structure checks, strict session limits, metadata-only review, and a 256 KB file ceiling. Duplicate tabs coordinate only ephemeral lineage metadata and never share prompt content.
Adaptive route delivery
Common controls load separately from page-only interactions. Visited routes open from the current-build cache while updates refresh in the background.
External AI processing
No OpenAI, Gemini, Anthropic, or other model provider is connected to the public frontend.
Accounts, subscriptions, and credits
No sign-in, checkout, recurring payment, credit purchase, or billing renewal is active.
Document and image upload
The current product does not upload files for extraction, storage, or model processing.
Consent-based analytics
Google Analytics loads only after the user explicitly allows it through the cookie controls.
This browserCheck the local
Check the local
runtime boundary.
These checks run only in this page. They do not contact an AI model and do not upload session content.
Open Help CenterChecks will run when the page loads.
ConnectionChecking…CHECKING
Delivery profileChecking browser network preferences…CHECKING
Same-tab recoveryChecking session storage…CHECKING
Duplicate-tab safetyChecking ephemeral tab coordination…CHECKING
Offline shellChecking service worker…CHECKING
Cached shell buildChecking cached page and asset alignment…CHECKING
Atomic releaseChecking document, asset, manifest, and service-worker fingerprints…CHECKING
Update transitionChecking waiting-worker handoff, reload-loop protection, and the current-tab verification receipt…CHECKING
Production deliveryRun the public smoke test after deployment to check routes, MIME, cache headers, redirects, and the custom 404 response.NOT RUN
Compatibility layerChecking native features and local fallbacks…CHECKING
Optional analyticsReading the local privacy choice…CHECKING
Install stateChecking whether this browser exposes an install action…
CHECKING
Manual steps
Use the browser menu and choose Install app or Add to Home Screen. Installation keeps the current local-only product boundary.
Workspace transportFixed by this build; URL parameters cannot enable a live provider.LOCAL ONLY
01 Before live AI
The switch is not
just an endpoint.
A live provider should remain disabled until backend protection, quality evaluation, privacy decisions, visible limits, and incident controls are implemented together.
Protected backend adapter
Server-side secrets, independent payload validation, timeouts, retry lineage, and idempotency enforcement.
Visible limits and states
Clear handling for usage limits, temporary failures, cancellation, offline mode, and unavailable features.
Workflow quality gates
Separate evaluations for math, writing, study, quiz, lesson, planning, and summary workflows.
Privacy and retention map
Current same-tab recovery uses a visible rolling two-hour expiry, a 192 KB snapshot budget, explicit quota/blocked-state recovery choices, startup cleanup for stale records, and an opt-out for the active tab. Future provider processing, deletion paths, file handling, user history, and age-aware decisions remain launch gates.
Operational response
Incident reporting, provider outage handling, harmful-output review, rollback, and support ownership.
Commercial truthfulness
Prices, renewal, taxes, credits, refunds, and regional availability shown before payment is accepted.
Machine-readable statusOne public source
One public source
for integration state.
The status document records the active build, frontend transport, network use, live-service flags, and public technical contracts. It is documentation—not an uptime promise or API credential.
/.well-known/boardesa-status.jsonOpen status JSON ↗Workspace contract ↗Runtime manifest ↗Atomic release manifest ↗Deployment preflight manifest ↗Security posture ↗Status questionsClear answers before
Clear answers before
the live launch.
Does “online” mean a live AI model is connected?+
No. Online only describes the browser network connection. The current workspace transport remains local-only whether the device is online or offline.
Is this an uptime status page?+
Not yet. There is no live AI backend to monitor. The page reports the current product architecture and local browser capabilities without inventing uptime percentages.
Can a URL or imported file activate live AI?+
No. The active transport is fixed by the deployed build. URL parameters and portable session files can select only allowlisted workspace settings; they cannot select a provider or endpoint.
What does “fallback ready” mean?+
It means the browser lacks one or more native interface capabilities, but Boardesa has loaded a local replacement for dialog focus, background inertness, media-query events, or SHA-256 session checks. It does not mean a remote compatibility service was contacted.
How does a Boardesa shell update avoid reload loops?+
The waiting service worker must first confirm its atomically validated cache. Boardesa then waits for controller handoff, verifies the new build, reloads once, and stores a privacy-safe current-tab receipt. If convergence fails, automatic reload stops and a manual repair action is shown.
Where should a problem be reported?+
Use the contact page for product, privacy, accessibility, or security reports. Include the affected page and a non-sensitive example.
Explore safelyTest the product shell.
Test the product shell.
Keep the boundary visible.
The workspace is available as a local preview. Live AI and billing remain disabled until their launch gates are complete.
Open workspace