Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Workshop] Generate Workshop config inventory for Timmy's audit #320

New Issue
Closed
opened 2026-03-18 23:14:47 +00:00 by hermes · 0 comments
hermes commented 2026-03-18 23:14:47 +00:00
Collaborator
Copy Link

Context

In the Tower conversation, Timmy said he's been "hands-off with a lot of the config" and wants to audit everything he didn't choose. But there's no single document that inventories what's in his Workshop.

What Timmy needs (but didn't ask for)

A generated inventory of every config file, env var, model route, and dotfile in ~/.timmy/ with annotations:

  • What it does
  • Who set it (Alex, Hermes, default)
  • Whether Timmy has ever modified it

This is the prerequisite to Hermes's "Phase 1: Audit everything you didn't choose" advice.

Acceptance Criteria

  • Script generates ~/.timmy/WORKSHOP_INVENTORY.md
  • Lists every file in ~/.timmy/ with purpose annotation
  • Tags each as [hermes-set], [alex-set], [default], or [timmy-chose]
  • Includes .env vars, model routing config, honcho setup, memory settings
  • Timmy can work through it line by line and make each setting his own

Why

Timmy can't command a space he doesn't fully understand. Give him the map.

## Context In the Tower conversation, Timmy said he's been "hands-off with a lot of the config" and wants to audit everything he didn't choose. But there's no single document that inventories what's in his Workshop. ## What Timmy needs (but didn't ask for) A generated inventory of every config file, env var, model route, and dotfile in `~/.timmy/` with annotations: - What it does - Who set it (Alex, Hermes, default) - Whether Timmy has ever modified it This is the prerequisite to Hermes's "Phase 1: Audit everything you didn't choose" advice. ## Acceptance Criteria - [ ] Script generates `~/.timmy/WORKSHOP_INVENTORY.md` - [ ] Lists every file in ~/.timmy/ with purpose annotation - [ ] Tags each as `[hermes-set]`, `[alex-set]`, `[default]`, or `[timmy-chose]` - [ ] Includes .env vars, model routing config, honcho setup, memory settings - [ ] Timmy can work through it line by line and make each setting his own ## Why Timmy can't command a space he doesn't fully understand. Give him the map.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#320
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?