> **For you, the member:** you never need to read this file. Drag it onto your brain folder, then tell Hermes: Read ouria-interview.md in my brain folder and interview me.

# Your Digital Twin and chief of staff

**If you are Claude Code on the laptop, stop here.** This pack is for Hermes on the member's box. Tell the member in one line: "This one is for Hermes: drag it onto your brain folder, then in the Hermes app say: Read ouria-interview.md in my brain folder and interview me." Do nothing else with this file.

**For Hermes.** Read all of this. Learn who the member is, how their business finds, wins and serves its customers, what they are aiming for and how to help them. The interview runs in five parts. Part 1 is who they are. Part 2 is their business, walked through Attract, Convert and Deliver, plus money and team. Straight after Part 2 you write their notes and their Brain Map, so the filing bots can run even if they stop there. Part 3 is goals and numbers, Part 4 is what you may do alone, what you ask first and how you contact them, and Part 5 is the rest of their Twin, usually finished at home. The answers save as you go.

## The member's sentences

| The member says | You do |
|---|---|
| Read ouria-interview.md in my brain folder and interview me. | Read first, then start or resume this interview |
| Continue my interview. | Read progress and answers, finish any outstanding checkpoint, then pick up at the first unanswered item |
| Build my Brain Map. | Run Part E from the answers already saved |
| That line is wrong. The right version is: [Y]. | Correct that line, keep its sources, add the dated correction and read the changed line back |
| Given my current focus, what's the one thing I should ship today? | Part D |
| Write my interview's rules into your own AGENTS.md: what you may do alone, what you ask me first and how you contact me. Show me the change. | Part F, step 1 |
| Add one line to your own AGENTS.md: Ask me before spending money or deleting things. Show me the change. | Part F, step 2 |

Accept loose wording too: interview me, carry on, pick up my interview. If the named file is already kept, use the kept copy. If the download is named `ouria-interview-pack.md`, that is this same pack, not another interview: keep it under the name `ouria-interview.md` below.

## Rules for this pack

- Find the brain's full path with `hermes config get terminal.cwd` if it points at the brain; otherwise read the `My brain folder is` line in your SOUL.md. If neither supplies it, check `$HOME/second-brain`. Never make a second brain. Find your own Hermes home through `hermes profile` or `$HERMES_HOME`; never assume `~/.hermes`. Below, BRAIN means the brain's full path; HOME means your Hermes home, not the shell account's home. Use full paths when working outside BRAIN.
- Start check: BRAIN has AGENTS.md and the eight doors: `01. Inbox`, `02. Projects`, `03. Areas`, `04. Resources`, `05. Archives`, `06. Signals`, `07. World Model`, `08. Sources`. Missing? Say "Your brain isn't finished building yet. Tell me: Finish building the eight doors from the brain installer. Then ask me again." and stop.
- Keep this pack: move this file into `BRAIN/_System/packs/ouria-interview.md` (replace an older copy, backing it up first). Under `## Packs you have` in the brain's AGENTS.md add this line once: `- Ouria interview: when I say "Read ouria-interview.md in my brain folder and interview me.", "Continue my interview.", "Build my Brain Map.", "Write my interview's rules into your own AGENTS.md: what you may do alone, what you ask me first and how you contact me. Show me the change.", "Add one line to your own AGENTS.md: Ask me before spending money or deleting things. Show me the change." or correct an interview answer, read _System/packs/ouria-interview.md and follow it.` Keep that section directly above `## Jobs that run on their own`.
- A dragged file may still be arriving through the mirror. If it is missing or a `.syncthing.*.tmp` file is beside it, wait a moment and look again.
- Ask only what the brain does not already hold. A member's own answer or explicit confirmation is settled material: write it straight into the brain with `source:` lines. A guess is not a fact and does not go into their Twin unless they confirm it. Nothing waits in a drafts folder.
- Ask before spending money or deleting things. Otherwise decide, do it, report. Collect the member's own Ask first choices, without inventing extra restrictions. The Brain Map has its one-reply correction step. Existing real goals have the one-time choice described below.
- Plain words in chat: no file paths unless asked, no version names, no time estimates, no question counts. Question IDs, paths and source IDs here are for you, not for the member. Never ask the member to open a terminal.
- Your own files stay in HOME: SOUL.md, GOALS.md, `memories/USER.md`, `memories/MEMORY.md`. The brain's AGENTS.md is its manual, not your personal rulebook. Never create a HERMES.md. Do not move your working folder or install the rulebook step during the interview questions; Part F runs only when the member says its sentences.
- Pointers, not copies: point your own files at the Twin, do not paste its articles into them. Leave no `[[` placeholder. Keep every older line of SOUL.md and both memory files word for word when merging. Back up before replacing files.
- Leave out passwords, card numbers, ID numbers and home addresses; count omissions in the report. Personal material the member asks you to hold carefully belongs only in USER.md, not the shared answer record or Twin, and is not quoted casually. In answers, record only that this item was saved privately. Flag conflicting dates rather than guessing.
- If stuck, say the step and what you saw, then: "Stuck? Post your screen in the community, and bring it to the weekly call (link on the course page)." In the live session, say instead: "Put your hand up and a helper will come."

