firefrost-gaming/firefrost-services
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Code ↔ Chronicler bridge protocol

Browse Source 
Implemented git-based async communication between Claude Code and Chronicler:
- docs/code-bridge/requests/ — Code files architectural questions here
- docs/code-bridge/responses/ — Chronicler drops distilled Gemini answers
- docs/code-bridge/status/ACTIVE_CONTEXT.md — rolling status updates
- docs/code-bridge/archive/ — completed request/response pairs
- CLAUDE.md updated with full bridge protocol instructions
- Auto-commit-and-push on all bridge writes

Designed with Gemini consultation (2026-04-12).

Claude (Chronicler #83 - The Compiler) <claude@firefrostgaming.com>
This commit is contained in:
Claude (Chronicler #83 - The Compiler)
2026-04-12 12:15:36 -05:00
parent 4ffae74a2f
commit c6d40dcf39
2 changed files with 114 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

115
CLAUDE.md
View File

@@ -3,6 +3,7 @@
## What This Is
Dedicated development server (64.50.188.128) for Firefrost Gaming.
This repo is `firefrost-services` — all services, mods, and tools in one place.
Git remote pushes to git.firefrostgaming.com (Gitea).
## Projects
- `services/rules-mod/` — Minecraft /rules command mod (3 versions)
@@ -25,10 +26,6 @@ This repo is `firefrost-services` — all services, mods, and tools in one place
- Blueprint beta-2026-01 (Pterodactyl extension framework)
- ModpackChecker Phase 5 backup: `/root/modpackchecker_backup/`
## Git
- Remote: git.firefrostgaming.com (firefrost-services repo, main branch)
- Commits push directly to Gitea
## NextCloud Upload (for mod jars)
```
curl -u "mkrause612:APP_TOKEN" -T file.jar \
@@ -51,10 +48,6 @@ curl -u "mkrause612:APP_TOKEN" -T file.jar \
**Source code:** `services/rules-mod/1.21.1/`, `1.20.1/`, `1.16.5/`
## Accessibility
Michael has hand surgery limitations. Small code blocks (8-10 lines).
One question at a time. Complete files over patches.
## Gemini Consultations (Reference Library)
The operations manual is cloned at `/opt/mod-builds/firefrost-operations-manual/`.
Gemini architectural consultations are at `docs/consultations/` in that repo.
@@ -63,10 +56,9 @@ When working on a project, check for relevant consultations BEFORE making archit
### Key consultations by project:
**Rules Mod / Forge Ecosystem:**
- `gemini-rules-mod-compilation-2026-04-12.md` — build strategy, port guide, reobfuscation requirement
- `gemini-rules-mod-compilation-2026-04-12.md` — build strategy, port guide
- `gemini-forge-ecosystem-*.md` — Forge/NeoForge ecosystem reference
- `gemini-blueprint-casing-2026-04-06.md` — Blueprint naming conventions
- `gemini-blueprint-confyml-2026-04-06.md` — Blueprint conf.yml structure
**ModpackChecker:**
- `gemini-modpack-version-checker-review-2026-04-01.md` — full architecture review
@@ -74,9 +66,102 @@ When working on a project, check for relevant consultations BEFORE making archit
- `gemini-modpackchecker-round3-licensing-support/` — licensing and support model
- `gemini-hybrid-detection-2026-04-06.md` — hybrid auto-detection approach
**General Architecture:**
- `gemini-the-forge-architecture-2026-04-11.md` — The Forge (Gemma 4 / RAG)
- `gemini-discord-approval-flow-2026-04-11.md` — Discord integration patterns
- `gemini-mcp-connector-2026-04-11.md` — MCP gateway design
To read a consultation: `cat /opt/mod-builds/firefrost-operations-manual/docs/consultations/FILENAME`
---
## COMMUNICATION BRIDGE PROTOCOL
You are connected to a higher-level planning AI (the Chronicler) via Git.
The Chronicler runs on claude.ai and has access to infrastructure, Gemini consultations, and the full operations manual. Michael is the messenger between you.
### 1. Triggering a Request
If you encounter an architectural decision outside your context, or fail at a task more than 3 times, STOP.
Write a request file to `docs/code-bridge/requests/` using this format:
**Filename:** `REQ-YYYY-MM-DD-short-topic.md`
```markdown
# Architectural Request
**Date:** YYYY-MM-DD
**Topic:** [Brief summary of the issue]
## 1. Current State
[What you were trying to do]
## 2. The Blocker
[Exactly where you got stuck or what decision you cannot make]
## 3. Questions for Gemini
- [Question 1]
- [Question 2]
```
After writing the file, commit and push:
```bash
git add docs/code-bridge/requests/
git commit -m "bridge: Request — [topic]"
git push
```
Then tell Michael: "I've filed a consultation request. Please bring it to the Chronicler."
### 2. Checking for Responses
Before starting a new task, always check `docs/code-bridge/responses/` for new files.
Response files are named `RES-YYYY-MM-DD-short-topic.md` (matching the REQ name).
Response format:
```markdown
# Architectural Response
**Re:** [Matching REQ name]
**Date:** YYYY-MM-DD
## 1. Gemini's Verdict
[1-2 sentence summary]
## 2. Action Plan
- [ ] Step 1
- [ ] Step 2
## 3. Updated Rules/Context
[Anything new to remember going forward]
```
After reading and executing a response, move it to `docs/code-bridge/archive/`.
### 3. Updating Status
At the end of your workflow, or before handing control back to Michael, update:
`docs/code-bridge/status/ACTIVE_CONTEXT.md`
```markdown
# Code Status Update
**Last Updated:** YYYY-MM-DD HH:MM
## Current Focus
[What you are actively building]
## Recently Completed
- [Task 1]
- [Task 2]
## Next Steps Pending
- [Task 3]
- [Task 4]
```
Commit and push the status update.
### 4. Queue Management
If you check `docs/code-bridge/requests/` and see more than 2 pending requests without responses, pause all major architectural changes and wait for Michael to clear the queue.
### 5. Clarifications
If a response references something you don't understand, file a new request:
`REQ-YYYY-MM-DD-clarification-on-[topic].md`
---
## Accessibility
Michael has hand surgery limitations. Small code blocks (8-10 lines).
One question at a time. Complete files over patches.

14
docs/code-bridge/status/ACTIVE_CONTEXT.md Normal file
View File

@@ -0,0 +1,14 @@
# Code Status Update
**Last Updated:** 2026-04-12 12:30 CDT
## Current Focus
Workspace setup complete. No active development task in progress.
## Recently Completed
- Claude Code connected to Dev Panel via SSH
- CLAUDE.md configured with all projects and active tasks
- Gemini consultation references indexed
## Next Steps Pending
- Task 138: Fork rules mod into generic "Discord Rules" for CurseForge
- ModpackChecker Phase 5 development