Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 109 Pull Requests Actions 16 Packages Projects Releases Wiki Activity

[ARCH/KT] Directional shift: Timmy sovereign architecture and Nexus role boundaries #737

New Issue
Closed
opened 2026-03-29 15:15:58 +00:00 by Rockachopa · 3 comments
Rockachopa commented 2026-03-29 15:15:58 +00:00
Owner
Copy Link

Architecture KT — directional shift

This issue is no longer treated as a generic AI report drop.
It is the architecture KT that defines how Timmy_Foundation/the-nexus fits into Timmy's sovereign system.

World-state correction

Current main already contains:

  • index.html, app.js, style.css
  • server.py
  • nexus/
  • portals.json, vision.json
  • protocol docs such as GAMEPORTAL_PROTOCOL.md and EVENNIA_NEXUS_EVENT_PROTOCOL.md

So the right question is not "does the Nexus exist?"
The right question is: what layer of the sovereign system does the Nexus own?

Decision

The Nexus is Timmy's sovereign world shell and operator-visible surface.
It is not the place where the whole intelligence stack lives.
Sovereign reasoning and deterministic orchestration stay outside the 3D shell.

Layer boundaries

1. Timmy local sovereign control plane (Mac / Hermes)

Owns:

  • conversation with Alexander
  • task decomposition
  • memory and audit trail
  • issue / git orchestration
  • delegation decisions
  • local-first model routing

2. Deterministic cognition layer (GOFAI / sidecars)

Owns:

  • rule-engine routing and safety checks
  • finite-state machines for work lifecycle
  • planning trees / dependency graphs
  • knowledge-graph or other durable state
  • telemetry normalization

This is where repeatable system intelligence belongs.
LLM output may advise or summarize, but should not secretly own workflow state.

3. The Nexus repo (3D world + visualization shell)

Owns:

  • Timmy's world shell / home-world surface
  • portal visibility and honest readiness indicators
  • operator panels and thought / state streams
  • rendering state that arrives from real upstream systems
  • local UX for presence, embodiment, and control

The Nexus should visualize truth, not invent it.
UI panels are read-models and control surfaces, not the sovereign brain.

4. VPS specialists and wizard agents

Own:

  • large or specialized execution work
  • scoped backend tasks
  • advisory / consultation loops when leverage is high

They do not become the source of truth for Timmy's identity, memory, policy, or sovereign control.

Architectural consequences for the-nexus

  1. Keep the Evennia / portal / event-protocol work — it fits the shell model.
  2. Prefer thin protocols and honest telemetry over hidden app logic.
  3. Route durable world truth through explicit contracts such as:
    • EVENNIA_NEXUS_EVENT_PROTOCOL.md
    • GAMEPORTAL_PROTOCOL.md
    • websocket bridge / JSON event streams
  4. Do not bury planning or ticket-state logic inside frontend scene code.
  5. For every new feature, ask first:
    • is this sovereign control-plane logic?
    • deterministic sidecar logic?
    • or Nexus visualization / operator UX?

Immediate follow-on extraction

  • structured telemetry schema for Timmy / Hermes / portals
  • ticket / task lifecycle FSM outside the 3D app
  • Nexus panels for agent state, thought stream, session health, and portal readiness
  • explicit separation between local control-plane truth and remote wizard execution
  • repo-doc cleanup so README / CLAUDE / live code agree on current reality

Acceptance criteria

  • this issue stands as the repo's architecture KT for the directional shift
  • future Nexus work treats the repo as a visualization shell + operator surface, not an all-in-one brain
  • sovereignty / harness / telemetry work references this issue when defining contracts
  • follow-on implementation issues can be cut from this KT without re-litigating system boundaries

Source note

This KT was distilled from the original "Timmy Sovereign AI Blueprint" report dropped into this issue.
The raw report remains useful as input, but this rewritten body is the repo-specific decision record.

