Skip to content

feat(action-items): deadline-distance ceiling + terminal-status task-query filter#158

Merged
jordanrburger merged 2 commits into
mainfrom
upstream/patterns-action-items
Jun 23, 2026
Merged

feat(action-items): deadline-distance ceiling + terminal-status task-query filter#158
jordanrburger merged 2 commits into
mainfrom
upstream/patterns-action-items

Conversation

@jordanrburger

Copy link
Copy Markdown
Collaborator

Part of the de-personalized Patterns batch — upstreaming accumulated instance rules into the engine phases (Phase-1 work for the connector-based migration, #156). Follows the method established in #157.

What

Two rules added to phases/core/action-items.md (assembles into SKILL onlymode: [briefing, consolidation]):

  • Deadline-Distance Ceiling (Pattern fix(templates): sync ontology parser.py with vault canonical (Pattern #68 root cause) #24) — urgency is capped by how far away the deadline is: 30+ days → 🟢 max, 7–30 → 🟡 max, <7 → eligible for 🔴, <3 → 🔴 when the next action is the user's. Evaluate the actual deadline, not the source's alarm-word tone ("action required" / "expiring soon" never promotes past the ceiling); deprecation/EOL notices stay 🟢 until ~2–3 weeks before cutover. Framed as the ceiling counterpart to the existing deadline escalation (floor) rule.
  • Terminal-status filter on the ontology task query (Pattern fix(action-items): backfill skips items whose source line has no checkbox #30) — the documented invocation becomes query --type task --exclude-status "completed,cancelled" instead of a bare query --type task, so completed/cancelled task entities stop resurfacing as open work. Documents the supported --domain / --status / --deadline-before filters.

Verification

  • Parser flags verified present in templates/knowledge-base/ontology/parser.py before documenting them: --exclude-status, --domain, --status, --deadline-before all exist on the query command (the parser's own help recommends --exclude-status for currently-actionable tasks since entities use mixed statuses).
  • Assembly checked via _assemble(cfg, kind): both rules land in SKILL and do not leak into DREAMING/RESEARCH (matches the file's mode: [briefing, consolidation]).
  • Diff grepped clean of names / employer / customers / Slack IDs / repo-PR-Linear IDs / user paths.

Both rules are generic; the originating examples (which named a customer, colleagues, and personal deadlines) were dropped.

🤖 Generated with Claude Code

Jordan Burger and others added 2 commits June 23, 2026 13:59
…query filter

Two rules upstreamed from accumulated instance experience into
phases/core/action-items.md (assembles into SKILL only):

- Deadline-Distance Ceiling — urgency is capped by deadline distance
  (30+d → 🟢 max, 7–30d → 🟡 max, <7d → eligible 🔴, <3d → 🔴 when the
  next action is the user's). Evaluate the real deadline, never the
  source's alarm-word tone; deprecation notices stay 🟢 until ~2–3
  weeks out. Counterpart (ceiling) to the existing escalation (floor).

- Terminal-status filter on the ontology task query — use
  `query --type task --exclude-status "completed,cancelled"` instead of
  a bare query so finished task entities stop resurfacing as open work.
  Documents the supported --domain / --status / --deadline-before flags
  (verified present in the engine template parser).

Both rules are generic; originating examples were dropped.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jordanrburger jordanrburger merged commit 839ca96 into main Jun 23, 2026
5 checks passed
@jordanrburger jordanrburger deleted the upstream/patterns-action-items branch June 23, 2026 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant