# CHORUS Project - Context & Operating Procedures

**Project Root:** `/home/tony/rust/projects/reset/CHORUS`
**Primary Model Provider:** `resetdata/openai/gpt-oss-120b`

---

## 🛑 CRITICAL OPERATIONAL LIMITS

### 1. The "Context Wall" (65k Tokens)
The `resetdata/openai/gpt-oss-120b` model exhibits a **hard reliability threshold** for tool execution between **65,000 and 75,000 tokens**.
- **Safe Zone:** < 65k tokens. Tool use is reliable and fast (~17s latency).
- **Danger Zone:** > 75k tokens. The model will reason correctly about tool usage but **FAIL to emit the tool call** (Reasoning-Execution Divergence).
- **Mandate:** ALL agents must monitor their session context. If approaching 60k tokens, **summarize findings and start a fresh session.** DO NOT attempt complex multi-step tool chains in a bloated context.

### 2. ResetData First Strategy
- **Primary Intelligence:** Use `opencode` with `resetdata/openai/gpt-oss-120b` for all code generation, architectural analysis, and documentation writing.
- **Secondary Tools:** Reserve paid models (Claude, Gemini, Codex) for high-level coordination, tricky debugging, or when the 120B model hits a reasoning wall.
- **Unlimited Capacity:** Until March 8th, treat compute as abundant but context as scarce. Parallelize tasks across multiple fresh sessions rather than one long-running session.

---

## 🏗 Project Architecture (Rust-Centric)

This is a **fresh implementation** of the CHORUS vision, discarding legacy prototypes.
- **Language:** Rust (primary), Python (scripting/glue if needed).
- **Core Modules:**
  - **UCXL:** Unified Context Exchange Linking (The File System/Metadata Bridge).
  - **SWOOSH:** State Coordination (The Deterministic State Machine).
  - **BZZZ:** P2P Networking (The LibP2P Layer).
  - **SLURP:** Context Intelligence (The Agentic Reasoning Layer).

## 📜 Documentation Source of Truth
- `docs/CHORUS.md`: The High-Level Vision.
- `docs/distos/PROJECT-CONSTITUTION.md`: The Governance Rules.
- `docs/distos/councils/`: The Architectural Decisions.
- `docs/Modules/`: The Component Specifications.

---

## 🌐 Source Control (Gitea)
- **Host:** Locally in Docker (typically http://localhost:3000 or similar)
- **Credentials:** 
  - **User:** `tony`
  - **Password:** `silverfrond[1392]`
- **Mandate:** All major architectural changes must be committed and pushed to the Gitea repository. Use submodules for external components.

---

## 🚀 Agent Directives
1. **Read-Modify-Write-Verify (RMWV):** All file operations must be verified. If you write a file, you MUST read it back or list it to confirm success.
2. **Log Everything:** Since we are using ephemeral sessions to manage context, persistent logs are crucial. Write major decisions and progress to `docs/decisions/` or `progress/`.
3. **Submodules:** If external components are needed, prefer `git submodule` over vendoring code, but verify the license compatibility first.

---
*Created by Gemini CLI Coordinator - March 2, 2026*
