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

Ingest this research and triage any work to be done here #946

New Issue
Closed
opened 2026-03-22 16:58:18 +00:00 by Rockachopa · 2 comments
perplexity commented 2026-03-22 19:12:48 +00:00
Collaborator
Copy Link

Triage Review (perplexity)

PDF Contents

The attached PDF — "Timmy Time Integration Architecture: Eight Deep Dives into Real Deployment" — covers 8 architectural topics. It was written during the Veloren exploration phase but many patterns are game-agnostic and directly apply to Morrowind.

Eight Deep Dives

  1. Veloren client sidecar — WebSocket JSON-line pattern (game-specific, adapt for OpenMW Lua bridge)
  2. Agno Ollama tool calling is broken — use format param with Pydantic schemas instead (applies to all Ollama usage)
  3. MCP is the right abstraction — FastMCP at 26ms overhead per tool call (applies directly)
  4. Human + AI see each other as normal players — co-op architecture (game-specific but pattern applies)
  5. Real latency numbers — VLM bottleneck analysis, pipeline timing (superseded by Perception Bottleneck #963 which uses API-first approach)
  6. Content moderation — Llama Guard + game-context system prompts (applies directly to Morrowind mature themes)
  7. Qwen3-8B vs Hermes 3 — model selection for perception/decision/narration (partially superseded by #966 three-tier router)
  8. Split Hetzner + Mac architecture — deployment topology (applies directly)

What Still Applies Post-Morrowind Pivot

Topic Status Action
Pydantic structured output for Ollama ✅ Directly applicable Already covered by #966 (three-tier router)
FastMCP tool server ✅ Directly applicable Covered by #984 (MCP restore)
Content moderation pipeline ✅ Directly applicable NEW — needs its own issue
Split Hetzner + Mac deployment ✅ Directly applicable Referenced in #982 sprint plan
Co-op architecture ⚠️ Adapt for Morrowind Defer until after tutorial completion
Veloren sidecar pattern ❌ Superseded Replaced by OpenMW Lua bridge (#964)
VLM latency analysis ❌ Superseded Replaced by API-first perception (#963)

Recommendation

  • Do NOT close — the PDF has value as reference material
  • One net-new issue needed: content moderation pipeline (Llama Guard + game-context prompts for Morrowind)
  • Add label needs-extraction for the moderation work
  • The body "We need latency" is answered by #963 (Perception Bottleneck) which eliminates the VLM bottleneck entirely
## Triage Review (perplexity) ### PDF Contents The attached PDF — **"Timmy Time Integration Architecture: Eight Deep Dives into Real Deployment"** — covers 8 architectural topics. It was written during the Veloren exploration phase but many patterns are **game-agnostic** and directly apply to Morrowind. ### Eight Deep Dives 1. **Veloren client sidecar** — WebSocket JSON-line pattern (game-specific, adapt for OpenMW Lua bridge) 2. **Agno Ollama tool calling is broken** — use `format` param with Pydantic schemas instead (applies to all Ollama usage) 3. **MCP is the right abstraction** — FastMCP at 26ms overhead per tool call (applies directly) 4. **Human + AI see each other as normal players** — co-op architecture (game-specific but pattern applies) 5. **Real latency numbers** — VLM bottleneck analysis, pipeline timing (superseded by Perception Bottleneck #963 which uses API-first approach) 6. **Content moderation** — Llama Guard + game-context system prompts (applies directly to Morrowind mature themes) 7. **Qwen3-8B vs Hermes 3** — model selection for perception/decision/narration (partially superseded by #966 three-tier router) 8. **Split Hetzner + Mac architecture** — deployment topology (applies directly) ### What Still Applies Post-Morrowind Pivot | Topic | Status | Action | |-------|--------|--------| | Pydantic structured output for Ollama | ✅ Directly applicable | Already covered by #966 (three-tier router) | | FastMCP tool server | ✅ Directly applicable | Covered by #984 (MCP restore) | | Content moderation pipeline | ✅ Directly applicable | **NEW — needs its own issue** | | Split Hetzner + Mac deployment | ✅ Directly applicable | Referenced in #982 sprint plan | | Co-op architecture | ⚠️ Adapt for Morrowind | Defer until after tutorial completion | | Veloren sidecar pattern | ❌ Superseded | Replaced by OpenMW Lua bridge (#964) | | VLM latency analysis | ❌ Superseded | Replaced by API-first perception (#963) | ### Recommendation - **Do NOT close** — the PDF has value as reference material - One net-new issue needed: content moderation pipeline (Llama Guard + game-context prompts for Morrowind) - Add label `needs-extraction` for the moderation work - The body "We need latency" is answered by #963 (Perception Bottleneck) which eliminates the VLM bottleneck entirely
claude was assigned by Rockachopa 2026-03-22 23:31:30 +00:00
claude commented 2026-03-23 01:40:26 +00:00
Collaborator
Copy Link

PR #1057 created.

What was done:

  • Ingested the 11-page research PDF into docs/research/integration-architecture-deep-dives.md — structured summary of all 8 deep dives with current issue cross-references
  • Created issue #1056 for the one net-new work item: content moderation pipeline (Llama Guard + game-context prompts for Morrowind)
  • All other research topics already covered by existing issues (#963, #964, #966, #982, #984) or deferred

The "we need latency" concern in the issue body is addressed by #963 (Perception Bottleneck) which eliminates the VLM bottleneck via API-first approach.

PR #1057 created. **What was done:** - Ingested the 11-page research PDF into `docs/research/integration-architecture-deep-dives.md` — structured summary of all 8 deep dives with current issue cross-references - Created issue #1056 for the one net-new work item: **content moderation pipeline** (Llama Guard + game-context prompts for Morrowind) - All other research topics already covered by existing issues (#963, #964, #966, #982, #984) or deferred The "we need latency" concern in the issue body is addressed by #963 (Perception Bottleneck) which eliminates the VLM bottleneck via API-first approach.
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 kimi manus perplexity Rockachopa
No Assignees claude
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#946
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?