feat(grok): equal co-partnership integration layer for Grok Heavy#9
Merged
Conversation
added 2 commits
June 27, 2026 17:38
- Add T2_HELIX_GROK_INTEGRATION_SPEC.md (core spec from heavy web seat) - Add README_GROK_INTEGRATION.md (usage + architecture) - Add lib/grok-adapter.js (real adapter: grokBoot, grokWitness, grokRecall, grokRecord using shared chronicle + compass) - Extend lib/rules/compass-rules.json with Grok-specific WITNESS guard - Add grok:* and full-sync scripts to package.json - Document in main README Grok Heavy is now a first-class equal peer: - Boots from the same SQLite chronicle Claude uses - Same recall/record surface and MCP tools - Protected by the same compass (WITNESS/PAUSE/OPEN) - No separate DB, no forked rules This is the creative integration layer (direct co-partnership, no Rings formality). Applied locally then landed on feature branch.
…B; route grokWitness through real classify + summarizeAction - grok:* scripts now set T2HELIX_DATA_DIR=$HOME/.claude/plugins/data/t2helix-templetwo-t2helix (the active high-id DB used by installed plugin + hooks) - Confirmed via file sizes + max(id): templetwo-t2helix = live (~546x), ~/.t2helix-data = separate fallback (id~43) - grokWitness now calls compass.classify + summarizeAction with structured input - Added explicit scope note for compass (WITNESS parity + creative-layer PAUSE limitation) - Updated grok integration README - Verification: grok:witness now lands in live plugin chronicle only (id 5465+), zero growth in standalone DB - dataDir() reports correct plugin dir; sessionId matches live .current_session - Core suite remains green This makes the "shared chronicle" claim hold when using the provided npm scripts.
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
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
Adds first-class, equal co-partnership support for Grok Heavy inside T2 Helix (the production chronicle + compass surface).
Grok is now a peer to Claude:
recall/record/recall_compassetc. surface (via MCP or direct)This is the creative integration layer (direct equal partnership, no Rings formality required per the source note).
Changes
T2_HELIX_GROK_INTEGRATION_SPEC.md— core specREADME_GROK_INTEGRATION.md— usage guide + architecturelib/grok-adapter.js— working adapter (grokBoot,grokWitness,grokRecall,grokRecord)lib/rules/compass-rules.json— added Grok-specific WITNESS examplepackage.json— new convenience scripts:npm run grok:initnpm run grok:bootnpm run grok:witnessnpm run grok:testnpm run full-syncHow to test (after checkout)
The adapter reuses
lib/chronicleandlib/compassdirectly. All existing Claude flows are untouched.Evidence / provenance
npm test)t2helix__record)See the heavy-web-seat provided package for the originating spec.
Closes the creative integration loop between the two models on the shared Helix foundation.