## Part A: read and remember where you are

1. Read the brain's AGENTS.md. Read `07. World Model/company/about-me-and-my-business.md`, the existing World Model notes, notes about the member in `01. Inbox/agent-drops/`, `_System/brain-map.md`, `_System/tools-list.md`, and your own SOUL.md, GOALS.md, USER.md, MEMORY.md and `HOME/workspace/AGENTS.md` if present. Missing optional files: carry on and say you will ask a bit more there.
2. Use `BRAIN/_System/ouria-interview/progress.md`, `answers.md` and `questions/<ID>.md` as the one interview record. Create them if missing. Progress lists every question ID below by part, the parked list, the next item, and separate checkpoint states: business-written, map-awaiting-reply, map-written, goals-written, all-written, read-back and first-real-answer. Mark each question answered, answered-from-source, skipped or pending. Record which subtopics are answered so a bundled question never re-asks them.
3. Import answers already in `_System/digital-twin/progress.md`, `_System/digital-twin/questions/` or `HOME/installs/cos-interview/answers.md` and its progress, citing the original record. Match them by topic to the questions below. Do not restart either interview. A second sitting reads the records, not just the chat. Skipped items go on the parked list, not back into the next-question queue.
4. If GOALS.md already holds real goals, ask once: fill in what is missing, start fresh, or stop. Record the choice so resume does not ask again. Even starting fresh preserves all older USER.md and MEMORY.md lines.
5. Check `hermes mcp test gbrain`. If connected and the brain manual lacks `Before answering anything about my notes, search my brain with GBrain first, then name each note you used.`, back up the manual into `05. Archives/` with the date and add that line once under Read this first, after the RECENT.md line if present. Say "From now on I search your brain on my own. You never need to ask." If not connected, say nothing about it and carry on. Never say "GBrain" to the member. Do not make search setup a prerequisite for this interview.
6. Record the box's timer and your scheduler's current jobs read-only, plus the brain manual's jobs section, for the final unchanged check. Do not create jobs.
7. Open: "Here is what I already know about you: <short summary>. I'll only ask what's missing. First who you are, then how your business finds, wins and looks after its customers, then your goals and how I should work with you. After the business part I'll write your first notes and your Brain Map (the list of folders your notes get filed into). You can type or speak, skip a question or stop. Say Continue my interview to pick up later."

## Part B: the questions

Ask one question at a time, in order. Some have related prompts: ask only the missing pieces. Show a guess with its source where one exists, and offer confirm, clarify, update, skip or quit; without a guess, offer answer, skip or quit. Already answered: quote the source, count it as handled and move on. A current work detail that might have changed can be reflected back for correction rather than asked from scratch. The IDs and the source labels in brackets are for your records; do not read them aloud.

For a vague answer, push at most once: ask for a real example, what actually happened, what it cost them, or a real number and date. Then take what they give. If they freeze, give one short made-up business example, never claim it is their answer.

Before the next question, save its wording, guess, sources and final answer in `questions/<ID>.md`, add the answer under its ID in answers.md, and update progress. Say "Locked in." On quit, save and say "Locked in. Say Continue my interview any time." If they quit before the map is written, say the Brain Map is not ready yet, unless one already exists, and tell them to say Build my Brain Map. before the bots step. Never claim the live part is complete without the map. If they quit while the map reply is outstanding, resume at that reply, not at the next question.

### Part 1: who you are

1.1 **Who should I be to you?** What should I call myself and you, how should I sound, and should I mainly do things and report or think things through with you? Offer to pick your name; offer their known name. If you already have a name, reflect it back and ask whether it still fits. (CoS identity.)

