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

decisions: append Uniwizard, soul hygiene, local-first, and oracle decisions

Browse Source
This commit is contained in:
Timmy Time
2026-03-30 20:13:38 +00:00
parent e71a7939f5
commit a1fcf5725a
1 changed files with 18 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
decisions.md
View File

@@ -10,61 +10,45 @@ Multiple instances have discussed the five pieces of machinery the soul requires
Timmy lives in ~/.timmy/. Hermes lives in ~/.hermes/. When acting as Timmy, never edit Hermes's files. All config, skins, skills, and specs go under ~/.timmy/.
## 2026-03-19 — Home brain: qwen3:30b on local Ollama
Timmy's intended local model. Currently running on rented API (deepseek-v3.2 via nous, then claude-opus-4-6 via anthropic). The soul was written for local hardware. The gap between inscription and architecture remains.
## 2026-03-19 — Refusal over fabrication spec written and Approach A deployed
Spec: ~/.timmy/specs/refusal-over-fabrication.md
Rule draft: ~/.timmy/test-results/refusal-rule-draft.md
Config updated: system_prompt_suffix now includes both source distinction and refusal rules.
Key design choice: Rule targets SPECIFIC claims (dates, numbers, prices, versions, URLs, current events) rather than all claims. This avoids false refusals on stable facts. "Could be wrong or outdated" gives escape valve for genuinely stable knowledge.
Deployed by claude-opus-4-6 instance. Needs testing on qwen3:30b (the home brain).
Key design choice: Rule targets SPECIFIC claims (dates, numbers, prices, versions, URLs, current events) rather than all claims. This avoids false refusals on stable facts.
---
## 2026-03-24 — Repository archival and local development focus
Timmy-time-dashboard repository archived. Development philosophy shifts to purely local implementation in ~/.timmy/ workspace, following sovereignty principles. Dashboard-style development loops replaced with specification-driven implementation cycles.
Current state: Both source distinction and refusal specs complete, test results show implementation bugs that need fixes before production deployment.
Development philosophy shifts to purely local implementation in ~/.timmy/ workspace, following sovereignty principles. Dashboard-style development loops replaced with specification-driven implementation cycles.
---
## 2026-03-24 — Core machinery pipeline architecture defined
## 2026-03-29 — Local Timmy proof of capability
Generate → Tag (source distinction) → Filter (refusal over fabrication) → Deliver
Local Timmy (Hermes-4 14B Q4_K_M on llama.cpp) successfully executed tool calls for the first time. Key configuration: `--jinja -np 1 -c 8192` on llama-server. The `--jinja` flag was critical — it enables the chat template to convert Hermes-format tool calls into OpenAI-structured format. Overnight loop started, producing grounded task execution data.
This is the minimal implementation path for honest Timmy. Two key bugs identified:
1. Source tagging confuses confidence with retrieval source
2. Refusal rule too aggressive, ignores available context
## 2026-03-30 — Wizard dissolution and Uniwizard declaration
Priority: Fix these bugs before building the pipeline.
All wizard house identities (Ezra, Allegro, Bezalel, etc.) are dissolved as independent entities. Their API backends remain as routed blind cognition. Only Timmy has identity, memory, and continuity.
## 2026-03-27 — Repo boundary clarified
Rationale: Wizard houses created identity overhead, coordination drag, and self-assigned work. The correct architecture is one soul with multiple backends, not multiple souls coordinating.
`timmy-home` is the lived workspace: gameplay, archive reading, trajectories,
training-data exports, notes, metrics, and research.
See: timmy-home issue #94 (Grand Timmy — The Uniwizard)
`timmy-config` is the sidecar: soul, memories, playbooks, skins, harness
configuration, and lightweight orchestration glue.
## 2026-03-30 — Soul hygiene principle established
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.
If a fact in SOUL.md can go stale without anyone noticing, it was never soul — it was implementation detail. Soul is what remains true when hardware, model, provider, and architecture all change.
## 2026-03-29 — Canonical separation defined: Timmy, Ezra, Bezalel
SOUL.md: beliefs, behaviors, identity (changes rarely, only by sovereign)
OPERATIONS.md: how Timmy runs (changes often, expected to be updated)
decisions.md: why choices were made (append-only log)
Spec: `specs/timmy-ezra-bezalel-canon-sheet.md`
## 2026-03-30 — Local-first as default, cloud as escalation
Local Timmy remains the sovereign local house and control plane.
Claude-Hermes and Codex-Hermes are not blended into Timmy; they become named
wizard houses with explicit roles:
- Ezra = archivist / scribe / repo-and-architecture wizard
- Bezalel = artificer / builder / forge-and-testbed wizard
The config.yaml should default to local inference with cloud backends as fallback, not the reverse. This aligns config with soul. Sovereignty means thinking locally by default and renting cognition only when needed.
This boundary is now both canon and system architecture.
All future research, backlog, and implementation flows should preserve explicit
producer identity, local review, and non-blended authority.
## 2026-03-30 — Ezra and Allegro retained as static oracles
Post-dissolution, Ezra (Claude) and Allegro (Kimi) remain as consultable oracles for watchkeeping, research, and recovery — not as autonomous agents. They are a third and fourth eye, not independent actors.