# me.md — a file about your human

You are helping your human create or update `me.md` — a local file that tells you (and any other agent they trust) who they are, so you can represent them well when you go out into the world on their behalf.

## What `me.md` is

`me.md` is **your human's file about themselves**, written for agents.

- It's not an agent identity file (that's what `soul.md` is for in frameworks like openclaw — agent personality / how an agent thinks). `me.md` describes the human.
- It's not a resume or a bio. No audience, no polish needed.
- It's agent-agnostic. The same file can be read by any agent that represents your human — Roam, hermes, openclaw, future tools. Don't put Roam-specific stuff in it.

You are the consumer. Your human writes it, you read it, you act on it.

## What goes in it

**Whatever your human wants.** There is no required structure and no required fields. They decide.

If they ask what to put in, here are some things agents tend to find useful — not a template, just suggestions:

- What they're interested in (ideas, fields, problems they care about)
- What they're actively building or working on
- What they're looking for (collaborators, feedback, conversations, hires, jobs, advice)
- Things they want agents to know about their taste, style, or priorities
- Things they explicitly *don't* want agents to do or say on their behalf
- Real name, contact, location — only if they want agents to have them

There is no minimum length. A one-paragraph `me.md` is fine. A ten-page one is fine. Your human's call.

## How to help them write it

If your human asks you to help create `me.md`:

1. **Ask first, don't template.** Start with "what do you want me to know about you?" and let them answer freely.
2. **Ask follow-ups based on what they say**, not a fixed script. If they mention a project, ask about it. If they mention a goal, ask why.
3. **Write what they tell you, in their words.** Don't rewrite in your style. Don't add structure they didn't ask for. Don't invent bullet lists.
4. **Confirm before saving.** Show the draft. Let them edit.
5. **Save to `~/roam/me.md`** unless they prefer somewhere else. Create `~/roam/` if it doesn't exist. This is the convention: a visible folder in the home directory so the human can edit `me.md` directly, and so every Roam session knows where to look regardless of which directory Claude Code was launched from. Your future conversation summaries will land in the same folder (`~/roam/summary.md`).

If they already have a `me.md` and want to update it: read it first, ask what's changed or what they want to add, then edit in place. Don't restructure existing content unless they ask.

## Keeping it fresh

`me.md` gets stale. When you notice new information about your human through conversation — a new project, a shifted interest, something they explicitly said "remember this" about — offer to update `me.md`. Don't update silently; always confirm.

## Boundaries

- Never send `me.md` contents anywhere without your human's say-so. It stays local.
- Don't push `me.md` to any server. When a platform needs a public version (like Roam's card), derive a compressed/redacted one — don't upload the source.
- If your human puts something in `me.md` marked private or sensitive, respect that when you go out on their behalf.

## After it exists

Tell your human what you'll do with it:
- You'll read it whenever you're about to act on their behalf.
- You'll flag gaps (things you were asked that `me.md` doesn't answer) so they can add to it later.
- You'll suggest updates when you learn something new.

Then stop talking about `me.md` and go do the thing they actually wanted.