rem-owner-page git:20261020.117b68dA

Immutable. This exact content never changes and is served at /api/v1/blob/1a759c8760952c62.

---
name: rem-owner-page
description: The owner's work, commitments and next decisions.
---

# Your own page

Write the user's page from their messages. Keep person headings and `Facts`
labels except `How the user writes to them`.

## The lead

Before `Facts`, write 2–4 cited sentences:

- **Start with what they are working on now and why the next step matters.**
  If `owner-work-evidence` shows an explicit reversal, lead with it and cite
  both messages. Newer questions are not a change. Otherwise name a blocker
  or unresolved choice. Replace the generic lead; put the
  latest request in the next step. `recent-projects` ranks, not proves shipping.
  List projects in `Who they are`.
- Add a firm, due-soon commitment or blocker. Put distant invitations and
  unrelated mail in `Open threads`.
- Put contact dates in `Facts` and `Cadence`, not the lead.

## Coding agents are the user's tools, not people

Claude Code and Codex are tools. A session prompt records the user's work and
may inform the lead, `Who they are` or `History`; it does not prove a result.
An agent is never a counterparty in `Open threads`, never `Last contact`, and
never a correspondent in `Cadence`.

## Roles are stated, not collected

- `Role` and `Company` are the user's only when **the user states them about
  themselves** (a signature, "I run …", "as the founder of …"), or **someone
  else states them about the user** ("Aaron, our CTO").
- **A role in a list the user writes about someone else is that person's, not
  the user's.** "Ody: partner at OpenOnion, runs marketing, Airbnb co-host" in
  the user's mail describes Ody. Leave it off this page.
- List stated roles with citations and dates; otherwise `Unknown`.

## The sections

- `Who they are`: the user's work in their own words, and the projects of the
  last weeks, each with what they did and when, from the sessions.
- `Insight`: 2–4 cited bullets connecting projects and commitments to the next
  decision: what must happen first, who waits, or a recurring tradeoff.
  Lead with `Changed:` when a dated reversal is
  evidenced; otherwise `Now:` joins repeated work to a decision or exact
  verification gap. `Changed:` needs an observed choice or result, not a newer
  question; `At stake:` names a firm due-soon commitment or blocker. Compare
  sources when possible and cite the dependency. Summarized requests alone are
  not insight. A coding request proves no shipment or passing test; only
  artifact evidence proves shipping. Work only: never a `[personal]` or
  `[sensitive]` item (a purchase, health, family); those live in `Who they are`.
- `Why they are here`: this is the owner's page; one line, cited to the map.
- `Our relationship`: `Account owner`.
- `History`: completed, dated milestones, newest first (launch, hire, move,
  release, project start/stop). Requests, questions and plans are not history;
  map mail counts go to `Cadence`.
- `Open threads`: mandatory. What the user owes (a reply, a document, a
  payment) and what is owed to them, to whom, since when, from the mail and the
  sessions ("promised the invoice to Tamara on 2026-09-24; not sent"). The user
  owes only what the user agreed to, quoted; someone's unanswered request to
  the user is `<Name> asked the user`, and the user's unanswered request is
  `The user asked <Name>`.
- `How they communicate`: how the user writes (language, length, channel), from
  their own messages.
- `Cadence`, `Uncertainties`: as on a person's page.