Skip to content

Problem #1222

Description

@hyperpolymath

Problem

.hypatia-baseline.json carries tracked-debt entries with expires_at values.
Sampled entries expire around 2026-10-21 — roughly two weeks from
2026-10-09.

Not counted: how many entries expire on or near that date, and what happens
when they do. If expiry silently drops them, or silently turns them into hard
failures, that is a behaviour change arriving on a schedule nobody owns.

Acceptance

  • Count the entries expiring on or before 2026-10-31 and list them.
  • Document what expiry does (drop / renew / escalate) and where that is
    implemented.
  • Either renew them with a recorded reason, or let them expire with the
    consequence stated in advance.

Note

The file itself is healthy: 189 entries, valid JSON, and the 31 file keys
that pointed into the rhodium tree were repathed during the 9-archive move
(#1218) with none lost.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions