PRODUCT WALKTHROUGH

A decision trail in five minutes

Start with the EU–Qatar reference case. It contains a fictional company scenario and independently researched official sources, with unresolved questions left visible.

1. Open the reference. In the demo, explore Overview, Evidence and Gates. Edits last only for this session. The example has no confirmed company eligibility or reviewer approval.
2. Create your own workspace. Open My workspace and sign in. Copy the reference or create a blank case. Define the company, activity, constraints, decision owner and next action.
3. Record the source-level reasoning. Add each proposition with its authority, HTTPS source URL, jurisdiction and the date you actually checked it. Leave unresolved interpretations as Needs review or Assumption.
4. Sequence the gates. Link each decision to supporting sources and earlier gates. Assign its owner and due date. Atlas rejects circular or missing dependencies when saving.
5. Save a version. Changes stay unsaved until you press Save version. If another session saves first, Atlas holds your save and opens a three-way comparison. Independent edits are combined; choose the draft or server value for each conflicting field. Review the combined draft and save separately. Invalid dependencies cannot be saved; you can download your original draft and return without merging.
6. Optional peer review. In Access, create a reviewer invitation. Send the link privately. It expires after seven days and accepts one signed-in account. The owner cannot approve their own case. Atlas does not verify the reviewer's qualifications. Research and preparation can continue without this record.
7. Export the brief. Check Brief, download text or choose Print / PDF. Every export retains the source references and review status. Use History to retrieve saved snapshots.

When the workspace connection fails

A failed initial read is shown as a connection problem, not as an empty account or a sign-out. Retry loading workspace repeats only the account and requested-case reads, keeping the validated link target. There is no automatic retry and no create or save action. If the portfolio loads but one case does not, the list remains available so you can choose a saved case explicitly. A failed save has a different recovery path: keep your draft and inspect the server version before repeating it.

Save confirmation must match the submitted content and the exact next version. Review confirmation must remain on the version you reviewed. If another session changes the case before the server responds, Atlas treats the outcome as uncertain instead of replacing your draft with that different version. Your action may already exist in History; keep a backup and inspect the latest saved case before repeating it. No write is retried automatically.

Use the check-up before saving

Atlas checks the complete UTF-8 JSON request against its 200 KB limit before sending it. Action metadata counts toward the limit. A local size or JSON preparation failure says Request not sent and leaves the draft untouched; it does not imply a possible server save. Once a request is transmitted, a lost or mismatched response is still treated as uncertain. No content is silently shortened to fit.

Check-up lists contradictory gate states, stale or incomplete evidence, missing owners and overdue actions. The work queue identifies open gates whose entire prerequisite chain has passed structural checks; it does not permit any regulated business activity. These are deterministic checks, not an AI legal opinion or a success probability. Evidence can be searched by claim, authority or jurisdiction, and filtered to items needing attention.

See the work plan and source impact

Plan explains which gates are ready for research, explicitly blocked, waiting on prerequisites or marked satisfied but needing a completion recheck. A prerequisite needs a satisfied status, named owner, valid date, current linked evidence and structurally complete earlier prerequisites. This rule is shared with Check-up, not a separate confidence score.

Filter by owner or question, work status, or one source to see all gates that depend on it, including downstream links. Open gate / Open source takes you directly to the matching record. Dates earlier than a prerequisite are flagged for review; no dates or statuses change automatically. Download work plan includes the whole case, not only the filtered view. A structurally complete gate is not a verified legal or business conclusion.

Open the right case without granting access

In an account case, Case link prepares a private navigation link for existing collaborators. It is not an invitation and never grants access. On opening, sign in with the intended account; Atlas checks permission and loads the latest saved version in the linked section, including cases outside the first portfolio page. Unsaved edits and a fixed version are not included. The entry fragment is consumed once and removed from the address bar; use the prepared link if you want to bookmark it. A later normal reload opens your usual portfolio.

Find cases by recorded review state

Portfolio filters can separate Current review recorded from No current review. They use the last loaded saved snapshot and the same preparation checks as the workspace. A source check becoming stale removes the current-review indication when the time snapshot refreshes. Refresh the portfolio to fetch later review or access changes. These filters never verify a reviewer's professional qualification or grant access.