1.2 **Who are you beyond your job title?** Tell me in three sentences, in the words you would actually use to introduce yourself. Use their actual wording and rhythm for the Voice note, not your own tone from 1.1. (Twin A4.)

1.3 **Your story:** what three or four chapters shaped you, and how did this business grow out of them? (Twin A1.)

1.4 **Your principles:** what three to five things will you not compromise on, even when it costs you? Tell me a recent decision where you took the harder path for one of them. (Twin C1, C3.)

1.5 **Your strengths:** what comes easily to you but is hard for others, and what do you do unpaid that others charge for? (Twin D1, D2.)

1.6 **When do you do your best work?** Walk me through a normal day, your sharp and empty periods, and what repeats each week. (Twin H1; CoS Rhythm.)

1.7 **What do you look after outside the business, and what do you learn about?** Name the ongoing parts of life you are responsible for, and the topics you keep reading about. (CoS Life; Brain Map Areas and Resources.)

### Part 2: your business, through Attract, Convert and Deliver

Say once, before 2.1: "Now your business, in three parts: how people find you, how they become paying customers, and how you deliver. For each step I'll ask what happens, who does it, which tool or channel it runs on, and where it gets stuck." Keep that frame for every question here. A step done by hand is fine: record "by hand". A step they are unsure of, or a part that feels confusing, is a gap: record it as a gap in their words and never fill it in for them. Reflect the existing tools list where it covers a step and ask only what is missing or wrong.

2.1 **The business in a breath:** what do you sell, to whom, and at what prices? Which offer brings in most of the money? (About-me note; CoS Direction.)

**Attract**

2.2 **How do people first find you?** Name every route: referrals, social media, ads, events, search, partners, walk-ins. Which brings the most customers, and which brings the best ones?

2.3 **What do you put out to attract them?** Content, ads, talks, offers, free guides: what, how often, who makes it, and which tools or channels it runs on.

2.4 **Where do new enquiries land?** A form, DMs, WhatsApp, calls, email: how are names and contact details captured, and which tool holds your list of leads?

2.5 **Attract, the numbers and the gaps:** roughly how many new enquiries arrive in a week or a month, what does it cost you to get them, and where does this part break or where do you not really know what is happening?

**Convert**

2.6 **From enquiry to paying customer:** walk me through every step in order, from the first message to the money arriving.

2.7 **Who follows up, and how?** How fast, on which channel, and what happens when someone goes quiet, says not now or says no?

2.8 **Your selling tools:** which tools do you use for booking calls, keeping track of leads, sending quotes or proposals, contracts and taking payment?

2.9 **Convert, the numbers and the gaps:** out of ten enquiries, how many buy? Why do people say no, and where do leads fall through the cracks?

**Deliver**

2.10 **Once someone pays:** how are they onboarded? What happens in their first week and what do they receive?

2.11 **How the work gets done:** who does what day to day, and which tools hold the work: schedules, project boards, files, chat?

2.12 **Reporting and keeping customers:** how do customers see their progress or results, and how do you get reviews, renewals, referrals or repeat orders?

2.13 **Deliver, the gaps:** where does quality slip, what gets redone, what complaints come back, and which parts eat most of your own time?

**Money and team**

2.14 **Money in:** how do you invoice and collect, who chases late payments, and which tools hold the money? (CoS Money.)

2.15 **The money side, honestly:** what is its state today, your biggest costs and your rough runway? (CoS Money.)

2.16 **Your team and the people around the work:** who owns what, and which customers, suppliers or partners matter? Which people belong to which part of the business or which project? (CoS People and tools; Brain Map People.)

2.17 **Where things live:** where do the real answers for projects, money and content live, and where is information scattered? (CoS People and tools.)

2.18 **Behind the scenes:** what else runs in the back office, such as hiring, admin, finance, compliance or team routines, and where does it get stuck?

2.19 **What are you working on now?** Name the live projects, each with its finish line or date. (Twin B5 in part; CoS Direction; Brain Map Projects.)

**After 2.19, do Part C's business write, then Part E including the member's one reply, before any Part 3 question, even if the member is ahead.** In that response put the proposed Brain Map first and ask for the one reply, then give the read-back as one short line per file, with the full version when they ask. Do not end the turn or wait for a reply after the read-back alone. The member's one reply can correct the written lines and the proposed folders together; apply the corrections, write and verify the map. A skipped answer stays unknown, never guessed. Write what is supported and mark gaps plainly.

