FEM/atlas·← booth·brand book

Journey Atlas

34 journeys × 3 profiles. Same destination, different vehicle, different route. The ForEveryMind SDK doesn't paint the same web three colours — it ships three different webs that share manufacturer DNA.

34 journeys validated148 cross-consistency tests12 demo tables · 331 rows / session

anchor journey · 60s read

full detail →

Same task: edit-row-and-save

User opens a table, edits a single cell, and saves. The journey covers the most-touched cell-level slot (cell-suffix) plus the post-save surfaces (save-confirmation / main-postlude).

Connector

Monica

Battleship

sea route

Bring the team into the workflow.

  • Enter: feed-item
  • prelude · ActivityBlurb
  • on save · TeamSaveAck
  • conflict · merge

HSP flood + Connector → social context is the cheapest channel. The activity feed entry carries provenance the cell can attach ("by Aisha, 2m"), so the cell-suffix slot fills additively without layout reflow.

Try Monica's route →

Explorer

Nate

Tractor

field route

Show me what I don't already know.

  • Enter: schema-map-tile
  • destructive · AdvanceNoticeStrip 3000ms
  • chunk · 4
  • motion · 0ms

ASD prediction-error + ADHD focus + DYS GLUT-drain — the journey compensates by chunking to 4 rows, freezing motion to 0ms, and arming an advance-notice strip 3s before any destructive write.

Try Nate's route →

Analyst

Sara

Airplane

air route

Numbers first. Then we talk.

  • Enter: kpi-drill
  • prelude · KpiBand
  • trailing · Sparkline
  • on save · SaveLedger

Analyst + DA-from-data — the journey adds dense numerics (KpiBand, Sparkline, SaveLedger) so the existing reward loop keeps firing through the edit. CORT +19 bumps confirmation_dialogs to 'always' (see profile packet) which DestructiveGuard reads.

Try Sara's route →

why this matters

Three vehicles. Same manufacturer DNA.

“One of us needs a tractor, one needs a battleship and another needs an airplane. They are utterly different. But they should all share the brand book DNA.”

“It's not just the look — it's the way we use it. The user journeys will be different routes. Some take the field, the air or the sea to get to the same destination, each in an entirely different vehicle.”
— Nathan Lord, founder, ForEveryMind

full atlas · 5min browse

All journeys, grouped by surface

Database· 14

add-column-to-table

table-editor

User initiates column creation via the table editor toolbar. The journey covers the column-name input surface (typed-name for Sara, literal-language for Nate), the advance-notice strip for destructive-adjacent DDL operations (Nate), and post-save feedback including KPI impact (Sara) and team context (Monica).

monica · 3nate · 4sara · 3

add-database-trigger

database-triggers

User navigates to the Database Triggers surface, creates a trigger on a table, defines its action, and saves. The journey covers trigger creation with destructive-write patterns and impact analysis across three cognitive models.

monica · 4nate · 4sara · 4

add-foreign-key

database-tables

User initiates creation of a foreign key relationship in the database tables view. The journey covers the FK dialog (table/column selection), relationship visualization (Nate's SchemaMap), impact analysis (Sara's KpiBand), and team context (Monica).

monica · 3nate · 4sara · 3

create-database-function

database-functions

User navigates to the Database Functions surface, creates a custom Postgres function, reviews impacted tables, and saves. The journey covers function SQL editing, schema validation, and confirmation workflows across three cognitive models.

monica · 3nate · 4sara · 4

create-index

database-indexes

User initiates index creation via the database indexes surface. The journey covers index-type selection, column selection, and post-creation feedback including performance impact (Sara's query-plan reveal, Nate's micro-progress).

monica · 3nate · 4sara · 3

delete-column

table-editor

User selects a column and initiates deletion. The journey covers the confirmation modal (untouchable by brand policy), plus the pre-confirmation advance-notice (Nate's prediction-error mitigation) and post-deletion feedback surfaces (Monica's team context, Sara's schema-change ledger).

monica · 1nate · 4sara · 2

delete-row-or-table

table-editor

User selects a row or table and initiates deletion. The journey covers the destructive-op confirmation modal (untouchable by brand policy), plus the pre-confirmation advance-notice (Nate) and post-confirmation feedback surfaces (Monica's activity context, Sara's row count ledger).

monica · 1nate · 4sara · 2

edit-row-and-save

table-editor

User opens a table, edits a single cell, and saves. The journey covers the most-touched cell-level slot (cell-suffix) plus the post-save surfaces (save-confirmation / main-postlude).

monica · 4nate · 4sara · 4

export-table-csv

table-editor

User initiates table export to CSV via the table toolbar or context menu. The journey covers column/filter selection, export format options, and post-export feedback including team-sharing (Monica), row-count snapshot (Sara), and pagination progress (Nate).

monica · 2nate · 4sara · 2

find-table-and-view-schema

database-schemas

User finds a table and views its schema. Three entry points: Monica via team activity feed ("Aisha just added orders/v2"), Nate via SchemaMap visual discovery, Sara via KPI hub drilldown into table metrics.

monica · 3nate · 4sara · 3

insert-new-row

table-editor

User opens a table editor and inserts a new row via form or grid inline. Monica gets activity context on save. Nate gets advance-notice strip before destructive write + chunk-size 4 pagination. Sara gets save-ledger feedback.

monica · 3nate · 4sara · 4

rename-table

table-editor

User initiates inline renaming of a table via double-click or context menu. The journey covers the inline-edit input, confirmation, and post-rename feedback surfaces across the three cognitive profiles.

monica · 3nate · 3sara · 3

search-value-across-table

table-editor

User applies a filter or search to a table and navigates paginated results. Nate gets DiscoveryCard idle filler + chunk-size 4. Sara monospace metrics + Sparkline. Monica gets activity context on discover.

monica · 3nate · 4sara · 4

view-schema-diagram

database-schemas-diagram

User opens the schema diagram surface to explore database relationships visually. The journey covers the ERD view, table-hover details, and contextual overlays including team activity (Monica), KPI metrics (Sara), and schema-first navigation (Nate).

monica · 3nate · 4sara · 3

SQL Editor· 5

Auth· 4

Storage· 3

Edge Functions· 4

Realtime· 1

Reports· 1

Settings· 1

Other· 1