git:20261002.e450aae to git:20261002.f8be35e

27 added, 27 removed. Audit A to A.

---

name: rem-owner-page

- description: How the notebook owner's own page differs from a person's page — who the user is and what they are working on now, their roles only as stated, and what they owe and are owed. Composed after rem-page-person only when `co rem investigate me` writes the owner's page.

+ description: The owner's work, commitments and next decisions.

---

# Your own page

- Write the user's own page from what they sent and typed. Keep the person

- headings and `Facts` labels except `How the user writes to them`.

+ This page is the user's, written for the user: "who am I, and what am I doing

+ now", from what they sent and typed. It keeps the person page's headings and

+ `Facts` labels, except `How the user writes to them`, which this page does not

+ have: leave it out.

## The lead

Under the title, before `Facts`, 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 original messages. Newer questions are not a change. Otherwise name a

- blocker or unresolved choice. Replace the generic quick-pass lead; put the

- latest request in the next step. `recent-projects` ranks, not proves shipping.

- List projects in `Who they are`.

- - Add only a firm, due-soon commitment or one blocking that work. Distant

- optional invitations and unrelated mail belong in `Open threads`.

- - The person-page `Last contact:` lead rule does not apply here; contact dates

- stay in `Facts` and `Cadence`.

+ - **Who the user is and what they are working on now.** From the coding

+ sessions: the projects they worked in and what they were doing there, dated

+ ("since 2026-09-20 building the reader for co rem; 2026-09-28 fixing the

+ Outlook import [4][7]"). Mail says who they work with; sessions say what they

+ are doing. The `recent-projects` item lists the projects of the last four

+ weeks with their dates: name each of the busiest there, dated, here and in

+ `Who they are`.

+ - What is open: the threads the user owes, and the ones owed to them.

+ - `Last contact:` is the newest message they sent to a person, with its channel.

## 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`.

+ Claude Code, Codex and any other coding agent in the sessions are tools the

+ user works with. A session prompt is the user's own work: what they asked for

+ is what they were doing ("2026-09-29 asked for a message-volume check on co

+ rem [5]"), and it goes in the lead, `Who they are` or `History`. An agent is

+ never a counterparty in `Open threads` (it owes the user nothing, and the user

+ owes it nothing), 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.

- - Several stated roles → all of them, each cited and dated. None stated →

- `Unknown`.

+ - 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. 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. A coding request proves no shipment or passing test.

+ - `Insight`: connect projects and commitments to the next decision: what must

+ happen first, who waits, or a recurring tradeoff. Summarized requests alone

+ are not insight; only artifact evidence proves shipping. Cite the dependency.

- `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`.

+ - `History`: dated events, newest first (a launch, a hire, a move, a release,

+ a project started or stopped). The map's mail counts are not history: move

+ them 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").

- `How they communicate`: how the user writes (language, length, channel), from

their own messages.

- `Cadence`, `Uncertainties`: as on a person's page.