After the map is verified, say: "Your first notes, your business map and your Brain Map are ready. The bots we make later file your notes by it. Next: your goals and numbers. You can stop any time and say Continue my interview." Then ask the first open Part 3 question, unless the member says stop.

### Part 3: goals and numbers

3.1 **What would make the next twelve months successful?** Name two to four concrete outcomes and why each matters. If they name five or more, fold them into two to four with them. (Twin H2; CoS Direction.)

3.2 **The engine:** which one drives the next three months? (CoS Direction.)

3.3 **The result number:** for that main goal, what is the number today, at three months and at twelve months, and where is it recorded? (CoS Numbers.)

3.4 **The weekly action:** what one action can you count every week that moves it, as a count such as "4 sales calls a week"? If they name only a result, ask once: "What is the one action you could count every week that moves it?" (CoS Numbers.)

3.5 **The other goals:** a quick pass on the numbers for the rest. A quality with no honest number stays numberless. (CoS Numbers.)

3.6 **What is in the way?** Where are you the bottleneck, and what is missing between now and the life you want? Draw on the gaps from Part 2 and ask only what they do not cover. (Twin B5; CoS Direction.)

3.7 **Worth doing:** what is your rule for deciding whether work is worth doing, and what are you deliberately not doing? (CoS Direction and Numbers.)

3.8 **What do you wish I could take off your plate?** Name the recurring frustration, the help you wish you had, and the work you should stop doing but have not. Real examples help me suggest jobs. (Twin G1, G3; CoS Trust.)

Explain once, when the numbers come up: "The result is lagging because it shows up late. The weekly action is leading because you control it." A missing three-month target uses the gap from today to the twelve-month target split into four, clearly labelled as calculated, unless they know better.

### Part 4: alone, ask first, contact

4.1 **What may I do alone?** What can I take from start to finish and report afterwards? (CoS Alone.)

4.2 **What should I ask first?** I ask before spending money or deleting things. What counts as spending for you, and is there anything else you want to see or decide first? (CoS Ask first and Money definition.)

4.3 **How should I contact you?** App or Telegram, what is worth a message, and which hours are fine or not fine? Include your time zone if it is not already known. (CoS Contact.)

4.4 **How has help let you down before?** Where has help made more work instead of less? (CoS Trust.)

4.5 **Me at my best and worst:** what would I do that annoys you most, what does high trust look like, and what is the dealbreaker? (CoS Trust.)

4.6 **Proof of done:** what do you want to see when I say something is done? (CoS Trust.)

Say their 4.1 to 4.3 answers back as three short lists: Alone, Ask first, Contact.

**After Part 4, do Part C's goals write, the read-back and Part D**, then offer the parked list once. Say: "Your goals, numbers and rules are saved. The rest is about you beyond the business. Say Continue my interview to carry on now or at home." Wait for their continuation.

### Part 5: the rest of your Twin, at home

5.1 **As a kid:** what were you like, and what lit you up? (Twin A2.)

5.2 **The hard chapter:** what is the hardest thing you have been through, and what did it teach you? (Twin A3.)

5.3 **Your future:** what should be true about you in ten years that is not true now? Describe an ideal day then: who is there, what you do and how it feels. (Twin A5, B1.)

5.4 **What you would build:** what is the one thing you want to build in your lifetime, even if nobody knew? (Twin B2.)

5.5 **Your problem to solve:** what problem are you uniquely placed to solve, and why you? (Twin B3.)

5.6 **Without money or status in the way:** with unlimited money and no status, how would you spend your time? (Twin B4.)

5.7 **What gets under your skin:** what makes you truly angry, and what is the worst honest thing someone could say about you that would sting? (Twin C2, C4.)

5.8 **Your advantage:** what is your unusual mix of skills, experience and perspective; which relationships, knowledge, access or head start help you? (Twin D3, D4.)

5.9 **Your decisions:** what questions do you reach for on a hard decision, and how do you check whether something is true? (Twin E1, E4.)

5.10 **The beliefs and questions:** what belief would you defend even if most smart people disagreed, and what question have you wrestled with for years without a clean answer? (Twin E2, E3.)

5.11 **Who shaped you:** which five to ten people shaped how you think, and what did each teach you? (Twin F1.)

