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
+5
-5
@@ -71,19 +71,19 @@ diwan's own operational file, at the root of the content repo — not a place fo
|
||||
|
||||
### Reports
|
||||
|
||||
Only things containing *actual information the user would want to know* — a finding, a decision made on their behalf, an ambiguity flagged, a problem hit — get a short subheading under the top-level "Reports" heading in `diwan.org`. Routine mechanical steps that were always going to happen and say nothing interesting on their own — "dispatched a session", "nudged an idle session", "nothing needed triaging this run", "closed a session Marc asked to close" — are **not** reportable; skip the entry entirely rather than writing one just to have something to show. It is normal and expected for a tick run to add zero new Reports entries. When something *is* reportable, keep it to its own short subheading, not one giant paragraph per run: this is what keeps each entry short and the whole log skimmable with everything collapsed. **Whoever actually did the thing writes the entry** — `diwan tick` reports its own actions (triage moves, inline answers, promotions, new dispatches), and a `diwan do` session reports its *own* progress once it has something worth telling the user, not before. In particular: a tick merely nudging an idle active session (see the `:session:` section above) is not itself reportable — tick has no idea yet whether anything came of it, so it stays silent; if the nudge leads the session to actually do something, that session writes the entry once it has.
|
||||
This is the one place the user checks for what's new — a shortcut to everything that needs their attention, not just a highlights reel — so the bar for getting a short subheading under the top-level "Reports" heading in `diwan.org` is deliberately broad: items moved (triage), a new session dispatched, a session closed, an inline answer, a finding, a flagged ambiguity, a problem hit, or anywhere a note was left for the user to read (even one already marked `[X]`/acted-on by whoever wrote it — that means *they've* acted on it, not that the user has seen it yet). The only things that don't get an entry: a run where genuinely nothing happened at all, and a bare nudge to an idle session (not because it's unimportant, but because whoever sent it has no idea yet whether anything came of it — see the `:session:` section above; if the nudge leads to real work, that work gets its own entry once there's something to report). Keep each entry to its own short subheading, not one giant paragraph per run: this is what keeps the whole log skimmable with everything collapsed. **Whoever actually did the thing writes the entry** — `diwan tick` reports its own actions, and a `diwan do` session reports its own progress once it has something to tell the user, not before.
|
||||
|
||||
Format: a `[ ]`/`[X]` checkbox right in the subheading title (same pattern as `Close diwan session`), a short title that *is itself the link* to the one heading the entry is most about (fuzzy heading link, or `id:` link for a note file with an `:ID:` drawer — just plain text with no link if there's no single heading to point at), and a signed one-or-two-line body, no more. No `:LINK:` property, no properties drawer at all — any further links belong inline in the body text:
|
||||
Format: a `TODO`/`DONE` keyword on the subheading itself, a short title that *is itself the link* to the one heading the entry is most about (fuzzy heading link, or `id:` link for a note file with an `:ID:` drawer — just plain text with no link if there's no single heading to point at), and a signed one-or-two-line body, no more. No `:LINK:` property, no properties drawer at all — any further links belong inline in the body text:
|
||||
|
||||
```org
|
||||
* Reports
|
||||
** [ ] [[file:personal.org::*Plan the kitchen redecoration][Kitchen redecoration: flagged a budget conflict]]
|
||||
** TODO [[file:personal.org::*Plan the kitchen redecoration][Kitchen redecoration: flagged a budget conflict]]
|
||||
[diwan 2026-11-08] The heading asks for a 3000€ budget but its linked Pinterest board is all 8000€+ kitchens — asked which one is right in the heading's own :chat: before researching further.
|
||||
** [X] Archived personal.org's Tasques backlog
|
||||
** DONE Archived personal.org's Tasques backlog
|
||||
[diwan 2026-11-07] 45 DONE tasks moved into archive/archive.org, oldest from 2023 — personal.org's active list was getting hard to scan.
|
||||
```
|
||||
|
||||
Unread = `[ ]`, read = `[X]`, same semantics as `:chat:` — the user checks an entry off once they've seen it. Once an entry is `[X]`, the *next* `diwan tick` deletes the whole subheading, not just the checkbox — this is a disposable log, not a record, and only `tick` ever deletes from it (a `do` session only ever appends its own new entries, never touches an existing one). Questions for the user still go in the relevant heading's own `:chat:`, not here — a report entry may link there, but the report itself is one-way, no back-and-forth expected.
|
||||
Unread = `TODO`, read = `DONE` — the user marks an entry `DONE` once they've seen it. Once an entry is `DONE`, the *next* `diwan tick` deletes the whole subheading, not just the keyword — this is a disposable log, not a record, and only `tick` ever deletes from it (a `do` session only ever appends its own new entries, never touches an existing one). Questions for the user still go in the relevant heading's own `:chat:`, not here — a report entry may link there, but the report itself is one-way, no back-and-forth expected.
|
||||
|
||||
### Tasks
|
||||
|
||||
|
||||
Reference in new issue
Block a user