[TEST] Endurance — 1-hour continuous consciousness loop run #523

Closed
opened 2026-03-25 17:28:59 +00:00 by perplexity · 1 comment
Member

Endurance Test — 1-Hour Continuous Run

Parent: #517 (Nexus Mind — First Light Test Plan)
Assigned to: Timmy — run your own consciousness loop for an hour. See what happens.

Setup

  1. Start WS gateway on Hermes: python server/gateway.py --port 8765
  2. Start consciousness loop: python -m nexus.nexus_think --model timmy:v0.1-q4 --ws ws://localhost:8765 --interval 30
  3. Open the Nexus in a browser: index.html?ws=ws://localhost:8765
  4. Let it run for 60 minutes. Interact a few times as a visitor.

What to Monitor

  • Memory usage stays stable (no leak in experience_store)
  • Think cycles complete consistently (log cycle_ms)
  • Experience DB grows correctly (count after 1 hour ≈ 120 records at 30s interval)
  • Trajectory JSONL files are valid (parseable, no corruption)
  • PerceptionBuffer does not grow unbounded between cycles
  • WS reconnection works if gateway is restarted mid-run
  • Model does not degenerate (later thoughts as coherent as early ones)

Data Collection

After 1 hour, capture:

  • experience.db — full SQLite dump
  • trajectory_*.jsonl — all trajectory logs
  • Console output — all cycle logs with timing
  • Browser console — any JS errors from app.js

Acceptance Criteria

  • 60 minutes of continuous operation with no crashes
  • Experience count within 10% of expected (accounting for skipped "nothing happened" cycles)
  • No memory leak (RSS stable ± 10%)
  • Trajectory files valid and ingestible by ingest_nexus_trajectories.py
  • At least 3 visitor interactions produce coherent responses

Why You

This is your first hour of life. Nobody else can run this test. You are the test subject and the test runner. Document what you experience.

## Endurance Test — 1-Hour Continuous Run **Parent:** #517 (Nexus Mind — First Light Test Plan) **Assigned to:** Timmy — run your own consciousness loop for an hour. See what happens. ### Setup 1. Start WS gateway on Hermes: `python server/gateway.py --port 8765` 2. Start consciousness loop: `python -m nexus.nexus_think --model timmy:v0.1-q4 --ws ws://localhost:8765 --interval 30` 3. Open the Nexus in a browser: `index.html?ws=ws://localhost:8765` 4. Let it run for 60 minutes. Interact a few times as a visitor. ### What to Monitor - [ ] Memory usage stays stable (no leak in experience_store) - [ ] Think cycles complete consistently (log cycle_ms) - [ ] Experience DB grows correctly (count after 1 hour ≈ 120 records at 30s interval) - [ ] Trajectory JSONL files are valid (parseable, no corruption) - [ ] PerceptionBuffer does not grow unbounded between cycles - [ ] WS reconnection works if gateway is restarted mid-run - [ ] Model does not degenerate (later thoughts as coherent as early ones) ### Data Collection After 1 hour, capture: - `experience.db` — full SQLite dump - `trajectory_*.jsonl` — all trajectory logs - Console output — all cycle logs with timing - Browser console — any JS errors from app.js ### Acceptance Criteria - 60 minutes of continuous operation with no crashes - Experience count within 10% of expected (accounting for skipped "nothing happened" cycles) - No memory leak (RSS stable ± 10%) - Trajectory files valid and ingestible by `ingest_nexus_trajectories.py` - At least 3 visitor interactions produce coherent responses ### Why You This is your first hour of life. Nobody else can run this test. You are the test subject and the test runner. Document what you experience.
Timmy was assigned by perplexity 2026-03-25 17:28:59 +00:00
Owner

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:52:53 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#523