Fixes#1356. Single-threaded HTTPServer queued all requests sequentially,
causing 60% timeout rate with 10 concurrent users.
Changes:
- world/multi_user_bridge.py: Added ThreadingHTTPServer class with
ThreadingMixIn + daemon_threads, swapped server instantiation
- multi_user_bridge.py: Fixed server instantiation to use the already-
defined ThreadingHTTPServer class (was using HTTPServer by mistake)
Impact: 10/10 concurrent users complete (~5s avg) vs 4/10 before.
2026-04-13 18:21:59 -04:00
4 changed files with 497 additions and 56 deletions
- JSON configuration files like `portals.json` and`vision.json`
It does **not** currently contain an active root frontend (`index.html`, `app.js`, `style.css`).
It does **not** currently contain an active root frontend such as:
-`index.html`
-`app.js`
-`style.css`
-`package.json`
Serving the repo root today shows a directory listing, not a rendered world.
## One Canonical 3D Repo
`Timmy_Foundation/the-nexus` is the **only** canonical 3D repo.
`Timmy_Foundation/the-nexus` is the only canonical 3D repo.
In plain language: Timmy_Foundation/the-nexus is the only canonical 3D repo.
The legacy browser app at `/Users/apayne/the-matrix` is source material for migration, not a second repo to keep evolving in parallel. Useful work from it must be audited and migrated here.
The old local browser app at:
-`/Users/apayne/the-matrix`
See `LEGACY_MATRIX_AUDIT.md`.
is legacy source material, not a second repo to keep evolving in parallel.
Useful work from it must be audited and migrated here.
## Why This Matters
See:
-`LEGACY_MATRIX_AUDIT.md`
We do not want to lose real quality work. We also do not want to keep two drifting 3D repos alive by accident.
## Why this matters
The rule:
- Rescue good work from legacy Matrix
- Rebuild inside `the-nexus`
- Keep telemetry and durable truth flowing through the Hermes harness
We do not want to lose real quality work.
We also do not want to keep two drifting 3D repos alive by accident.
## Active Migration Backlog
The rule is:
- rescue good work from legacy Matrix
- rebuild inside `the-nexus`
- keep telemetry and durable truth flowing through the Hermes harness
- Hermes is the sole harness — no external gateway dependencies
still contains the old root browser files (`index.html`, `app.js`, `style.css`, `package.json`, tests/), so it is a useful in-repo reference point for what existed before the later deletions.
## Active migration backlog
-`#684` sync docs to repo truth
-`#685` preserve legacy Matrix quality work before rewrite
-`#686` rebuild browser smoke / visual validation for the real Nexus repo
-`#687` restore a wizardly local-first visual shell from audited Matrix components
-`#672` rebuild the portal stack as Timmy → Reflex → Pilot
-`#673` deterministic Morrowind pilot loop with world-state proof
-`#674` reflex tactical layer and semantic trajectory logging
-`#675` deterministic context compaction for long local sessions
## What gets preserved from legacy Matrix
High-value candidates include:
- visitor movement / embodiment
- chat, bark, and presence systems
- transcript logging
- ambient / visual atmosphere systems
- economy / satflow visualizations
- smoke and browser validation discipline
Those pieces should be carried forward only if they serve the mission and are re-tethered to real local system state.
## Running Locally
There is no root browser app on current `main`. Do not static-serve the repo root expecting a world.
### Current repo truth
You can run:
-`python3 server.py` — local websocket bridge
- Python modules under `nexus/` — heartbeat / cognition work
There is no root browser app on current `main`.
Do not tell people to static-serve the repo root and expect a world.
The browser-facing Nexus must be rebuilt through the migration backlog using audited Matrix components.
### Branch Protection & Review Policy
## Branch Protection & Review Policy
**All repositories enforce these rules on `main`:**
| Rule | Status |
|------|--------|
| Require Pull Request for merge | ✅ Enabled |
| Require 1 approval before merge | ✅ Enabled |
| Dismiss stale approvals on new commits | ✅ Enabled |
| Require CI to pass (where CI exists) | ⚠️ Conditional |
| Block force pushes to `main` | ✅ Enabled |
| Block deletion of `main` branch | ✅ Enabled |
**All repositories enforce:**
- PRs required for all changes
- Minimum 1 approval required
- CI/CD must pass
- No force pushes
- No direct pushes to main
**Default reviewers:**
-`@perplexity`— all repositories (QA gate)
-`@Timmy`— `hermes-agent` only (owner gate)
-`@perplexity`for all repositories
-`@Timmy`for nexus/ and hermes-agent/
**CI status:**
-`hermes-agent`: ✅ Active
-`the-nexus`: ⚠️ Runner pending (#915)
-`timmy-home`: ❌ No CI
-`timmy-config`: ❌ Limited CI
**Enforced by Gitea branch protection rules**
See [CONTRIBUTING.md](CONTRIBUTING.md) for full details.
### What you can run now
-`python3 server.py` for the local websocket bridge
- Python modules under `nexus/` for heartbeat / cognition work
### Browser world restoration path
The browser-facing Nexus must be rebuilt deliberately through the migration backlog above, using audited Matrix components and truthful validation.
---
*One 3D repo. One migration path. No more ghost worlds.*
# The Nexus Project
## Branch Protection & Review Policy
**All repositories enforce these rules on the `main` branch:**
| Rule | Status | Rationale |
|------|--------|-----------|
| Require PR for merge | ✅ Enabled | Prevent direct commits |
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
