Canonical comment v2: derived state rendered, real digests replace Slice 1 placeholders #10
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#10
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
Render readiness, blockers, and open questions into the logical canonical comment; replace
SLICE1_RULE_PAYLOAD/SLICE1_EVIDENCE_PAYLOADwith real digests and bumpprojection_versionin the effect key — the contract ADR-0002 §4 already reserves.Design
currycomb-projectionrenders from #8 conclusions. Duplicate/loser handling per ADR-0002 §3 stays automatic; policy breadth waits for #15.Tasks
canonical_comment/2effect key; input/desired digests realRequirement scenario
GIVEN an issue with two open derived questions, WHEN reconciliation runs at v2, THEN the canonical comment lists both questions with rule digest, and a repeated event is a no-op by desired digest.
Canonical comment v2: derived state rendered, real digests replace Slice 1 placeholders
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.