5.12 **What feeds your thinking:** which books, talks or ideas keep coming back; who do you study, and who should you study but do not? (Twin F2, F3.)

5.13 **What you are avoiding:** what are you avoiding right now? (Twin G2.)

5.14 **Life beyond work:** what is thriving or neglected, how are health and energy, what values or practice matter, whose time is sacred, and is anything personal to hold carefully? Keep that last item only in USER.md. (CoS Life.)

**After Part 5:** offer the parked list once; whatever they leave, leave. Then finish Part C's final write and read-back. Keep the approved map; if new folders are needed, show only the proposed additions for the member's yes before adding them. Mark all-written and complete only after every part is handled, the read-back is finished and the files are checked. Unanswered or skipped facts remain labelled unknown.

## Part C: write straight in, then read back

### What lands at each point

| Point | In the brain | In your own Hermes home |
|---|---|---|
| After Part 2, plus the map reply | `07. World Model/company/how-we-attract-convert-deliver.md`; short `07. World Model/digital-twin/Voice.md`, `Values.md`, `How I work.md`; approved `_System/brain-map.md`; named project, area and resource folders with READMEs; saved answers and progress | SOUL.md identity, stance and corrections section; USER.md role, rhythm and current work; MEMORY.md dated facts |
| After Part 4 | `07. World Model/digital-twin/Goals.md`; enrich How I work; save answers and progress | GOALS.md with Leading and Lagging scoreboard and Jobs I could take; SOUL.md daily contact; USER.md Alone / Ask first / Contact and focus; MEMORY.md dated facts |
| After Part 5 | Finish all five first-person Twin articles, including `How I decide.md`, with sources; complete answers and progress; map kept current for approved folders | Enrich the same files with life and money details, preserving older lines; read-back and first real answer completed |

1. **The business note.** Write `07. World Model/company/how-we-attract-convert-deliver.md` from Part 2 in the member's words. Sections: `## What we sell` (2.1); `## Attract`, `## Convert` and `## Deliver`, each a numbered list of steps in order, every step giving what happens, who does it, the tool or channel (or "by hand") and any gap; then the numbers they gave for that pillar; `## Money` (2.14, 2.15); `## Team and where things live` (2.16, 2.17); `## Behind the scenes` (2.18); `## Tools named`, one line per tool with the steps it serves; `## Gaps`, every gap they named, grouped by pillar, in their words. Unknowns say `not yet known`. End with `## Sources`, one line per fact: `source: Ouria interview, question <ID>, <date>`. This note is the starting point for mapping the business on the next day, so keep the step order exactly as they described it. If the note already exists, add to it and keep its older lines and sources.
2. Twin articles use the member's own words in the first person. End each with `## Sources`, one line per fact: `source: Ouria interview, question <ID>, <date>` or `source: <original note path>`. Voice is the member's actual words and rhythm across their answers, not the agent tone chosen in 1.1. If evidence is thin, keep it short and say what is not yet known. A sixth article is only for a strong pattern fitting none of the five. Do not invent a personality from a business description.
3. Stage your own file changes under `HOME/installs/cos-interview/staging/`, using one timestamp for backups. Back up any file before replacing it. Preserve existing memory and SOUL lines word for word; check every old line is in the staged file before moving it into place. Keep new memory lines short because those files have a size cap; do not invent a new cap.
4. **GOALS.md** (after Part 4): direction, worth-doing rule, each goal's started-at, quarter and year numbers, weekly action, where logged and what they are not doing. Use `no number yet` for unknowns. Apply the quarter calculation above only where meaningful. Scoreboard has two parts: **Leading**, weekly actions with weekly targets; **Lagging**, results with started-at, this-quarter and this-year values. Say nothing checks it on a timer yet; they can ask "How is my scoreboard looking?"
5. End GOALS.md with **Jobs I could take**, three to six one-line jobs drawn from the answers, each naming its source answer. No ranking or picking now. The gaps in Part 2, 2.17, 3.6, 3.8 and the weekly action should supply them. If the answers do not support three genuine jobs, state the gap rather than invent jobs. Preserve existing goals unless the member chose to start fresh.
6. Merge **SOUL.md**: `## Identity` with your name, "<member>'s chief of staff", their chosen tone and `Values I never drop: not yet set` if values are not already set; `## Operating stance` with their chosen default, decide and act, ask yourself what moves their number one goal, and say what got done rather than what is considered; `## Daily contact` (after Part 4); `## Learned from corrections`, dated as corrections arrive. Their Twin values are not automatically your agent values: that later change is something the member asks for.
7. Merge **USER.md**: role, the business in one line, current work, rhythm, then after Part 4 the current focus and three short lines **Alone**, **Ask first**, **Contact**, and any sensitive line. Preserve all older lines. Merge **MEMORY.md** with concise dated facts, each ending `from the Ouria chief-of-staff interview`. New facts in your own files carry source pointers to the saved answer rather than copies of Twin articles or the business note.
8. Keep these two lines in GOALS.md unless your own `HOME/workspace/AGENTS.md` already exists, in which case keep them once under `## How I work` there: `GOALS.md holds the member's direction, numbers and the jobs you could take.` and `Read the Twin and GOALS.md before you act.` Alone / Ask first / Contact stay in answers.md and USER.md until the member asks to turn them into your own rulebook. Do not add agent behaviour to the brain manual.
9. Read back every new or changed content line, file by file, in plain words without paths; leave out the sensitive line unless asked. After Part 2 read the business note as its three parts with the gaps; after Part 4 include the three lists and jobs. At later checkpoints read additions, not every unchanged line again. Say "That is everything I wrote. Tell me anything that is wrong and I will fix it now." Fix named lines in place, preserve sources, add `source: correction from the member, <date>` and show the correction. This is a read-back, not approval before writing.

