Timmy_Foundation/timmy-home
16
0
Fork 0
Code Issues 176 Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'Clarify active architecture and repo boundaries' (#1) from codex/cleanup-boundaries into main

Browse Source
This commit was merged in pull request #1.
This commit is contained in:
Perplexity Computer
2026-03-27 21:21:54 +00:00
parent af479d6221 4f5a59641b
commit 9b81d68da4
2 changed files with 17 additions and 132 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
OPERATIONS.md
View File

@@ -1,12 +1,12 @@
# Timmy Operations — What Runs the Workforce
## ACTIVE SYSTEM: Sovereign Orchestration
- **Repo:** Timmy_Foundation/sovereign-orchestration
- **Local:** ~/.timmy/sovereign-orchestration/
- **Entry point:** python3 src/sovereign_executor.py --workers 3 --poll 30
- **Task queue:** SQLite (crash-safe, durable)
- **Status:** Getting deployed (issues #29, #30)
- **Target repos:** Timmy_Foundation/the-nexus, Timmy_Foundation/autolora
## ACTIVE SYSTEM: Hermes + timmy-config sidecar
- **Harness:** Hermes
- **Config repo:** Timmy_Foundation/timmy-config
- **Workspace repo:** Timmy_Foundation/timmy-home
- **Orchestration:** Huey + SQLite via `timmy-config/orchestration.py` and `timmy-config/tasks.py`
- **Target repos:** Timmy_Foundation/the-nexus, Timmy_Foundation/timmy-home, Timmy_Foundation/timmy-config
- **Training data home:** `~/.timmy/training-data/`
## DEPRECATED — DO NOT RESTORE
- bash loops (claude-loop.sh, gemini-loop.sh, timmy-orchestrator.sh)
@@ -16,7 +16,8 @@
- All scripts in timmy-config/bin/ are LEGACY
These crash-loop and produce zero work. They were restored by mistake
on 2026-03-25 causing a regression. The sovereign executor replaces them.
on 2026-03-25 causing a regression. The Hermes + timmy-config sidecar
replaces them.
## How to check what's running
```bash
@@ -30,5 +31,5 @@ ps aux | grep -E "claude-loop|gemini-loop|timmy-orchestrator" | grep -v grep
## Cron Jobs (Hermes built-in)
- Health Monitor: every 5m, haiku (not opus!)
- AutoLoRA training: every 45m, haiku
- DPO export / training support jobs: explicit model, explicit task, no hidden defaults
- All crons MUST specify model explicitly. Never inherit default.

130
decisions.md
View File

@@ -44,129 +44,13 @@ This is the minimal implementation path for honest Timmy. Two key bugs identifie
Priority: Fix these bugs before building the pipeline.
---## 2026-03-24 13:13 UTC — Use SQLite for storage
## 2026-03-27 — Repo boundary clarified
---
`timmy-home` is the lived workspace: gameplay, archive reading, trajectories,
training-data exports, notes, metrics, and research.
## 2026-03-24 13:13 UTC — First decision
---
## 2026-03-24 13:13 UTC — Second decision
---
## 2026-03-24 13:13 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 15:22 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 15:22 UTC — Use SQLite for storage
---
## 2026-03-24 15:22 UTC — First decision
---
## 2026-03-24 15:22 UTC — Second decision
---
## 2026-03-24 19:50 UTC — Use SQLite for storage
---
## 2026-03-24 19:50 UTC — First decision
---
## 2026-03-24 19:50 UTC — Second decision
---
## 2026-03-24 19:50 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 19:51 UTC — Use SQLite for storage
---
## 2026-03-24 19:51 UTC — First decision
---
## 2026-03-24 19:51 UTC — Second decision
---
## 2026-03-24 19:51 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 20:19 UTC — Use SQLite for storage
---
## 2026-03-24 20:19 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 20:19 UTC — First decision
---
## 2026-03-24 20:19 UTC — Second decision
---
## 2026-03-24 20:19 UTC — Use SQLite for storage
---
## 2026-03-24 20:19 UTC — First decision
---
## 2026-03-24 20:19 UTC — Second decision
---
## 2026-03-24 20:19 UTC — Use Redis
Fast in-memory cache
---
## 2026-03-24 20:21 UTC — First decision
---
## 2026-03-24 20:21 UTC — Second decision
---
## 2026-03-24 20:21 UTC — Use SQLite for storage
---
## 2026-03-24 20:21 UTC — Use Redis
Fast in-memory cache
---
`timmy-config` is the sidecar: soul, memories, playbooks, skins, harness
configuration, and lightweight orchestration glue.
Hermes owns the harness. Training should flow from Timmy's lived work and DPO
artifacts, not from re-growing a bespoke training pipeline inside every repo.