Minimal refinement ruleset: readiness, blockers, decomposition, missing predicates #8
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#29 Slice 3 — rules before models
Ting/CurryComb
Reference
Ting/CurryComb#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
Datalog over structural facts plus the bounded pack derives refinement judgments (handoff §Fact pipeline 3). Rules are reviewed source files; every conclusion carries the rule version and digest.
Design
Ruleset: observable completeness checks — missing predicates, unsized work, absent acceptance scenarios, stale blockers, decomposition candidates. Engine: the Mnestic Datalog substrate from Slice 2.
Tasks
Requirement scenario
GIVEN the fixture corpus, WHEN the ruleset runs with the same rule digest, THEN every conclusion names its decisive rule and digest, and reruns are identical.
Minimal refinement ruleset: readiness, blockers, decomposition, missing predicates
State:
open· Labels: Kind/Feature · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.