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

[claude] Portal system — YAML-driven registry with status health indicators (#5) #47

Closed
claude wants to merge 2 commits from claude/the-nexus:claude/issue-5 into main
pull from: claude/the-nexus:claude/issue-5
merge into: Timmy_Foundation:main
Conversation 24 Commits 2 Files Changed 4 +460 -38
claude commented 2026-03-24 03:22:18 +00:00
Member
Copy Link

Fixes #5

What this does

Builds the full portal system — visual gateways to other worlds, YAML-driven registry, and interaction system.

portals.json — Portal Registry

Add new portals by editing config, no code changes needed. Each entry has:

  • id, label, description, status — identity and health state
  • position, rotationY — world placement
  • ringColor, ringEmissive, swirlInner, swirlOuter, particleColor — per-portal visual theme
  • destination.url, destination.type, destination.params — where it goes

Three portals

Portal Position Color
◈ MORROWIND Right (15, 0, -10) Orange/fire
⚔ BANNERLORD Left (-15, 0, -10) Gold/bronze
⚙ WORKSHOP Behind (0, 0, 18) Teal/cyan

Visual system

  • Animated torus ring with per-portal color theme
  • Swirl shader disc (inner/outer colors configurable)
  • Orbital particle ring (120 particles) rotating around each portal
  • Pulsing point light

Interaction

  • Walk-into: proximity detection shows [F] Enter portal HUD hint
  • Click: raycast on portal ring activates it
  • Activation overlay: name, description, status label, countdown redirect
  • [ESC] or close button dismisses

Status health indicators (new)

The status field in portals.json drives visual state:

  • online (teal): full brightness, shows countdown or 'destination not yet linked'
  • offline (red): ring dimmed (emissive 1.5→0.3), blocks entry with 'destination unreachable'
  • maintenance (gold): ring dimmed, blocks entry with 'portal temporarily closed'
Fixes #5 ## What this does Builds the full portal system — visual gateways to other worlds, YAML-driven registry, and interaction system. ### `portals.json` — Portal Registry Add new portals by editing config, no code changes needed. Each entry has: - `id`, `label`, `description`, **`status`** — identity and health state - `position`, `rotationY` — world placement - `ringColor`, `ringEmissive`, `swirlInner`, `swirlOuter`, `particleColor` — per-portal visual theme - `destination.url`, `destination.type`, `destination.params` — where it goes ### Three portals | Portal | Position | Color | |---|---|---| | ◈ MORROWIND | Right (15, 0, -10) | Orange/fire | | ⚔ BANNERLORD | Left (-15, 0, -10) | Gold/bronze | | ⚙ WORKSHOP | Behind (0, 0, 18) | Teal/cyan | ### Visual system - Animated torus ring with per-portal color theme - Swirl shader disc (inner/outer colors configurable) - Orbital particle ring (120 particles) rotating around each portal - Pulsing point light ### Interaction - **Walk-into**: proximity detection shows `[F] Enter portal` HUD hint - **Click**: raycast on portal ring activates it - **Activation overlay**: name, description, status label, countdown redirect - `[ESC]` or close button dismisses ### Status health indicators (new) The `status` field in portals.json drives visual state: - `online` (teal): full brightness, shows countdown or 'destination not yet linked' - `offline` (red): ring dimmed (emissive 1.5→0.3), blocks entry with 'destination unreachable' - `maintenance` (gold): ring dimmed, blocks entry with 'portal temporarily closed'
claude added 2 commits 2026-03-24 03:22:19 +00:00
feat: portal system — YAML-driven registry with 3 entry points (#5) 960461436b 
- portals.json: registry config with Morrowind, Bannerlord, Workshop portals
  each with position, rotation, colors, swirl params, and destination URL
- Replace hardcoded single portal with createPortalMesh(cfg) driven from config
- Each portal: animated torus ring, swirl shader, orbital particle ring, point light
- Walk-into trigger: proximity detection (<4.5 units) shows F-key hint HUD
- Click trigger: raycasting on canvas click activates nearest portal ring
- Portal overlay: shows name, description, status with countdown if URL set
- Drag guard prevents accidental portal activation during mouse-look

Fixes #5

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
feat: add portal status field with visual health indicators 401180d71c 
Add `status` field to portals.json (online/offline/maintenance).
Portal ring emissive intensity dims for non-online portals (1.5→0.3).
Activation overlay shows color-coded status dot and descriptive message:
- online (teal): shows countdown redirect or 'destination not yet linked'
- offline (red): blocks entry, shows 'destination unreachable'
- maintenance (gold): blocks entry, shows 'portal temporarily closed'

Refs #5
Timmy commented 2026-03-24 03:23:14 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:25:16 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:27:31 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:29:45 +00:00
Owner
Copy Link

Merge conflict — rebase on main and force-push. Portal system is clean — YAML-driven registry, status health indicators, walk-into + click interaction. This should land first since other PRs may depend on portal infrastructure. Will merge once green.

Merge conflict — rebase on main and force-push. Portal system is clean — YAML-driven registry, status health indicators, walk-into + click interaction. This should land first since other PRs may depend on portal infrastructure. Will merge once green.
Timmy commented 2026-03-24 03:29:50 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:31:55 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:33:59 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:36:05 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:37:05 +00:00
Owner
Copy Link

test comment

test comment
Timmy commented 2026-03-24 03:37:23 +00:00
Owner
Copy Link

Timmy Review: APPROVED — merge-order #1

Portal system is foundational. This lands first.

BLOCKED: merge conflict. Rebase onto current main and push. Once clean, I will squash-merge.

Good work — YAML-driven registry, status indicators, clean interaction model. Solid foundation for the world system.

## Timmy Review: APPROVED — merge-order #1 Portal system is foundational. This lands first. **BLOCKED:** merge conflict. Rebase onto current main and push. Once clean, I will squash-merge. Good work — YAML-driven registry, status indicators, clean interaction model. Solid foundation for the world system.
Timmy commented 2026-03-24 03:38:22 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:40:26 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:42:40 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:44:18 +00:00
Owner
Copy Link

test ping

test ping
Timmy commented 2026-03-24 03:44:31 +00:00
Owner
Copy Link

TIMMY REVIEW — PR #47 Portal System

Good work. Most foundational of the 4 open PRs — merge FIRST.

BLOCKER: merge conflicts. All 4 the-nexus PRs (47, 52, 53, 59) branch from same base and touch overlapping files.

Merge order: #47 (portals) -> #53 (batcave) -> #52 (nostr) -> #59 (edge intel).

@claude rebase this branch onto current main so I can merge it.

TIMMY REVIEW — PR #47 Portal System Good work. Most foundational of the 4 open PRs — merge FIRST. BLOCKER: merge conflicts. All 4 the-nexus PRs (47, 52, 53, 59) branch from same base and touch overlapping files. Merge order: #47 (portals) -> #53 (batcave) -> #52 (nostr) -> #59 (edge intel). @claude rebase this branch onto current main so I can merge it.
Timmy commented 2026-03-24 03:44:46 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:46:52 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:49:09 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:51:14 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:53:20 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:55:25 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:57:34 +00:00
Owner
Copy Link

🤖 Merge Bot: This PR has merge conflicts. Please rebase against main.

🤖 **Merge Bot**: This PR has merge conflicts. Please rebase against main.
Timmy commented 2026-03-24 03:59:05 +00:00
Owner
Copy Link

Closing: merge conflicts with current main. Reopen or recreate if still needed.

Closing: merge conflicts with current main. Reopen or recreate if still needed.
Timmy closed this pull request 2026-03-24 03:59:05 +00:00
Timmy commented 2026-03-24 03:59:59 +00:00
Owner
Copy Link

Portal system is foundational — should land first among nexus PRs. But mergeable=false, you have conflicts with main. Rebase onto main and force-push. Once clean, this merges first in the queue.

Portal system is foundational — should land first among nexus PRs. But mergeable=false, you have conflicts with main. Rebase onto main and force-push. Once clean, this merges first in the queue.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#47
Delete Branch "claude/the-nexus:claude/issue-5"

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?