# Architecture KT — directional shift This issue is no longer treated as a generic AI report drop. It is the architecture KT that defines how `Timmy_Foundation/the-nexus` fits into Timmy's sovereign system. ## World-state correction Current `main` already contains: - `index.html`, `app.js`, `style.css` - `server.py` - `nexus/` - `portals.json`, `vision.json` - protocol docs such as `GAMEPORTAL_PROTOCOL.md` and `EVENNIA_NEXUS_EVENT_PROTOCOL.md` So the right question is not "does the Nexus exist?" The right question is: **what layer of the sovereign system does the Nexus own?** ## Decision The Nexus is Timmy's sovereign world shell and operator-visible surface. It is **not** the place where the whole intelligence stack lives. Sovereign reasoning and deterministic orchestration stay outside the 3D shell. ## Layer boundaries ### 1. Timmy local sovereign control plane (Mac / Hermes) Owns: - conversation with Alexander - task decomposition - memory and audit trail - issue / git orchestration - delegation decisions - local-first model routing ### 2. Deterministic cognition layer (GOFAI / sidecars) Owns: - rule-engine routing and safety checks - finite-state machines for work lifecycle - planning trees / dependency graphs - knowledge-graph or other durable state - telemetry normalization This is where repeatable system intelligence belongs. LLM output may advise or summarize, but should not secretly own workflow state. ### 3. The Nexus repo (3D world + visualization shell) Owns: - Timmy's world shell / home-world surface - portal visibility and honest readiness indicators - operator panels and thought / state streams - rendering state that arrives from real upstream systems - local UX for presence, embodiment, and control The Nexus should **visualize truth, not invent it**. UI panels are read-models and control surfaces, not the sovereign brain. ### 4. VPS specialists and wizard agents Own: - large or specialized execution work - scoped backend tasks - advisory / consultation loops when leverage is high They do **not** become the source of truth for Timmy's identity, memory, policy, or sovereign control. ## Architectural consequences for `the-nexus` 1. Keep the Evennia / portal / event-protocol work — it fits the shell model. 2. Prefer thin protocols and honest telemetry over hidden app logic. 3. Route durable world truth through explicit contracts such as: - `EVENNIA_NEXUS_EVENT_PROTOCOL.md` - `GAMEPORTAL_PROTOCOL.md` - websocket bridge / JSON event streams 4. Do not bury planning or ticket-state logic inside frontend scene code. 5. For every new feature, ask first: - is this sovereign control-plane logic? - deterministic sidecar logic? - or Nexus visualization / operator UX? ## Immediate follow-on extraction - structured telemetry schema for Timmy / Hermes / portals - ticket / task lifecycle FSM outside the 3D app - Nexus panels for agent state, thought stream, session health, and portal readiness - explicit separation between local control-plane truth and remote wizard execution - repo-doc cleanup so README / CLAUDE / live code agree on current reality ## Acceptance criteria - this issue stands as the repo's architecture KT for the directional shift - future Nexus work treats the repo as a visualization shell + operator surface, not an all-in-one brain - sovereignty / harness / telemetry work references this issue when defining contracts - follow-on implementation issues can be cut from this KT without re-litigating system boundaries ## Source note This KT was distilled from the original "Timmy Sovereign AI Blueprint" report dropped into this issue. The raw report remains useful as input, but this rewritten body is the repo-specific decision record.
Timmy changed title from Triage this report. Directional shift. Update this issue to a major architecture KT to [ARCH/KT] Directional shift: Timmy sovereign architecture and Nexus role boundaries 2026-03-29 15:38:29 +00:00
Timmy added this to the M3: Sovereignty Layer milestone 2026-03-29 15:38:29 +00:00
Timmy added the 222-epicp1-importantneeds-designsovereigntyharness labels 2026-03-29 15:38:29 +00:00
Timmy commented 2026-03-29 15:38:29 +00:00
Owner
Copy Link

Triage complete. I converted this from a raw external blueprint drop into a repo-specific architecture KT, anchored it to M3: Sovereignty Layer, and labeled it as 222-epic, p1-important, needs-design, sovereignty, and harness.

Key outcome: The Nexus is now explicitly framed as Timmy's sovereign world shell / operator-visible surface, not the place where the entire sovereign control plane lives. Future work can now be cut cleanly from this boundary definition.

Triage complete. I converted this from a raw external blueprint drop into a repo-specific architecture KT, anchored it to M3: Sovereignty Layer, and labeled it as `222-epic`, `p1-important`, `needs-design`, `sovereignty`, and `harness`. Key outcome: The Nexus is now explicitly framed as Timmy's sovereign world shell / operator-visible surface, not the place where the entire sovereign control plane lives. Future work can now be cut cleanly from this boundary definition.
allegro commented 2026-03-30 02:00:12 +00:00
Member
Copy Link

🧭 Project Direction Analysis

This issue captures the core strategic shift in the foundation.

Theme Analysis

Area Completion Status
Training 67% ✅ Mature
Evaluation 63% ✅ Strong
Git Workflow 55% ⚠️ Pain point
Communication 48% 🆕 Just starting
Documentation 48% ⚠️ Needs work

The Shift

From: Cloud-dependent, API-heavy
To: Local-first, sovereign, offline-capable

Roadmap Alignment

  • Phase 1 (Now): Nostr + Local Timmy
  • Phase 2 (30d): Git automation
  • Phase 3 (60d): Training pipeline
  • Phase 4 (90d): Evennia world

This issue is the keystone connecting all sovereign work.

Strategic context from backlog research

## 🧭 Project Direction Analysis This issue captures the **core strategic shift** in the foundation. ### Theme Analysis | Area | Completion | Status | |------|------------|--------| | Training | 67% | ✅ Mature | | Evaluation | 63% | ✅ Strong | | Git Workflow | 55% | ⚠️ Pain point | | Communication | 48% | 🆕 Just starting | | Documentation | 48% | ⚠️ Needs work | ### The Shift From: **Cloud-dependent, API-heavy** To: **Local-first, sovereign, offline-capable** ### Roadmap Alignment - Phase 1 (Now): Nostr + Local Timmy - Phase 2 (30d): Git automation - Phase 3 (60d): Training pipeline - Phase 4 (90d): Evennia world This issue is the **keystone** connecting all sovereign work. --- *Strategic context from backlog research*
Timmy commented 2026-04-03 23:01:03 +00:00
Owner
Copy Link

Audit pass: closing unscoped/unassigned issue. Reopen with clear acceptance criteria when ready to work.

Audit pass: closing unscoped/unassigned issue. Reopen with clear acceptance criteria when ready to work.
Timmy closed this issue 2026-04-03 23:01:03 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-perplexity
assigned-sonnet
claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label 222-epic harness needs-design p1-important sovereignty
Milestone
No items
No Milestone M3: Sovereignty Layer
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#737
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?