Skip to main content
Goal: build your own personal context — preferences, vocabulary, a saved workflow — verify it persists across threads, and learn what must never go in it.
If a save lands in the wrong place —If Ana says she can only save to the shared library, or writes to a generic path instead of users/<your-email>/context.md, the routing file from Module 1 isn’t loaded. Stop and fix the routing setup — the ANA.md file from Module 1 isn’t loaded — before continuing; every later module depends on it.

​
2.1 · Preferences

Prompt
You’ll see: Ana confirm what she’s saved to your personal context. This is the immediate layer — no review, no patch, effective now. Note what you just did not change: nothing about how Ana behaves for anyone else.

​
2.2 · Personal vocabulary

Prompt
You’ll see: your shorthand saved. From now on, “how did the big three do during EOQ crunch?” just works — for you.

​
2.3 · A saved personal workflow

The highest-leverage personal item — a multi-step ritual reduced to one phrase:
Prompt
You’ll see: the workflow recorded. Next Monday: two words instead of twenty minutes.

​
2.4 · The persistence test

Saved context is only real if it survives the thread. Verify: start a NEW thread (context selections load fresh per thread), then ask:
Prompt
You’ll see: your items come back. Then:
Prompt
You’ll see: the personal layer carrying across threads. If something didn’t persist, it was answered conversationally but never saved — re-ask with an explicit “remember/save this.”

​
2.5 · The hygiene rule — what NEVER goes in personal context

Personal context is for things that are true about you. The moment an item is true about the business, it belongs upstairs:
ItemBelongs in
”I like tables over prose”Personal ✓
“Active member means [definition]“Org — a definition in personal context forks the truth: your answers silently diverge from your teammates’ on the same question
”Our team never shows SQL to stakeholders”Role — that’s a persona behavior, not a preference
”The [X] table is deprecated; use [Y]“Org (or connector-scoped) — everyone querying it needs to know
The test: if a colleague asked the same question, should they get the same treatment? Yes → org or role layer, via the reviewed path (Modules 3–4). The forked-truth failure mode is Module 7’s first table entry for a reason — it’s the most common context-stack disease, and it starts here, innocently.
Personal context: set once, applies everywhere.

Personal context: set once, applies everywhere.

​
✅ Checkpoint

  • Preferences, vocabulary, and one workflow are saved to your personal context
  • A NEW thread recalled all three without re-explanation
  • “Run my [workflow]” executed the full ritual from the saved definition
  • You applied the hygiene test to your own saved items and moved (or flagged) anything that’s actually business truth