awake: no read-back sections — open tasks (overdue), open claims and chains stay write-only

[1Croydan1]

Problem

awake — the one surface the agent reliably reads on entry (93 organic calls, 68% of top-level kaeru sessions) — doesn't show exactly the entities whose read loops are dead. AwakenedContext (kaeru-core/src/session.rs:72-131) contains layered/cortex/pinned/recent/under_review — nothing else.

Consequences (audit of 13,105 sessions + live graph)

1. Tasks: 69 task / 14 done. The concept of overdue doesn't exist in the code at all (grep -rn overdue → 0). Real case: a task due Aug 3 was still open on Aug 12, even though on Aug 10 the agent actively worked the same initiative and closed a sibling task — nothing surfaced the overdue deadline.
2. Open hypotheses: 15 of 21 hypothesis nodes are forever open; zero cross-session confirm/refute in the entire history. An open claim is invisible on re-entry: awake doesn't show it, and "open questions" in overview means only inbound contradicts edges (recall/overview.rs:117-119), not status:open. The only path is tagged "status:open" — and tagged has never been called, ever.
3. Chains: 22 chains written, 0 ever read (chains=0, read_chain=0 in the whole history). In awake a chain is a faceless line name (chain) — id in the warm bucket (cap 15, newest-first — washed out within days); the summary authored "for the future agent" is never printed. A complete write-only cycle was captured live: awake showed the line → reflect marked the chain stale → the agent called rechain — servicing a chain it never once opened.

Proposal

Three sections in awake:

• open tasks (N) — with due dates, overdue first;
• open claims awaiting verdict (N) — hint confirm/refute --by <evidence>;
• chains (N): name — summary → read_chain <name> — print the agent-authored summary; raise a chain regardless of age when its endpoints intersect pinned/hot/core.
  Plus: add a "stale/overdue tasks" category to reflect's work-list (kaeru-mcp/src/tools/lint.rs:52-109).

[GrumpyChubbyCat]

Done in fda0683 — thanks, this was the sharpest of the audit issues: it named the exact mechanism (nothing on the re-entry path mentions these entities, so they're write-only) rather than just the symptom.

Three read-back sections in awake:

open tasks (3):
  - [⚠ OVERDUE 2026-08-03] renew-the-certificate — <id>
  - [due 2026-08-25] write-the-cfp — <id>
  - [no due date] refactor-lint — <id>
↳ `done <name>` when finished, `set_status <name> <status>` to move it, `board` for the columns.

open claims (1):
  - caching-wins — <id>
    the cache pays for itself
↳ still awaiting a verdict — `confirm <name> --by <evidence>` or `refute <name> --by <evidence>`.

chains (1):
  - the-trail — <id>
    why we picked the second option
↳ saved reasoning trails — read one with `why <name>`.

On overdue: you were right that it didn't exist in the code. It does now — OpenTask.overdue compares the due: tag against today (UTC), strictly before, so a task due today isn't late yet. Tasks sort deadline-first, which means the cap can never push an overdue one out of view (there's a test for exactly that).

On "open": defined against the initiative's own status registry — the last column is terminal, everything before it is open. A task whose status: matches no column counts as open too, same fallback the board view uses, so drift surfaces instead of vanishing.

One departure from the proposal. You asked to raise a chain when its endpoints intersect pinned/hot/core. I listed all chains instead: they're deliberately authored and therefore few, and an intersection rule would quietly hide the ones that don't qualify — the exact failure this issue is about. Instead every section caps at 10 rows, prints the true total in the header, and names the remainder (… and 4 more — board``). Capped, never silent.

reflect gained the overdue tasks category as asked. Note it doesn't suggest re-dating: there is no verb that changes a due: tag after capture. That's a real gap, worth its own issue.

Also in kaeru-rig (open_tasks / open_claims / chains in the kaeru_awake JSON, overdue_tasks in kaeru_reflect).