Say which writes reach the timeline #26

Merged

tiagoagueda merged 1 commit from 11-readme-timeline into main

2026-11-12 01:25:26 +00:00

tiagoagueda commented

2026-11-11 22:58:49 +00:00

Owner

Closes #11

The README (a table of the five write tools), the instructions shown to the model and the token advice now say what each write leaves: notes and status changes a timeline entry; reminders the token's name on the reminder; cover-letter drafts nothing. Two tests hold the text to the tools.

🤖 Generated with Claude Code

Closes #11 The README (a table of the five write tools), the instructions shown to the model and the token advice now say what each write leaves: notes and status changes a timeline entry; reminders the token's name on the reminder; cover-letter drafts nothing. Two tests hold the text to the tools. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

tiagoagueda added 1 commit

2026-11-11 22:58:49 +00:00

Say which writes reach the timeline, in the README and the instructions

CI / Lint and test (Python 3.12) (pull_request) Successful in 16s

Details

CI / Lint and test (Python 3.14) (pull_request) Successful in 16s

Details

CI / Audit the dependencies (pull_request) Successful in 27s

Details

CI / Lint and test (Python 3.13) (pull_request) Successful in 16s

Details

3f8ef579b2

The README, the package docstring and the instructions the server hands the model all said
that every write lands on the application's timeline with the token's name against it.
In the core (on main, and in 0.5.0) only a note and a status change are timeline entries,
signed with actor_of(). A reminder added or completed through the API is no timeline
entry: it stores the token's name in its own actor field, shown as "via API token ..." in
the agenda and overwritten by the next change. A letter draft is created with no record of
who wrote it at all.

The README now has a table of the five write tools and what each leaves behind, and the
instructions tell the model the same, so it knows that a reminder or a letter it writes is
not something the person can trace afterwards. Two tests hold this: the instructions no
longer promise a timeline entry for every write, and the README's table has exactly one
row per write tool the server offers.

Closes #11

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

tiagoagueda merged commit 632588caad into main

2026-11-12 01:25:26 +00:00

tiagoagueda deleted branch 11-readme-timeline

2026-11-12 01:25:26 +00:00

tiagoagueda referenced this pull request from a commit

2026-11-12 01:25:27 +00:00

Say which writes reach the timeline (#26)