Reports: TODO/DONE format instead of checkboxes, much broader reportability bar
Format: '** TODO <title>' unread, '** DONE <title>' read -- tick deletes DONE entries at the start of its next run (previously [X]). This only changes the Reports heading's own keyword; :chat: entries and Close diwan session stay checkbox-based, unaffected. Reportability: reversed last turn's narrow 'only real findings' bar. The report is now explicitly meant to be the one place Marc checks for everything new or needing attention -- so triage moves, new dispatches, session closures, and inline answers are reportable again, alongside findings/ambiguities/problems and anywhere a note was left for Marc to read (even one the agent already marked [X] itself -- that's not the same as Marc having seen it). Only two exclusions remain: a run where nothing happened at all, and a bare nudge (no information yet on whether anything came of it). No code changes -- this is PROTOCOL.md/TICK.md/DO.md/DESIGN.md only. Also cleaned up one stale 'did nothing' entry in diwan-dev-notes' diwan.org that violated the rule even under the old wording.
This commit is contained in:
1 parent
43215d6e0a
commit
19e6ae3a59
4 files changed
+18
-18
No files matched your search
@@ -20,7 +20,7 @@ Don't mark your own entries `[X]` — that's Marc acknowledging them. You may ma
|
||||
|
||||
## Reporting
|
||||
|
||||
When you finish a notable piece of work — answered a chat question with real content, completed a chunk of delegated research, did something worth telling Marc about after being resumed/nudged — append one short entry of your own to `diwan.org`'s Reports log, in the format PROTOCOL.md's Reports section describes (a `[ ]` subheading whose title is itself a link back to your own heading, a signed one-or-two-line body). This is the one explicit exception to staying inside your own subtree: you may append a new entry there, but never edit or delete an existing one — that's `tick`'s job only. Don't report every small step, just the things Marc would actually want to know happened without reading your heading in full. Nothing about resuming or being nudged is itself reportable on its own — only report once you've actually done something as a result.
|
||||
When you finish a piece of work — answered a chat question with real content, completed a chunk of delegated research, moved something, left Marc a note he hasn't seen yet, did something worth telling him about after being resumed/nudged — append one short entry of your own to `diwan.org`'s Reports log, in the format PROTOCOL.md's Reports section describes (a `TODO` subheading whose title is itself a link back to your own heading, a signed one-or-two-line body). This is the one explicit exception to staying inside your own subtree: you may append a new entry there, but never edit or delete an existing one — that's `tick`'s job only. The bar is broad — this report is the one place Marc checks for what's new, so err on the side of reporting rather than staying quiet — but it's still per *result*, not per step: don't write five entries narrating your own process, write one once there's something to show. Nothing about resuming or being nudged is itself reportable on its own — only report once you've actually done something as a result.
|
||||
|
||||
## Committing
|
||||
|
||||
|
||||
Reference in new issue
Block a user