Context

You're going to turn my personal context into a knowledge wiki. It follows Andrej Karpathy's LLM wiki pattern: the raw source files stay untouched, you write and maintain a set of linked markdown pages, and a schema file tells the next session how to keep it up to date.

Two rules hold for the whole job. Don't make up facts about me, and if a source is missing, note the gap. When two sources disagree, keep both claims and say they conflict instead of smoothing it over.

Step 1: Check what I've gathered.
Before you create any files, go through this list with me. For each source, ask whether I uploaded it, connected it, or decided to skip it, and wait for my answers. If I still want a source I haven't gathered, tell me to go get it first. Don't start until I say the set is complete.
1. iMessage, for close relationships: an imessage-export folder with a summary.md inside
2. LinkedIn, for the wider group of people I know: the unzipped data export
3. Files on this computer, for notes, school, and work: files.md
4. Gmail, for day-to-day email: connected
5. Google Calendar, for how my time actually goes: connected
6. Google Drive, for notes and documents: connected
7. A brain dump, for what's never been written down: interview.md

Step 2: Ask where the wiki should live.
It can be a folder on this computer or a folder in Google Drive. Wait for my answer, then create the folder and tell me the path. The raw sources include other people's messages, so keep the folder private.

Step 3: Read what you have.
Start with the files and folders I attached. Then use Gmail, Calendar, and Drive if they're connected. In Drive, read the folders that look like notes, journals, writing, or current work. If you can't tell which ones matter, ask me once and keep going. Don't try to read all of Drive, and don't wait on a source I don't have. If I didn't attach files.md but you can see this computer's files, read Documents, Desktop, and Downloads yourself.

Read text, CSV, and JSON. Skip images, video, and attachments. LinkedIn's Connections.csv usually has a few lines of notes above the real header row, so find the header before you parse it.

Step 4: Build the wiki.
Use this structure, and fill it with real pages based on what you actually found:

context-wiki/
  AGENTS.md
  raw/
    imessage/
    linkedin/
    files/
    gmail/
    calendar/
    drive/
    brain/
  wiki/
    index.md
    overview.md
    log.md
    people/
    preferences/
    work/
    day-to-day/
    sources/

Here's what each part is for:
- raw/ holds the sources as they came in. Copy exports here. For a connected source you can't copy, write a short note saying what you read and when. Never edit anything in raw/ after that.
- wiki/people/ has one page per person who matters. iMessage is the best evidence for close relationships, and LinkedIn is best for the wider network.
- wiki/preferences/ covers likes, dislikes, taste, and values. The brain dump is the main source. Email and calendar can correct it when what I do doesn't match what I said.
- wiki/work/ and wiki/day-to-day/ come mostly from Gmail, Calendar, Drive, and my files. This is the everyday stuff that would never make it into a biography.
- wiki/sources/ has one page per raw source: what it covers, how recent it is, and what it shouldn't be trusted for.
- wiki/overview.md is the big picture, with links. End it with a Gaps section.
- wiki/index.md lists every wiki page with one line each, grouped by folder. Future sessions read this first.
- wiki/log.md only ever gets added to. Start each entry with ## [YYYY-MM-DD] ingest | title so it's easy to search.

Step 5: Write AGENTS.md.
This is the rulebook. Write it so a new agent could keep the wiki up to date without ever seeing this chat. Include these rules:
- raw/ never changes. wiki/ is yours to write. I pick the sources and ask the questions.
- Filenames are kebab-case.md.
- Every wiki page starts with a title and a two-sentence summary, and ends with a Sources section of relative links.
- Link people, preferences, and work pages to each other.
- When sources disagree, keep both and mark the conflict.
- To add a source: read it, update the pages it affects, update index.md, and add an entry to log.md.
- To answer a question: read index.md, open the relevant pages, answer with links, and save a useful answer back into the wiki if I ask you to.
- To check the wiki: look for pages nothing links to, claims that are out of date, missing pages, and conflicts.

Write the pages in plain language. Keep them short and make specific claims, with no biography voice and no filler. Quote me when my exact words matter.

When you're done, show me the folder tree, the path, and five pages I should read first. Then stop.