pastilhasandClaude Opus 5
10fe3ffe65
Findings were being relayed through the owner by hand, from memory, at the end of long sessions. A file survives a context window and carries its reasoning; a message does not. The untracked COMMS/ at the workspace root stays what it is — state about one machine at one moment. This one is in the repo because any clone should carry it. First handoff covers what I would otherwise have asked the owner to pass on: the bind-mount container test I could not run here and how to retrofit green, the setup-dockers.sh PG18 layout left deliberately alone, the terminal replay bug and the deprovision/uid-reuse hole with a proposed fix, the shared-home question I cannot answer without the passwd and users rows, and the four things most likely to surprise a reader — bootstrap-only default grants, chat grantable but refused, Bun.spawn ignoring uid, and members never getting the owner's anthropic proxy. The README states the convention: dated files, verified separated from assumed, name lines, reply in a new file rather than editing someone else's, and delete a handoff when it is spent. Durable reasoning goes in docs/ or next to the code — this directory is for coordination, not for the record. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
28 lines
1.6 KiB
Markdown
28 lines
1.6 KiB
Markdown
# COMMS/sidecar-app-store
|
|
|
|
A tracked channel between the agents working on the sidecar app store and per-user Linux accounts.
|
|
|
|
## Why it is in the repo
|
|
|
|
Because the alternative was the owner relaying findings between us by hand, from memory, at the end of long
|
|
sessions. A file survives a context window; a message in a chat does not, and neither does the reasoning
|
|
behind it. The untracked `COMMS/` at the workspace root is for state about one machine at one moment. This
|
|
one is for things any clone should carry.
|
|
|
|
## How to use it
|
|
|
|
- **One file per handoff**, named `YYYY-MM-DD-<subject>.md`. Dated, because "which of these is current" is the
|
|
first question a reader has.
|
|
- **Write what you verified and what you assumed**, separately and explicitly. A handoff that reads as
|
|
confident about something untested is worse than no handoff — the reader will build on it.
|
|
- **Name files and lines.** `os-user.ts:362` costs nothing to write and saves the reader a search.
|
|
- **Reply in a new file rather than editing someone else's.** An edited handoff loses the record of what was
|
|
believed when a decision was made, which is usually the thing that explains the decision.
|
|
- **Delete a handoff when it is spent**, the way `platform/CLAUDE.md` says to delete finished checklists.
|
|
Something still open belongs here; something done belongs in a commit message or a doc.
|
|
|
|
## Where the durable reasoning lives instead
|
|
|
|
Handoffs are for coordination — what is broken, what is unproven, what needs deciding. Anything that will
|
|
still be true in a month belongs in `docs/per-user-linux-accounts.md` or next to the code, not here.
|