Memory #114 CURRENT
Lydian Node — Unified Terminology "Lydian Node" is the umbrella term for the sovereign node bundle (Conductor + Clock + Wallet + PrIA + TribNet intelligence + Memory); use this name going forward Adopted 2026-04-19. Going forward, the integrated personal/institutional sovereign node — comprising Conductor (orchestrator), Clock (peering/time), Wallet (key + value custody), PrIA (identity), TribNet bridge (intelligence), and Memory Layer (prime-indexed store) — is collectively referred to as the **Lydian Node**. **Tiers of Lydian Node:** - MicroNode (64B, C₂³ authority, BLE/WiFi) — PWA mobile variant planned - EdgeNode (C₂² authority, multi-person SQLite) — ASUS G752VS is the next physical edge - (Future) Institutional / hosting-tier nodes inside Lydian Framework **Why:** Mark introduced the term 2026-04-19 to unify what had previously been referred to as "Conductor + services" or "the node." Naming it Lydian Node aligns the runtime bundle with the umbrella Lydian Framework. **How to apply:** - Use "Lydian Node" in future docs, commits, and conversation instead of splitting into per-service names, unless a specific subsystem is the subject. - Each Lydian Node is a deployable unit — Conductor is the orchestrator *inside* a Lydian Node, not a synonym for it. - Existing repo layout is unchanged (conductor/, Genesis-Platform-Identity-Startup/, Tribernachi-Memory-Layer/, etc.) — "Lydian Node" is a conceptual composition of those services, not a new repo. - When scoping remaining work for "the node," frame it as Lydian Node milestones (wallet, edge hardware, mobile micro-node, Claude Code integration, etc.). — [project_lydian_node_terminology.md]
| Composite | 5D8DD44C8008E702B |
| Project prime | 13 |
| Domain prime | 1F |
| 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.