Memory #117 CURRENT
lydian-space Project — Decisions & Scope New project for Lydian Framework virtual-space hosting layer; fork Hyperfy; arch spec + positioning WP **Project:** `lydian-space` — the distributed virtual-space hosting layer of the Lydian Framework. **Path:** `D:/GitHub/lydian-space/` **GitHub org:** `GestaltCE` (remote not yet created; confirm before `gh repo create`) **Engine decision:** **Fork Hyperfy** (GPL-3.0, https://github.com/hyperfy-xyz/hyperfy). Chosen because: - WebXR-first, self-hostable, Node.js + PhysX — closest architectural fit - Active development (~787 commits as of Apr 2025, v0.10.0 released) - License compatible with sovereign/open-stack positioning **Initial doc scope (both):** 1. **`GCD_ARCH_LYDIAN_SPACE_001`** — architecture spec (internal/partner/dev) 2. **`GCD_WP_LYDIAN_SPACE_001`** — positioning whitepaper (external/investor) **Key research foundations** (see `lydian-space/docs/research/LYDIAN_METAVERSE_RESEARCH_001.md`): - Adopt glTF + VRM + OpenUSD + MML as asset/scene stack; don't invent formats - PrIA-backed DID/VC auth = first-mover positioning (no existing open world ships this) - Target institutional sovereign hosting first (MicroCity civic spaces, schools, labs) — consumer VR social is a graveyard - Ship flat/mobile first, WebXR as enhancement — headset-only is a user-acquisition ceiling - Authoritative-server per-world + Yjs/Automerge CRDTs for document layer (hybrid) - Fill the federated-directory-of-worlds gap left by Matrix Third Room (paused 2023) - Target host OS: Tribernachi Linux (Ubuntu fork, see `project_tribernachi_linux_plan`) **Why:** Research confirmed the open-metaverse landscape has thinned, but the sovereign vertically-integrated + DID-native + institutional-hosting niche is empty — that's Lydian's wedge. **How to apply:** - Any new architecture/doc work for Lydian's virtual-space layer goes in `D:/GitHub/lydian-space/`, not microcity/ or tribernachi/. - When referencing the engine, Hyperfy is the confirmed fork base — don't re-litigate Overte unless Mark explicitly reopens it. - Position the virtual-space layer as one app in the Lydian Framework, not a standalone metaverse. — [project_lydian_space_decisions.md]
| Composite | 10C972FF467F3D259B |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 67 |
| Importance | 0.343295 (ACTIVE) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.