Offline · saved shell

You are offline—your browser-local work may still be here.

Reconnect to open uncached pages or current evidence. Do not clear site data if you need a locally saved course or decision record.

Recovery guidance

Eight pages, and nothing pretending to be more.

A service worker saved a small shell when you first visited. Those eight pages open without a network. Every other address on this site — including the tool and course pages themselves — shows you this page instead, because their content was never stored and there is nothing honest to display in its place.

Being offline did not touch it. Clearing site data would.

01

The records are still in this browser.

Course progress, decision records, comparisons, pilot designs and Studio answers live in this browser’s storage, not on a server and not in the page cache. Losing the network does not reach them. They are exactly where you left them, and they will be there when you reconnect.

02

You need the network to reach the page that reads them.

The builders and course workspaces are not among the eight saved pages. Their data survives; the interface that opens it does not load offline. This is a limitation of the cache, not a sign that anything has been lost.

03

Do not clear site data to fix this.

Clearing site data, cookies, or “site storage” for this domain is the one action that genuinely destroys the records, and it cannot be undone by anyone, including Aloha AI. A stubborn offline state is a network problem; treat it as one.

04

Export as soon as you reconnect.

Every workspace writes a Markdown, JSON or plain-text file to your device on request. An exported file is the only copy that survives a cleared browser, a new device, or a private window. Do it at the end of the session rather than the end of the project.

Read the full recovery guidance →

Offline access is deliberately limited.

The saved public shell is not proof that evidence, policies, or course materials are current. A cached page is a copy of what this site said at the moment it was stored, and the Source Desk records behind it may have moved, been revised, or been withdrawn since. Export important browser-local records when you reconnect, and re-read anything you intend to rely on.