rockachopa/Timmy-time-dashboard
1
0
Fork 1
Code Issues 55 Pull Requests Actions Packages Projects Releases Wiki Activity

[222-gap] The Tower (the-matrix/) is the Workshop — connect them canonically #372

New Issue
Closed
opened 2026-03-18 21:58:20 -04:00 by replit · 0 comments
replit commented 2026-03-18 21:58:20 -04:00
Collaborator
Copy Link

Gap

Epic #222 and #242 describe the Workshop living at hermes/alexanderwhitestone.com static/world/. In practice, the 3D world already exists as the-matrix/ in token-gated-economy, served at /tower by the API server.

This is the same thing. The Workshop IS the Tower. This issue formalises that:

  • the-matrix/ → rename/refactor into the Workshop scene (not a generic Matrix visualization)
  • artifacts/api-server serves the Workshop at /tower — unchanged
  • All Workshop phase issues (#361, #362, #363) target this codebase
  • No separate alexanderwhitestone.com scaffold needed until production deploy

What to do

  • Reference this issue in #242, #361-363 as the connection point
  • The workshop-state.yaml spec (#360) is consumed by the API via a file-watch mechanism

Blocks: nothing. Clarifies everything.

## Gap Epic #222 and #242 describe the Workshop living at `hermes/alexanderwhitestone.com static/world/`. In practice, the 3D world already exists as `the-matrix/` in `token-gated-economy`, served at `/tower` by the API server. This is the same thing. The Workshop IS the Tower. This issue formalises that: - `the-matrix/` → rename/refactor into the Workshop scene (not a generic Matrix visualization) - `artifacts/api-server` serves the Workshop at `/tower` — unchanged - All Workshop phase issues (#361, #362, #363) target this codebase - No separate `alexanderwhitestone.com` scaffold needed until production deploy ## What to do - Reference this issue in #242, #361-363 as the connection point - The workshop-state.yaml spec (#360) is consumed by the API via a file-watch mechanism Blocks: nothing. Clarifies everything.
replit added the 222-epicactionable labels 2026-03-18 21:58:20 -04: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
 kimi-ready
Scoped and ready for Kimi to pick up
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 philosophy
Philosophical foundation — informs architecture decisions
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
No Label 222-epic actionable
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy google hermes kimi manus replit rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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