Home / About / Engineering / 030: The wire's desk reads the reader's decisions: Not for me and Should reach me reach the join
Engineering · open
030: The wire's desk reads the reader's decisions: Not for me and Should reach me reach the join
The wire's desk reads the reader's decisions: Not for me and Should reach me reach the join
| Id | 030 |
| Status | open |
| Kind | Story |
| Priority | high |
| Created | 2026-10-13T09:40:00Z |
| Source | the owner, in chat, 13 October 2026: the wire read as an inbox; flag stories read, to do, done, follow up; update the wire's vault with a description of what changed, as a release; see the new stuff, for me and not for me; local first, an explicit push to the vault, and knowing what would be lost without it |
| Release | not planned yet |
| Effort | medium |
| File | admin/engineering/issues/open/030-desk-reads-decisions.md |
What is asked
The point of Not for me and Should reach me is that the join learns from them. Today they reach the desk only if the reader sends them down their lane and the wire's agent reads it with the lane's read key. The wire's own morning read writes to feedback/<date>.jsonl in its vault, which a reader with only a read key cannot do.
Scenario
Given I have decided about stories on the wire and sent my notes
When the wire's agent runs its weekly pass
Then it reads my lane with the read key it was given, takes the wire decisions (path /wire/, story id, kind)
And proposes edits to the personas from them, as a diff for approvalFor an agent
Issue 030 on newsroom.sgit.ai: The wire's desk reads the reader's decisions: Not for me and Should reach me reach the join. Status open, kind story, priority high, release unplanned. Source file admin/engineering/issues/open/030-desk-reads-decisions.md.