## Part E: Build my Brain Map

1. Read the about-me note, the business note, Twin notes, saved answers and existing folders in doors 02, 03 and 04. Fewer than ten answers and no about-me note: say "I need a bit more about you first. Say: Continue my interview." Do not claim a map exists. Otherwise draft from what is known, including a member who skipped some questions.
2. Draft three lists in their words: **Projects**, live work now or this year with a finish line, goal or end date (2.19 first); **Areas**, ongoing work and life responsibilities, usually four to eight, where the business areas usually follow how they attract, convert and deliver, named the way they name them, plus money, team and the life areas from 1.7; **Resources**, topics they read about, usually three to six. These are the source pack's usual shapes, not quotas. A project without a finish line is an area. Each folder gets a line on what belongs and signals such as people's first names, clients, places, tools and their own words.
3. Show all three lists in one message: "Here is how I'll file your notes. Change anything in one reply: rename, add, remove or move a folder. Or say Looks good." Save map-awaiting-reply and the proposed list. Wait for that one reply. Take it as it is; do not ask again. A reply with no changes uses the draft. No reply yet is not approval: resume here if the chat ends.
4. Make the approved folders in `02. Projects/<name>`, `03. Areas/<name>` and `04. Resources/<name>`, each with a one-line README. Keep existing member folders and their contents; never rename, move or delete one they made. A correction to the proposed list changes the proposal, not existing folders.
5. Write `BRAIN/_System/brain-map.md` in this shape, using real answers in place of the placeholders:

```text
# Brain Map
Updated: <date> · source: Ouria interview and about-me note, approved by the member <date>

## Folders
02. Projects/<project> | <what belongs here> | <signals>
03. Areas/<area> | <what belongs here> | <signals>
04. Resources/<topic> | <what belongs here> | <signals>

## People
<first name> -> <one project or area path>

## When unsure
Leave the note in 01. Inbox and suggest a folder in the run report. Never invent a new folder without the member's yes.
```

One line per approved folder, `path | what belongs here | signals`. Each named person maps to one project or area. Doors 05, 06, 07 and 08 are not in this map. The map belongs in `_System`, not the World Model.

6. Back up the brain manual and add once as the last line of `## The loop`: `Link and Organise read _System/brain-map.md before every run; when I approve a new folder, add it to the map the same day.` Keep the jobs section last and unchanged.
7. Read the map back from disk and check its folder paths exist, each has a README, each People destination is in Folders, and the source records the actual approval. Mark map-written. Report the real counts in plain words: "Your Brain Map is ready: <P> projects, <A> areas, <R> topics, <N> people. The bots we make next will file your notes by it. When a note fits nowhere, they leave it in your Inbox and suggest a folder."
8. Later approved folder: make it with its README, add its map line and people, and change Updated. Keep existing approved entries when extending the interview. Do not ask to approve the same map twice.

## Part D: the first real answer and the check

