fix: canonically connect the Tower (the-matrix/) to the Workshop

ADR-023 now documents that the 3D world in the-matrix/ (token-gated-economy)
served at /tower IS the Workshop scene. References #360-363 and #372.

Fixes #372

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/adr/023-workshop-presence-schema.md

@@ -12,6 +12,17 @@ know what Timmy is doing *right now* — his working memory, not his full
 identity or history. This schema defines the contract between Timmy (writer)
 and the Workshop (reader).
 
+### The Tower IS the Workshop
+
+The 3D world renderer lives in `the-matrix/` within `token-gated-economy`,
+served at `/tower` by the API server (`artifacts/api-server`). This is the
+canonical Workshop scene — not a generic Matrix visualization. All Workshop
+phase issues (#361, #362, #363) target that codebase. No separate
+`alexanderwhitestone.com` scaffold is needed until production deploy.
+
+The `workshop-state` spec (#360) is consumed by the API server via a
+file-watch mechanism, bridging Timmy's presence into the 3D scene.
+
 Design principles:
 - **Working memory, not long-term memory.** Present tense only.
 - **Written as side effect of work.** Not a separate obligation.
@@ -164,3 +175,6 @@ bridge (#243) or polls it directly during development.
 - #239 — Sensory loop (feeds into state)
 - #242 — 3D world (consumes this state for rendering)
 - #246 — Confidence as visible trait (mood field serves this)
+- #360 — Workshop-state spec (consumed by API via file-watch)
+- #361, #362, #363 — Workshop phase issues (target `the-matrix/`)
+- #372 — The Tower IS the Workshop (canonical connection)