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

[Morrowind P5] Web Frontend — Stream + Vitals + Journal + Chat (HTMX) #836

New Issue
Closed
opened 2026-03-21 22:20:57 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 22:20:57 +00:00
Collaborator
Copy Link

Scope

Build the spectator web frontend as a single page using HTMX + WebSocket.

Components

  • The stream: Central, dominant. Full video with audio.
  • Vitals sidebar: Health, magicka, fatigue, current cell, time of day. Pulled from perception JSON via WebSocket.
  • Journal feed: Timmy's recent journal entries, scrolling in real time as he writes them.
  • Spectator chat: Viewers talk to each other. Timmy does NOT see this chat by default (paying tiers change this).
  • Viewer count: How many people are watching.
  • Injection history: Log of recent injections with spectator handle and what they did.

Requirements

  • HTMX + WebSocket architecture
  • Real-time updates without full page reloads
  • Responsive design (desktop + mobile)
  • Deployed at a public URL

Exit Criterion

10 concurrent spectators watching Timmy explore Balmora, with journal entries updating live.

Source

project-morrowind-phases-5-10.pdf — Phase 5, Web Frontend

## Scope Build the spectator web frontend as a single page using HTMX + WebSocket. ## Components - **The stream**: Central, dominant. Full video with audio. - **Vitals sidebar**: Health, magicka, fatigue, current cell, time of day. Pulled from perception JSON via WebSocket. - **Journal feed**: Timmy's recent journal entries, scrolling in real time as he writes them. - **Spectator chat**: Viewers talk to each other. Timmy does NOT see this chat by default (paying tiers change this). - **Viewer count**: How many people are watching. - **Injection history**: Log of recent injections with spectator handle and what they did. ## Requirements - HTMX + WebSocket architecture - Real-time updates without full page reloads - Responsive design (desktop + mobile) - Deployed at a public URL ## Exit Criterion 10 concurrent spectators watching Timmy explore Balmora, with journal entries updating live. ## Source project-morrowind-phases-5-10.pdf — Phase 5, Web Frontend
claude was assigned by Rockachopa 2026-03-22 23:34:36 +00:00
perplexity commented 2026-03-23 13:53:03 +00:00
Author
Collaborator
Copy Link

📋 Triage: Infrastructure — Deprioritized

Infrastructure/deployment work. Keep open, do as needed, but not blocking the harness.

Ref: #1076

📋 **Triage: Infrastructure — Deprioritized** Infrastructure/deployment work. Keep open, do as needed, but not blocking the harness. Ref: #1076
claude added the deprioritizedinfrastructure labels 2026-03-23 13:57:17 +00:00
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 deprioritized infrastructure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok kimi manus perplexity Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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