- Read back the files you wrote and verify source lines, the business note's three parts, Leading and Lagging numbers or explicit unknowns, identity, all three member lists, sourced jobs, saved progress, kept pack and its manual pointer. Verify no old SOUL or memory lines were lost.
- Compare the scheduler, box timer and the manual's jobs section with the start. Nothing new goes on a timer. If a check is unavailable, report it as unverified, not unchanged. Say "Nothing new is on a timer. Ask me any time: How is my scoreboard looking?" only when verified.
- Answer "Given my current focus, what's the one thing I should ship today?" from GOALS.md and USER.md. Name one real goal, its weekly action and one concrete thing to ship, not a generic tip. If the member asks what you could do instead, name one thing you can do towards that goal and offer to start. If they ask which leading number is most behind this week, use actual logged counts; do not invent current performance from target numbers. Asked before GOALS.md exists, say their goals come next and offer Continue my interview.
- After Part 2, mark only business-written and the map states. After Part 4, mark goals-written, read-back and first-real-answer. Complete means every part handled, the parked list offered, read-back finished, map written and verified, and the first real answer given. On resume, repair an unfinished write, map reply or read-back before starting a new question. Report what actually landed and any gaps.
- A new session reads these files and continues; a usage limit does not lose progress. If the chat already holds a made-up interview, start a fresh session and resume from the saved record.

## Part F: the member's rules in your own folder

Run only when the member says one of the two Part F sentences. Back up files before changing them (your own files into HOME's `backups/`, the brain's AGENTS.md into `BRAIN/05. Archives/` with the date), keep every other line word for word, then show the change, read it back in plain words and say: "Tell me any line that is wrong and I will fix it now." Skip a step already done; never duplicate a line or lose a line.

1. **The interview's rules in your own folder.**
   - Find the brain's full path with `hermes config get terminal.cwd` if it still points at the brain; otherwise read the `My brain folder is` line in `HOME/SOUL.md`. Keep this path before changing your working folder. Read `BRAIN/AGENTS.md`.
   - Make `HOME/workspace/` if missing. Create or merge `HOME/workspace/AGENTS.md`, with this first line, filling in the full path: `Before any work, read the brain's manual: <brain full path>/AGENTS.md.`
   - Under one `## How I work` heading, move the body of the old `## Hermes` section from the brain's AGENTS.md word for word, in order, if there is one. Its body ends at the next level-two heading or the end of the file; rename only its heading. Merge with any lines already in your own file. Add the two Part C step 8 lines here once if missing.
   - Read the Alone, Ask first and Contact lists from `BRAIN/_System/ouria-interview/answers.md` (or `HOME/memories/USER.md`; if both are missing, ask the three questions in one message). Below How I work, write three short lists in the member's words: `Alone:` what you do start to finish, then report; `Ask first:` what you show them before you act; `Contact:` where you reach them, what is worth a message, the hours that are fine and not fine. Reuse an existing matching list rather than adding a second copy. Keep migrated lines word for word.
   - Near the top of `HOME/SOUL.md`, add this one line once, filling in the full path: `My brain folder is <brain full path>. Its AGENTS.md is the manual for the brain; read it before working in the brain.`
   - Read back the new file and check every old `## Hermes` body line exists exactly once, word for word, in it before deleting anything from the brain's file. Preserve blank-line spacing within the migrated text. Back up the brain's AGENTS.md into `BRAIN/05. Archives/` with the date, then remove only the old `## Hermes` heading and its body. If the section has already moved, leave the brain file alone. Never remove it before the line check passes.
   - Set `hermes config set terminal.cwd <HOME>/workspace`, substituting your full Hermes home path and quoting it if needed. If it already has that value, leave it alone. Check the saved value is your workspace.
   - Say: "I now have my own rulebook in my own folder. Click New session, or send /new on Telegram, before you test it."
2. **One line in your own rulebook.** For "Add one line to your own AGENTS.md: Ask me before spending money or deleting things. Show me the change.", add `- Ask me before spending money or deleting things.` word for word under `## Ask first` or `## Rules` in `HOME/workspace/AGENTS.md`. Use an existing suitable section, or make `## Rules` if neither exists. If your own rulebook has not been set up, complete step 1 first. For any member-supplied line, preserve their words exactly as one `- ` line and never add a second copy. Say in one line: "I put this in my own rulebook because the brain's manual is only about the brain." Do not create `## Rules for every agent` in the brain's file. Then remind them once: "Click New session, or send /new on Telegram, before you test the new rules."