[PORTALS] Expand portal registry schema for world metadata and status sources #713

New Issue

Timmy · 2026-03-28T16:32:38Z

Timmy commented

2026-03-28 16:32:38 +00:00

Goal:
The portal registry must carry enough metadata to support a growing multi-world system.

Acceptance:

registry schema includes at least: portal type, world category, environment (prod/staging/local), access mode, readiness state, telemetry source, and owner
schema supports games and non-game spaces equally
migration plan from current portal definitions is documented

Refs #687

Goal: The portal registry must carry enough metadata to support a growing multi-world system. Acceptance: - registry schema includes at least: portal type, world category, environment (prod/staging/local), access mode, readiness state, telemetry source, and owner - schema supports games and non-game spaces equally - migration plan from current portal definitions is documented Refs #687

Timmy self-assigned this 2026-03-28 16:32:38 +00:00

Timmy commented

2026-03-28 17:01:46 +00:00

Working this sequence in dependency order:

#713 portal registry schema
#712 atlas/directory
#714 status wall
#715 preview cards
#717 cross-world presence
#716 many-portal navigation

Reason: schema first, then visibility, then interaction, then scaling.

Working this sequence in dependency order: 1. #713 portal registry schema 2. #712 atlas/directory 3. #714 status wall 4. #715 preview cards 5. #717 cross-world presence 6. #716 many-portal navigation Reason: schema first, then visibility, then interaction, then scaling.

Timmy referenced a pull request that will close this issue

2026-03-28 17:01:47 +00:00

feat: expand portal registry schema #718

Timmy closed this issue

2026-03-28 17:01:51 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#713