Reports: only write entries with real information; tick: actually retire closed sessions
Reports no longer get an entry for routine mechanical steps (a plain dispatch, a session closure Marc already asked for, a nudge, a pass with nothing to triage) -- only for actual findings/decisions/problems. Zero new entries in a tick run is now the normal case; PROTOCOL.md's worked example replaced with entries that carry real information instead of 'dispatched X'/'triaged N items' noise. TICK.md step 3: a session whose Close diwan session is checked off now gets genuinely torn down by the tick agent -- herdr tab close on its DIWAN_ID's tab, :session: tag stripped from the heading, DIWAN_ID property kept as a historical record. Resolves the 'retired-session teardown' known gap from DESIGN.md (previously only reported, never actually closed). Not yet verified against a real live tick run.
This commit is contained in:
1 parent
c09f2a1a11
commit
c7859400a1
3 files changed
+17
-15
No files matched your search
+6
-6
@@ -28,7 +28,7 @@ A heading tagged `:session:` has (or is about to get) a dedicated, persistent ag
|
||||
** [ ] Close diwan session
|
||||
```
|
||||
|
||||
Can be added by the user directly, when they already know a heading needs its own ongoing session, or by diwan (ordinarily `tick`) when it decides a `:diwan:`-tagged request is non-trivial and self-contained enough to delegate (see above). `DIWAN_ID` is a herdr terminal name (see "herdr", below) — not an arbitrary id. It points directly at the live/persisted agent session handling this heading, so "jump in personally" is just attaching to that terminal, no separate lookup needed. A heading keeps the same `DIWAN_ID`/`:session:` tag across multiple tick passes until its `Close diwan session` item is checked off (`[X]`) by the user, at which point the *next* tick retires the session and leaves the property and tag as a historical record (does not delete them).
|
||||
Can be added by the user directly, when they already know a heading needs its own ongoing session, or by diwan (ordinarily `tick`) when it decides a `:diwan:`-tagged request is non-trivial and self-contained enough to delegate (see above). `DIWAN_ID` is a herdr terminal name (see "herdr", below) — not an arbitrary id. It points directly at the live/persisted agent session handling this heading, so "jump in personally" is just attaching to that terminal, no separate lookup needed. A heading keeps the same `DIWAN_ID`/`:session:` tag across multiple tick passes until its `Close diwan session` item is checked off (`[X]`) by the user, at which point the *next* tick actually retires it: closes that `DIWAN_ID`'s herdr tab for real (`herdr tab close`, not just leaving it be) and removes the `:session:` tag from the heading. The `DIWAN_ID` property itself is left in place as a historical record (in case the session's work is ever worth revisiting) — only the tag and the live terminal go away.
|
||||
|
||||
## `:chat:` tag
|
||||
|
||||
@@ -71,16 +71,16 @@ diwan's own operational file, at the root of the content repo — not a place fo
|
||||
|
||||
### Reports
|
||||
|
||||
Every notable thing a diwan agent does — a tick dispatching something new, a tick triaging a batch of inbox items, a `do` session finishing a real piece of work — gets its own short subheading under the top-level "Reports" heading in `diwan.org`. One entry per notable thing, 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.
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
```org
|
||||
* Reports
|
||||
** [ ] [[file:personal.org::*Plan the kitchen redecoration][Dispatched kitchen redecoration]]
|
||||
[diwan 2026-11-08] Non-trivial, dispatched as do-kitchen.
|
||||
** [X] Triaged 2 inbox items
|
||||
[diwan 2026-11-07] Moved into esdeveniments.org and personal.org.
|
||||
** [ ] [[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
|
||||
[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.
|
||||
|
||||
Reference in new issue
Block a user