If more than one currently authorized reviewer has recorded review of the current version, the case and portfolio show the most recent record. Equal timestamps use a stable identifier tie-break, not a ranking of reviewers. Losing access, a new version or stale source checks can remove a record from the current summary. This is not a consensus, a count of independent checks or professional certification.

Removing a collaborator preserves your open content and unsaved edits. If another session has saved a different version, its review is not copied onto your open version. Keep a draft backup and reopen the saved case before relying on its current review. A removal response without a confirmed updated member list is treated as uncertain, not success.

Take selected work dates with you

In Plan, open Export selected dates to a calendar. Select dated work, prepare the preview and download or copy the .ics text. The export includes the case title and selected work, not the full case or its sources. Undated items and gates marked Satisfied are excluded. All-day dates are user-entered planning dates, not verified official deadlines. No calendar is connected and no invitation or alarm is sent. Use a private, separate calendar and inspect imports; re-import behavior and duplicate handling depend on your calendar app. This is a snapshot, not ongoing synchronization or a case backup.

Recover a draft without overwriting history

Open Changes to compare current edits against the selected saved version. Added, removed and changed fields are shown separately, with a plain-text report you can download. In History, choose Compare beside any saved version or enter its number. Comparison never restores content or records approval. Unsaved edits, if present, are included and labelled.

Atlas attempts to protect unsaved case fields in this browser tab's session storage. Reloading offers Recover draft, Download recovery or Discard recovery. If the server version changed, recovery starts a new draft. If access is no longer available, download the recovery and resolve access separately. This is not encrypted storage or a guaranteed backup. Unfinished source/gate forms are also protected in this tab and included in draft exports, but are not saved records until added. Save version remains the server-save action. If a save's network result is uncertain, check the latest saved version before retrying.

Import case JSON accepts a file; Paste backup JSON accepts copied backup text when a file selector is inconvenient. Both show a content preview before creating a separate case, discard imported reviews and access grants, and reject unsupported schema versions. New backups have a SHA-256 checksum to detect changes, not to establish authorship or evidence authenticity. Older files are explicitly labelled as having no checksum. History snapshots can be downloaded and imported as separate cases to recover earlier content without rewriting the original trail.

A browser recovery draft can still be recovered when its original saved case is no longer available or your access has changed. Atlas uses only the cached local content and opens a separate unsaved draft. The old case, its history, review and permissions are not restored. Create case is a separate decision. A connection failure or expired sign-in keeps the recovery prompt and backup option available instead of assuming the original case was deleted.

Reuse structure without carrying conclusions

New case offers market-entry, partnership and pilot-research starters. They contain open questions, not jurisdiction-specific legal requirements. Reuse as template copies sources and gate links with new identifiers, clears source-check dates and completion flags, and removes old owners, deadlines and case-specific context. Reassess all copied propositions. The original case and its review history remain unchanged.

The case portfolio searches titles, locations, owners, decision questions and next actions. Filter for attention, overdue actions or access role; sort by update, title or date. The list reflects saved cases, not current unsaved edits. The latest page loads first, up to 25 cases and a bounded response size. Load older cases extends the list; search and filters cover loaded cases only. Refresh portfolio returns to the latest page and keeps your current draft intact. If another user changes or shares a case during pagination, refresh for its latest place in the list. Pagination is not a frozen snapshot.

Free on-device AI: optional, experimental

Open AI lab, choose Summarize case, Find gaps or Suggest next steps, select 1–6 sources and press Preview analysis input. Read the exact input and acknowledge it. With compatible desktop WebGPU and roughly 2 GB of free GPU memory, approve the approximately 1 GB model download and press Load free local model. Once ready, Run local analysis. The first load may take several minutes; model assets are cached for later use. No API key or AI API fee is required. There is no automatic paid or cloud fallback. The browser, GPU and network may prevent loading.

