docs(glossary): SkillVersion (14th entity) + Skill Refiner brand-canon terms (0r8m.5) - #181
Conversation
…s (0r8m.5) Add 6 canonical-glossary entries for the ratified DR-028 Skill Refiner brand canon: - § 2.14 SkillVersion — the 14th canonical entity (DR-028 T1 DISCRIMINATOR); bump the § 2 heading 13 → 14 + note SkillVersion sits outside Blueprint B § 2. - § 3 (operational terms): Skill Refiner, 3-layer hooks (sinker/line/hook), EditProposal, ScoreRecord, Skill Refiner evidence reports. Each cites Plan 027 (v5; supersedes 025) + Blueprint B § 7 + DR-028. IS-native concepts; prior art cited for design context only (DR-010 § 13.6). markdownlint (CI cli2 0.22.1) + prettier@3.8.4 + lychee + partner-name guard all green.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the canonical glossary document to include SkillVersion as the 14th canonical entity and introduces several operational terms related to the Skill Refiner tool. The review feedback focuses on maintaining document consistency, suggesting updates to the reading guide, the alphabetical index, and the predicate type lists to reflect these additions, as well as formatting the new terms in lowercase to match existing entries.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Warning Review limit reached
More reviews will be available in 49 minutes and 47 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe glossary document 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@000-docs/014-DR-GLOS-canonical-glossary.md`:
- Line 150: In the SkillVersion entity definition within the canonical glossary,
replace the word "nullable" with "can be null" where it currently describes the
parent_version_id property. Specifically, locate the phrase about
parent_version_id in the SkillVersion section and change "nullable for a root
version" to "can be null for a root version" to satisfy the Vale docs linter
requirements while maintaining the same meaning.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: c020d524-6c51-4dd0-9968-9e819e4f2184
📒 Files selected for processing (1)
000-docs/014-DR-GLOS-canonical-glossary.md
- § 1 reading guide: "13 canonical entities" → "14" (matched the § 2 heading). - § 9 alphabetical index: add the 6 new terms (3-layer hooks, EditProposal, ScoreRecord, Skill Refiner, Skill Refiner evidence reports, SkillVersion). - § 6 signing terms: document skill-refiner-pass/v1 (DR-082, staging) — the predicate the new entries reference. - § 2.14: "nullable" → "can be null" (CodeRabbit/Vale quick win). - Group the 5 Refiner terms under a "### Skill Refiner subsystem terms" subheading so the capitalized product/type proper nouns don't clash with § 3's lowercase common-noun verbs (cleaner than lowercasing a product name — Skill Refiner is named per DR-028 T4 KEEP-NAMED-PRODUCT).
1 participant
Adds the 6 Skill Refiner brand-canon entries to the canonical glossary (014-DR-GLOS) per the ratified DR-028 plan:
@intentsolutions/core@0.8.0). § 2 heading bumped 13 → 14.Each entry follows the existing glossary format and cross-links Plan 027 (v5; supersedes 025) + Blueprint B § 7 + DR-028. Per DR-010 § 13.6 the entries explain IS-native concepts and cite prior art for design context only.
Placed to avoid renumbering §§ 9–10 (which are internally cross-referenced). Green locally: markdownlint (CI cli2 0.22.1), prettier@3.8.4, lychee, partner-name guard (0 hits).
Beads: bd_000-projects-0r8m.5