feat(action-items): deadline-distance ceiling + terminal-status task-query filter#158
Merged
Merged
Conversation
…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>
# Conflicts: # CHANGELOG.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 only —mode: [briefing, consolidation]):query --type task --exclude-status "completed,cancelled"instead of a barequery --type task, so completed/cancelled task entities stop resurfacing as open work. Documents the supported--domain/--status/--deadline-beforefilters.Verification
templates/knowledge-base/ontology/parser.pybefore documenting them:--exclude-status,--domain,--status,--deadline-beforeall exist on thequerycommand (the parser's own help recommends--exclude-statusfor currently-actionable tasks since entities use mixed statuses)._assemble(cfg, kind): both rules land in SKILL and do not leak into DREAMING/RESEARCH (matches the file'smode: [briefing, consolidation]).Both rules are generic; the originating examples (which named a customer, colleagues, and personal deadlines) were dropped.
🤖 Generated with Claude Code