Skip to content

fix: correct IN11 operator name truncation in operators.json (closes #89) #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hummbl-dev wants to merge 3 commits into
base: main
Choose a base branch
from
Open

fix: correct IN11 operator name truncation in operators.json (closes #89) #90

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6070083
fix: correct IN11 operator name truncation in operators.json
hummbl-dev Jul 24, 2026
2a7d8c9
Merge branch 'main' into claude/fix-in11-name
hummbl-dev Jul 29, 2026
601d655
Merge branch 'main' into claude/fix-in11-name
hummbl-agent Aug 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions base120/data/operators.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
"code": "P4",
"name": "Lens Shifting",
"transformation": "P",
"definition": "Deliberately adopt different interpretive frameworks to reveal hidden aspects"
"definition": "Deliberately adopt different interpretive frameworks to reveal hidden aspects of a situation"
},
{
"code": "P5",
Expand Down Expand Up @@ -105,7 +105,7 @@
"code": "P18",
"name": "Boundary Object Selection",
"transformation": "P",
"definition": "Choose representations that bridge multiple perspectives while remaining meaningful"
"definition": "Choose representations that bridge multiple perspectives while remaining meaningful to each"
},
{
"code": "P19",
Expand Down Expand Up @@ -165,7 +165,7 @@
"code": "IN8",
"name": "Contrapositive Reasoning",
"transformation": "IN",
"definition": "Use logical equivalence that \"if A then B\" equals \"if not B then not A\""
"definition": "Use logical equivalence that if A then B equals if not B then not A"
},
{
"code": "IN9",
Expand All @@ -181,7 +181,7 @@
},
{
"code": "IN11",
"name": "Devil",
"name": "Devil's Advocate Protocol",
"transformation": "IN",
"definition": "Assign explicit role to argue against group consensus or preferred option"
},
Expand Down Expand Up @@ -267,7 +267,7 @@
"code": "CO5",
"name": "Emergence",
"transformation": "CO",
"definition": "Recognize higher-order behavior arising from component interactions"
"definition": "Recognize higher-order behavior arising from component interactions beyond individual properties"
},
{
"code": "CO6",
Expand Down Expand Up @@ -345,7 +345,7 @@
"code": "CO18",
"name": "Knowledge Graphing",
"transformation": "CO",
"definition": "Represent information as interconnected entities and relationships"
"definition": "Represent information as interconnected entities and relationships rather than isolated documents"
},
{
"code": "CO19",
Expand Down Expand Up @@ -571,7 +571,7 @@
},
{
"code": "RE16",
"name": "Retrospective\u2192Prospective Loop",
"name": "Retrospective -> Prospective Loop",
"transformation": "RE",
"definition": "Use systematic reflection on past to inform future planning"
},
Expand Down Expand Up @@ -719,4 +719,4 @@
"transformation": "SY",
"definition": "Manage interactions between independent systems with emergent behaviors"
}
]
]

@coderabbitai coderabbitai Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Add CI validation for canonical YAML/JSON parity.

Regeneration fixes the current drift, but the linked objective also calls for CI to compare the canonical YAML with operators.json; JSON parsing alone will not prevent future name or definition drift. Add that check or confirm it exists outside this diff.

🤖 Prompt for 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.

In `@base120/data/operators.json` at line 722, Add CI validation that regenerates
or loads the canonical YAML and compares its complete operator names and
definitions against operators.json, failing when either content or ordering
drifts. Locate the existing CI workflow or generation/check command rather than
modifying the data file, and reuse the project’s canonical comparison mechanism
if one already exists.