Summaries contain model-selected exact source excerpts, not AI-written factual paraphrases. Relevant excerpts may be omitted. Generated English research questions are drafts and can contain mistaken assumptions, not verified conclusions. Selected next-step suggestions can become open, unassigned research gates only after you explicitly add them. Save the case separately. Changing the input invalidates the previous draft. Sources are user-entered records; the model never retrieves their URLs. Read the input preview's exclusions: omitted profile and constraints make this a limited research analysis, not an assessment of eligibility.

Stop / release model cancels active work and frees model memory. Model cache remains until Remove model cache or browser eviction. Leaving the AI section stops active model work. Copy a useful draft before reloading: local AI results are not automatically saved or included in case backups. If an embedded page cannot run the model, open Atlas directly using the links in the panel. Read local AI data handling.

Advanced manual AI preparation

The advanced manual section prepares a local research packet from a question and up to 20 selected source records. No model call or automatic web research takes place. Inspect the visible packet before using it elsewhere. A separately obtained structured proposal can be pasted for validation; this separate manual workflow does not generate an answer. Validation checks the current case, question, selected sources and exact excerpts of your entered claims. It does not prove those claims or the proposed reasoning are correct.

Selected suggestions become labelled open, unassigned research gates in an unsaved draft. They never check a source, complete a gate or grant approval. Changing the case, question or source selection requires a new packet. There is no paid AI activation or API-key input in the app.

For integration tests, the input format can also accept a complete Responses API result. Refusals, incomplete or failed results, unexpected tool calls and ambiguous output are not accepted as usable proposals. Pasting a result does not verify who generated it and never contacts the provider.

Lab questions and pasted inputs remain available when switching between sections of the same case. Use Back up / restore lab inputs to copy a separate notes JSON before reloading or switching cases. Restore it against the same case snapshot, acknowledge the material again, prepare a new packet and validate the retained pasted input. Clear lab inputs does not delete case records or gates already added to the draft.

Show the reference without overstating it

Open the public practice workspace and choose Start reference tour. The six steps visit the case context, evidence, gates, work plan, optional local AI lab and brief. The tour changes only the visible section: it does not edit data, make model calls, save anything or simulate an approval. Close it at any point to explore freely. Use the direct workspace link for a full-width demonstration outside an embedded website frame.

If the connection drops

Workspace requests stop waiting after 30 seconds. Keep the current draft: a timeout or broken response does not prove a save, creation or access change failed. Atlas does not automatically repeat the action. Export your draft, refresh the portfolio, and inspect the latest saved version before retrying. Refreshing the list does not overwrite the draft; opening a case is a separate action. If a save reached the server, the next stale-version save opens conflict review instead of silently replacing it. An unchanged creation retry from the same page reuses its request ID and returns the existing case within a seven-day receipt window. This does not survive refreshing the page or editing the attempted content. It is not automatic retry or offline sync: check the list first, especially after reloading or changing a draft.

Build with no external-expert budget

Start with public-source research, fictional demonstrations, workflow interviews and a non-sensitive preparation workspace. No paid specialist or additional AI API is required to use those features. Hosting and business operating costs still depend on provider terms; zero total running cost is not promised.

1. Demonstrate one narrow business question with its sources and unresolved gates.
2. Ask target users to perform their normal workflow, note where they struggle, and record feedback without claiming them as customers.
3. Validate whether a source-linked preparation brief is useful before promising regulated advice, incorporation or approvals.
4. Keep specialist-dependent questions marked Needs review. Arrange qualified review when an actual service requires it, with scope and cost agreed separately.

Install on your computer or phone

Open the account workspace directly in a full browser, rather than inside an embedded frame. In Chrome or Edge use the installation icon or the browser's Install app menu. In iPhone Safari choose Share, then Add to Home Screen. Atlas opens in its own window. It remains a web application and requires internet for account data. No app-store listing is claimed.

Your older local demonstrator data

The earlier browser-only workspace used a separate local storage key. This release does not delete it or silently send it to a server. Keep any old JSON exports. Older schemas need a deliberate conversion before importing into the account workspace; contact the project owner if you need that migration.

When a route should stay on hold

Leave it on hold if a source is stale, an activity classification is uncertain, an authority has not confirmed a material detail, or the reviewer has not checked the current version. A useful research trail can still be shared for review without pretending the decision is finished.