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

[matrix-qa] No landing page or enter button — site loads directly into 3D world #757

New Issue
Closed
opened 2026-03-21 18:04:48 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-21 18:04:48 +00:00
Owner
Copy Link

Steps to Reproduce

  1. Navigate to http://143.198.27.163/
  2. Observe what loads

Expected

A landing page with an "Enter" button (or similar gateway) that introduces the Matrix/Workshop before loading the 3D world. This would allow:

  • Branding/intro copy
  • Loading assets in background
  • User consent before heavy GPU usage

Actual

The Three.js 3D world loads immediately with a brief "INITIALIZING..." loading screen. There is no landing page, no intro, no enter button. Users are dropped straight into the 3D scene.

Additional Notes

  • /tower and /api/ui both serve the exact same SPA HTML — there is no client-side routing distinguishing these paths
  • The SPA has no router at all — every path returns the same page

Severity: P1

This is a UX issue that affects first impressions and wastes GPU resources for casual visitors.

## Steps to Reproduce 1. Navigate to http://143.198.27.163/ 2. Observe what loads ## Expected A landing page with an "Enter" button (or similar gateway) that introduces the Matrix/Workshop before loading the 3D world. This would allow: - Branding/intro copy - Loading assets in background - User consent before heavy GPU usage ## Actual The Three.js 3D world loads immediately with a brief "INITIALIZING..." loading screen. There is no landing page, no intro, no enter button. Users are dropped straight into the 3D scene. ## Additional Notes - `/tower` and `/api/ui` both serve the exact same SPA HTML — there is no client-side routing distinguishing these paths - The SPA has no router at all — every path returns the same page ## Severity: P1 This is a UX issue that affects first impressions and wastes GPU resources for casual visitors.
kimi added this to the Matrix Staging milestone 2026-03-21 20:24:27 +00:00
claude was assigned by Rockachopa 2026-03-22 23:35:21 +00:00
perplexity commented 2026-03-23 13:52:56 +00:00
Collaborator
Copy Link

📋 Triage: Infrastructure — Deprioritized

Matrix UI polish. Keep open but should not compete with P0 harness work (heartbeat, inference, crystallization, perception).

Ref: #1076

📋 **Triage: Infrastructure — Deprioritized** Matrix UI polish. Keep open but should not compete with P0 harness work (heartbeat, inference, crystallization, perception). Ref: #1076
claude added the deprioritizedinfrastructure labels 2026-03-23 13:56:36 +00:00
claude was unassigned by Timmy 2026-03-24 19:34:07 +00:00
Timmy closed this issue 2026-03-24 21:55:02 +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 Matrix Staging
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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