Maity: Board

KTW follow-up reminders from the hub (idea)

tsk-j9jqwj5bbv57 proposed feature

Maintainer idea (2026-10-22, via oz-agent-e): once the hub reads the project's Keep the Why state (the KTW panel work, state.json from the URL in .keep-the-why), it notifies the responsible member when entries stay open / needs-review / pending-confirmation, or a Revisit-when has fired, unresolved by humans for N days, and escalates after M days (to the steward, then the owner via inbox). Scope check: reading the published state and routing reminders is on the right side of context/scope.md ("KTW stays external and optional; the hub never reimplements it") - the hub never parses context/ itself, never decides KTW semantics, only reacts to the published state. Needs: contract (thresholds as project policy, who is responsible: area owner of the entry's path, else the KTW steward, else the owner; dedup; a reminder is a notice, escalation is an inbox info request). Proposed until the KTW panel lands.