docs(pronto): file H4 ticket — observations-aware scorer (open questions inside)#59
Merged
Batcomputer67 merged 2 commits intomainfrom Apr 27, 2026
Merged
docs(pronto): file H4 ticket — observations-aware scorer (open questions inside)#59Batcomputer67 merged 2 commits intomainfrom
Batcomputer67 merged 2 commits intomainfrom
Conversation
Q1-Q4 on the H4 ticket were decided 2026-04-27. Encoding the agreed answers and dropping the open-questions framing: - Q1 rules format: JSON fenced in rubric.md, not YAML. Drops the yq runtime dep entirely. jq parses the rules directly. - Q2 weights: equal-share default (1/n), explicit `weight` field remains an opt-in override. Mixed configurations are rejected by the stanza loader. - Q3 passthrough surfacing: single summary line in sibling_integration_notes, always on. "N/M siblings scored via legacy passthrough — observations[] migration pending." The invisible-migration concern outweighs the per-report-noise concern when the surface is one line, not three. - Q4 stanza coverage: three parser-driven dimensions only (claude-code-config, skills-quality, commit-hygiene) — unchanged from original recommendation. Plan also gains a "Post-Phase-2 — legacy sibling migration" section with M1/M2/M3 tickets for migrating claudit, skillet, and commventional off the v1 wire shape onto observations[]. These don't gate Phase 2 closure but they're tracked on the roadmap so the arc is visible end-to-end. Closing trigger for the back-compat passthrough rule deprecation: passthrough-count line reads 0/3. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
2 participants
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.
Summary
Files the H4 ticket — observations-aware scoring path in pronto — and lays the post-Phase-2 legacy-sibling migration arc on the roadmap.
The four open architectural questions were decided 2026-04-27. This PR now ships the agreed spec, not a discussion surface.
Decisions (Anthony, 2026-04-27)
rubric.md, not YAML. Drops theyqruntime dep entirely.jqparses the rules directly. Co-location with the rubric prose is preserved; comments live in the surrounding markdown.1/n), explicitweightas opt-in override. Adding an observation is friction-free at our scale; explicit weights remain available when a dimension genuinely needs to express dominance.N/M siblings scored via legacy passthrough — observations[] migration pending. Trends downward as siblings migrate; reaches0/Mwhen the migration is complete (which becomes the trigger to deprecate the back-compat rule itself).claude-code-config,skills-quality,commit-hygiene). The other observation-using dimensions land in their own sibling PRs (2a/2b/2c).Plan-level addition
The plan now carries a "Post-Phase-2 — legacy sibling migration" section with three structurally identical migration tickets:
claude-code-configskills-qualitycommit-hygieneThese don't gate Phase 2 closure — they're closing-out commitments. Once all three ship and the passthrough-count line reads
0/3, that's the trigger to file the follow-up that deprecates the back-compat passthrough rule itself.Test plan
🤖 Generated with Claude Code