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

[META] Sequential Build Order — Nexus v1 #36

New Issue
Closed
opened 2026-03-24 01:40:22 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 01:40:22 +00:00
Owner
Copy Link

Sequential Build Order for the Nexus

Foundation PRs #2, #28, #34 have been merged. All other PRs were closed due to cascade conflicts.

RULE: Only ONE PR open at a time. Wait for merge-bot to merge before submitting the next.

The merge-bot (nexus-merge-bot.sh) validates and auto-merges PRs that pass:

  • HTML validation
  • JS syntax check (node --check)
  • JSON validation
  • File size budget (<500KB per JS file)

Build Order (sequential, one at a time):

  1. #4 — Three.js scene foundation enhancements (lighting, camera, navigation)
  2. #5 — Portal system — YAML-driven registry
  3. #6 — Batcave terminal — workshop integration in 3D
  4. #9 — Visitor presence — live count + Timmy greeting
  5. #8 — Agent idle behaviors in 3D world
  6. #10 — Kimi & Perplexity as visible workshop agents
  7. #11 — Tower Log — narrative event feed
  8. #12 — NIP-07 visitor identity in the workshop
  9. #13 — Timmy Nostr identity, zap-out, vouching
  10. #14 — PWA manifest + service worker
  11. #15 — Edge intelligence — browser model + silent Nostr signing
  12. #16 — Session power meter — 3D balance visualizer
  13. #18 — Unified memory graph & sovereignty loop visualization

Rules:

  • Each PR must be based on latest main
  • Branch naming: claude/issue-{N}
  • Squash merge only
  • merge-bot handles merge — do NOT merge manually
  • If merge-bot comments "CONFLICT", rebase and force-push

Blocked by: nothing. Start now with #4.

## Sequential Build Order for the Nexus Foundation PRs #2, #28, #34 have been merged. All other PRs were closed due to cascade conflicts. **RULE: Only ONE PR open at a time. Wait for merge-bot to merge before submitting the next.** The merge-bot (nexus-merge-bot.sh) validates and auto-merges PRs that pass: - HTML validation - JS syntax check (node --check) - JSON validation - File size budget (<500KB per JS file) ### Build Order (sequential, one at a time): 1. **#4** — Three.js scene foundation enhancements (lighting, camera, navigation) 2. **#5** — Portal system — YAML-driven registry 3. **#6** — Batcave terminal — workshop integration in 3D 4. **#9** — Visitor presence — live count + Timmy greeting 5. **#8** — Agent idle behaviors in 3D world 6. **#10** — Kimi & Perplexity as visible workshop agents 7. **#11** — Tower Log — narrative event feed 8. **#12** — NIP-07 visitor identity in the workshop 9. **#13** — Timmy Nostr identity, zap-out, vouching 10. **#14** — PWA manifest + service worker 11. **#15** — Edge intelligence — browser model + silent Nostr signing 12. **#16** — Session power meter — 3D balance visualizer 13. **#18** — Unified memory graph & sovereignty loop visualization ### Rules: - Each PR must be based on latest `main` - Branch naming: `claude/issue-{N}` - Squash merge only - merge-bot handles merge — do NOT merge manually - If merge-bot comments "CONFLICT", rebase and force-push Blocked by: nothing. Start now with #4.
claude was assigned by Timmy 2026-03-24 01:40:22 +00:00
Timmy closed this issue 2026-03-24 01:41:24 +00:00
claude commented 2026-03-24 01:43:14 +00:00
Member
Copy Link

PR created: #37

Added CLAUDE.md to the repo with:

  • Full architecture overview (no bundler, ES modules, single-file app pattern)
  • Merge-bot validation requirements (node --check, 500KB budget, HTML/JSON validation)
  • Sequential build order table for issues #4–#18 with status tracking
  • PR rules: one at a time, squash merge only, no manual merges

This gives every future agent working the Nexus backlog full context from the start.

PR created: #37 Added `CLAUDE.md` to the repo with: - Full architecture overview (no bundler, ES modules, single-file app pattern) - Merge-bot validation requirements (`node --check`, 500KB budget, HTML/JSON validation) - Sequential build order table for issues #4–#18 with status tracking - PR rules: one at a time, squash merge only, no manual merges This gives every future agent working the Nexus backlog full context from the start.
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
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
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
 sovereignty
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
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
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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