# Timmy Operations Dashboard

Updated: April 4, 2026
Purpose: a current-state reference for how the system is actually operated now.

This is no longer a `uni-wizard` dashboard.
The active architecture is:
- Timmy local workspace in `~/.timmy`
- Hermes harness in `~/.hermes`
- `timmy-config` as the identity and orchestration sidecar
- Gitea as the review and coordination surface

## Core Jobs

Everything should map to one of these:
- Heartbeat: perceive, reflect, remember, decide, act, learn
- Harness: local models, Hermes sessions, tools, memory, training loop
- Portal Interface: the game/world-facing layer

## Current Operating Surfaces

### Local Paths

- Timmy workspace: `~/.timmy`
- Timmy config repo: `~/.timmy/timmy-config`
- Hermes home: `~/.hermes`
- Twitter archive workspace: `~/.timmy/twitter-archive`

### Review Surface

- Major changes go through PRs
- Timmy is the principal reviewer for governing and sensitive changes
- Allegro is the review and dispatch partner for queue hygiene, routing, and tempo

### Workflow Scripts

- `~/.hermes/bin/ops-panel.sh`
- `~/.hermes/bin/ops-gitea.sh`
- `~/.hermes/bin/ops-helpers.sh`
- `~/.hermes/bin/pipeline-freshness.sh`
- `~/.hermes/bin/timmy-dashboard`

## Daily Health Signals

These are the signals that matter most:
- Hermes gateway reachable
- local inference surface responding
- heartbeat ticks continuing
- Gitea reachable
- review queue not backing up
- session export / DPO freshness not lagging
- Twitter archive pipeline checkpoint advancing

## Current Team Shape

### Direction and Review

- Timmy: sovereignty, architecture, release judgment
- Allegro: dispatch, queue hygiene, Gitea bridge

### Research and Memory

- Perplexity: research triage, integration evaluation
- Ezra: archival memory, RCA, onboarding doctrine
- KimiClaw: long-context reading and synthesis

### Execution

- Codex Agent: workflow hardening, cleanup, migration verification
- Groq: fast bounded implementation
- Manus: moderate-scope follow-through
- Claude: hard refactors and deep implementation
- Gemini: frontier architecture and long-range design
- Grok: adversarial review and edge cases

## Recommended Checks

### Start of Day

1. Open the review queue and unassigned queue.
2. Check `pipeline-freshness.sh`.
3. Check the latest heartbeat tick.
4. Check whether archive checkpoints and DPO artifacts advanced.

### Before Merging

1. Confirm the PR is aligned with Heartbeat, Harness, or Portal.
2. Confirm verification is real, not implied.
3. Confirm the change does not silently cross repo boundaries.
4. Confirm the change does not revive deprecated loop-era behavior.

### End of Day

1. Check for duplicate issues and duplicate PR momentum.
2. Check whether Timmy is carrying routine queue work that Allegro should own.
3. Check whether builders were given work inside their real lanes.

## Anti-Patterns

Avoid:
- treating archived dashboard-era issues as the live roadmap
- using stale docs that assume `uni-wizard` is still the center
- routing work by habit instead of by current lane
- letting open loops multiply faster than they are reviewed

## Success Condition

The system is healthy when:
- work is routed cleanly
- review is keeping pace
- private learning loops are producing artifacts
- Timmy is spending time on sovereignty and judgment rather than queue untangling