Free lesson

Five Layers: Where Everything Lives

Five Layers: Where Everything Lives — Your Personal AI Assistant: Build One That Knows Your Context, No Code Needed. One assistant, five places for information; What each layer is for; When everything ends up in one place; A fictional example, worked through; Map your current assistant. Practical assignment: Audit the five layers.

Demo edition. The materials are undergoing editorial review.

Topics covered

  • One assistant, five places for information
  • What each layer is for
  • When everything ends up in one place
  • A fictional example, worked through
  • Map your current assistant

One assistant, five places for information

In lesson 1, you gave your assistant some basic settings. That is only one layer. When everything goes into a long chat, memory, or global instructions, temporary details compete with lasting ones, and conflicting versions of the same fact become hard to locate.

A useful working model has five layers:

| Layer | What belongs there | Typical lifetime | |---|---|---| | Instructions | How you want help; a few facts needed almost everywhere | Until you change them | | Memory | Stable facts and preferences | Months, with review | | Projects | Chats, rules, and material for one area | While that area is active | | Reference files | Schedules, rules, lists, and other project details | Until the next dated update | | One-off chats | A request you will not need again | For the current task |

Use two questions to place an item: How often does it change? and Where is it needed? Frequent change points to a dated file or one-off chat. Information needed in only one area points to that area's project.

What each layer is for

Instructions affect many answers, so keep broadly useful rules there: “answer briefly,” “label assumptions,” or “use metric units.” A detailed renovation plan does not belong there.

Memory can carry information between chats. It suits preferences or context that rarely change. Temporary, incorrect, or overly sensitive entries should be reviewed and removed when appropriate.

A project brings together one continuing area, such as a renovation, a course, or university applications. Depending on the service, it may have its own instructions, files, and context from chats. Do not treat a project as a guaranteed privacy boundary; check the memory, access, and sharing settings in the service you actually use.

A reference file holds exact details that a project needs. A short file with a title, update date, and current facts is easier to check than several pasted copies spread across chats.

A one-off chat suits a sign translation or a draft of one message. Temporary mode is a separate feature: how it handles history, existing personalization, and retention depends on the service and settings.

When everything ends up in one place

One endless chat feels convenient, but old and new conditions become mixed. A model has a limited working context, so you should not treat the entire transcript as a guaranteed active reference. Keep a continuing subject in a project, then start fresh chats for distinct tasks with the current file or a short handover summary.

Other common mistakes include:

  • making global instructions describe every possible situation;
  • leaving a temporary fact such as “I am on night shifts this month” in long-term memory;
  • recording the same fact differently in three places;
  • assuming that a project provides absolute isolation without checking its memory and access mode.

If a fact genuinely must appear in two places, name one authoritative source. For example: “For current dates, use deadlines-2026-11.md.” You then update one file rather than several copies.

A fictional example, worked through

Fictional example. Marta has a global instruction that says, “Answer briefly.” Memory still contains “I am on night shifts this month,” saved a year ago. She manages a three-month renovation in a chat called “Miscellaneous” and pastes each new estimate into a message. A separate request to “translate this sign” also sits in that chat.

Here is the placement:

  1. “Answer briefly” stays in instructions because it is widely useful and rarely changes.
  2. The old shift pattern should leave memory because it was temporary and may now be false.
  3. The renovation becomes a project because it is a distinct continuing area.
  4. The current estimate becomes a dated reference file in that project; the previous version is marked as archived.
  5. The sign translation belongs in a one-off chat.

A partner's dietary restriction presents a boundary case. If it is relevant across many areas and appropriate to store, memory may fit. If it matters only to meal planning, keep it inside that project.

Map your current assistant

Do not start by deleting things in bulk. First record the current state so that each problem has a visible source.

Main service:
Instructions: on/off; about ___ lines; last changed ___
Memory: on/off; about ___ entries; past-chat use: on/off/don't know
Projects: ___; names: ___
Reference files: where and how many: ___
Chats used for more than one month: ___
Temporary mode: use/never use/unavailable
Same fact in more than one place: ___
Wrong layer #1: ___ → now in ___ → belongs in ___
Wrong layer #2: ___
Wrong layer #3: ___

Feature names and availability vary by service, plan, and workspace. Search your service's official help for terms such as “memory,” “instructions,” “projects,” and “temporary chat,” then inspect the actual controls. If no memory list is available, record that limitation instead of guessing what it contains.

Practical assignment

Audit the five layers

Continue to learning

Course outline

  1. An Assistant That Knows You — in 20 Minutes
  2. Five Layers: Where Everything Lives
  3. Memory Under Control
  4. Instructions That Actually Get Followed
  5. Projects: One Area of Life, One Workspace
  6. A Reference File Your Assistant Can Rely On
  7. Specialized Assistants: One Role, One Job
  8. Routines: One Phrase Instead of an Explanation
  9. An Assistant on a Schedule: Regular Check-Ins
  10. Voice and Phone: Capture on the Go
  11. Email, Calendar and Files: Access on a Leash
  12. Sycophancy: When Your Assistant Agrees Too Easily
  13. Big Decisions: Your Assistant Prepares, You Decide
  14. Keep Your Own Head: What Not to Hand Over
  15. When Your Assistant Gets It Wrong: Fix the Layer
  16. Upkeep and Moving: Your Assistant Passport