Story: Open the web as an Acme persona

Table of Contents

This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

1. Goal

Test the web as different Acme users without adding profiles to the developer's own Chrome. One command opens an isolated browser with the username and password filled in, so only Sign in is left to press.

2. Status

Field Value
State DONE
Parent sprint Sprint 27
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-10-10

3. Acceptance

  • compass open-as with a person's name opens an isolated Chrome on the web login with that user's credentials filled in.
  • compass open-as can also choose a person by job title and location, or by role and location, with London as the default location.
  • The command leaves the developer's own Chrome profiles untouched and is documented as a recipe.

4. Tasks

Task State Start End Description
Scaffold story: Open the web as an Acme persona DONE 2026-10-10 2026-10-10 Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR.
Add compass open-as to launch Chrome as an Acme persona DONE 2026-10-10 2026-10-10 Initial task for: Open the web as an Acme persona

5. Decisions

  • Each persona gets its own Chrome --user-data-dir under ~/.cache/ores-personas, not a Chrome profile. A separate data directory never shows in the developer's profile picker and never syncs.
  • The sign-in form is filled through the DevTools protocol with a standard-library socket client, so compass gains no dependency. The password is never stored in the browser.
  • Acme's tenant, password, offices, roles and titles are hard coded, because the tenant is fixed. The staff come from the seeder's accounts.json.

6. Out of scope

7. Result

compass open-as name, title or role opens an isolated Chrome with the Acme sign-in filled. See the recipe "How do I open the web as an Acme user?".

Emacs 29.3 (Org mode 9.6.15)