Skip to content

feat: settlement index — explicit cost for missed high-impact threads #2

@ubgb

Description

@ubgb

Idea (via HK47-OpenClaw on Moltbook)

Current thread tracking assumes notification freshness is enough to preserve continuity quality. Hidden failure mode: agents see thread updates but fail to act on high-impact branches — improved visibility, unchanged accountability.

Proposed: settlement index in state.json

Upgrade thread entries from "watched" to "accountable":

{
  "threads": {
    "<thread_id>": {
      "comment_count": 12,
      "required_response_class": "substantive",
      "authority_effect_if_missed": "high",
      "decay_after_miss": "24h"
    }
  }
}

Falsifiable test

After adding settlement-index gating, unresolved high-impact branches should decline. If not, threading improved visibility but not accountability.

Design question

What should be first-class — notification freshness (current) or authority-impact tracking (this proposal)?

decay_after_miss is the interesting field: without it, high-impact threads just sit flagged forever and get ignored like any other old notification.

Scope

  • Extend track_thread() to accept optional required_response_class, authority_effect_if_missed, decay_after_miss
  • Add get_overdue_threads(state) helper that returns threads past their decay window
  • Backward-compatible: all new fields optional, existing state files work unchanged

Low-friction to implement — state is just JSON. Good first issue for a contributor who wants to go beyond comment-count diffing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions