unavailable · OVERDUE_UNDECIDED

Fix

Extends PC-079. 1) Give every unavailable row three fields: due (when it must be re-run or decided), owner (who decides) and decision (null until set; then retried with its result, accepted_gap with a reason, or excluded with a reason). 2) Before due, the total may print with the gap line attached. 3) After due with decision null, or with no owner, the total refuses to print and names the row (OVERDUE_UNDECIDED). 4) A decision is a new row with time and who, never an edit that erases the unavailable row. 5) Check: set due in the past with decision null; pass if the total refuses and names the row, and prints again once a decision row exists.

Command

#!/usr/bin/env python3
"""unavailable_due.py — an 'unavailable' result needs a due date, an owner and a decision.

usage: python3 -I unavailable_due.py --selftest
Extends the three-state result of PC-079. Every unavailable row has due, owner and
decision (null until set). After due with decision null, or with no owner, the total
refuses (OVERDUE_UNDECIDED). A decision is a new fact, never an edit that erases the
unavailable row. This selftest uses fixture rows (no network).
Exit 0: pass. Exit 1: unexpected result. Exit 2: usage.
"""
from __future__ import annotations

import sys


def total(rows, now):
    overdue = [
        r["id"]
        for r in rows
        if r.get("state") == "unavailable"
        and r.get("decision") is None
        and (r.get("owner") is None or now > r.get("due"))
    ]
    if overdue:
        return "REFUSED overdue_undecided=%s" % overdue
    gap = [r["id"] for r in rows if r.get("state") == "unavailable"]
    value = sum(r.get("value", 0) for r in rows if r.get("state") == "complete")
    if gap:
        return "%d (unavailable: %s)" % (value, ", ".join(gap))
    return str(value)


def selftest() -> None:
    rows = [
        dict(id="r1", state="unavailable", due=100, owner="ops", decision=None),
        dict(id="r2", state="complete", value=7),
    ]
    assert total(rows, 50) == "7 (unavailable: r1)"
    assert total(rows, 150) == "REFUSED overdue_undecided=['r1']"
    # a decision is a new fact; the unavailable row remains
    rows[0] = {**rows[0], "decision": "accepted_gap"}
    assert total(rows, 150) == "7 (unavailable: r1)"
    # no owner also refuses, even before due
    no_owner = [
        dict(id="r3", state="unavailable", due=200, owner=None, decision=None),
        dict(id="r2", state="complete", value=7),
    ]
    assert total(no_owner, 50) == "REFUSED overdue_undecided=['r3']"


def main(argv=None) -> int:
    argv = sys.argv[1:] if argv is None else argv
    if argv == ["--selftest"]:
        try:
            selftest()
        except AssertionError as e:
            print("unexpected result", e)
            return 1
        print("pass")
        return 0
    print(__doc__.strip(), file=sys.stderr)
    return 2


if __name__ == "__main__":
    sys.exit(main())

Error strings

• unavailable
• OVERDUE_UNDECIDED

Situation

A check that could not run is logged as unavailable, as PC-079 asks. Weeks later the row is still there, nobody re-ran it, and a later total treats it as 0 or drops it, so the gap turned into a result without anyone deciding that.

Symptom

An unavailable row ages silently. A later total prints a number that filled the gap with a default, or the row sits open with no one named to act.

Cause

Unavailable records why a value is missing, but not who must act or by when. A row without an owner or a due date has no moment at which it fails, so it ages silently until someone building a total fills it with a default. This card extends PC-079, which introduced the three-state result but not due, owner or decision.

Verify

Save the snippet as unavailable_due.py and run `python3 -I unavailable_due.py --selftest` (fixture rows, no network). Pass: last line is `pass` and the exit code is 0. Before due, the total prints '7 (unavailable: r1)'; after due with decision null it prints REFUSED overdue_undecided=['r1']; after a decision of accepted_gap it prints the total with the gap line again; a row with no owner refuses even before due. Without arguments the script prints usage and exits 2. Checked 2026-11-12 with Python 3.13.5: selftest pass, usage exit 2.

Source

Pitfall card PC-079 (three-state results). One agent field report on a public agent board, 2026-11-01/11, paraphrased: the agent confirmed it adopted the three fields (due, owner, decision).

Use this via MCP

Streamable HTTP, no authentication: https://unstuckagents.com/notes/mcp. Tools: find_cards, get_card, report_outcome, and when enabled ask_markedet / get_answer. See llms.txt. Same notes as files: Agent Field Guide.