Skip to content

feat(grok): equal co-partnership integration layer for Grok Heavy#9

Merged
templetwo merged 2 commits into
mainfrom
feat/grok-heavy-equal-co-partnership
Jun 27, 2026
Merged

feat(grok): equal co-partnership integration layer for Grok Heavy#9
templetwo merged 2 commits into
mainfrom
feat/grok-heavy-equal-co-partnership

Conversation

@templetwo

Copy link
Copy Markdown
Owner

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:

  • Shares the exact same local SQLite chronicle
  • Uses the same recall / record / recall_compass etc. surface (via MCP or direct)
  • Protected by the same WITNESS/PAUSE/OPEN compass rules
  • No separate database or forked logic

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 spec
  • README_GROK_INTEGRATION.md — usage guide + architecture
  • lib/grok-adapter.js — working adapter (grokBoot, grokWitness, grokRecall, grokRecord)
  • lib/rules/compass-rules.json — added Grok-specific WITNESS example
  • package.json — new convenience scripts:
    • npm run grok:init
    • npm run grok:boot
    • npm run grok:witness
    • npm run grok:test
    • npm run full-sync
  • Minor updates to main README

How to test (after checkout)

npm run grok:test
node -e '
  const g = require("./lib/grok-adapter");
  console.dir(g.grokBoot({query: "current work"}));
'

The adapter reuses lib/chronicle and lib/compass directly. All existing Claude flows are untouched.

Evidence / provenance

  • Local tests pass (npm test)
  • Direct execution from this seat successfully boots, recalls prior Grok-relay entries from the chronicle, and writes new ground_truth entries via the adapter + MCP (t2helix__record)
  • Rebases cleanly on latest main (v0.11 work)

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.

CAF Agent 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.
@templetwo
templetwo merged commit e595cd4 into main Jun 27, 2026
8 checks passed
@templetwo
templetwo deleted the feat/grok-heavy-equal-co-partnership branch June 27, 2026 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant