Beacon v2 / Beacon-next (Sandbox CT123)

Beacon-next is the pure-edge reverse-proxy modernization lane for the

Body

Beacon v2 / Beacon-next (Sandbox CT123)

Purpose

Beacon-next is the pure-edge reverse-proxy modernization lane for the production Beacon v1. It is a manifest-driven Rust/Axum sandbox on CT123, designed to be "safe to test, not safe to migrate." Cutover to production requires explicit operator approval for DNS movement, TLS issuance, live route edits, firewall changes, and service restart.

Current State

• Status: sandbox — Phase 4 verified; "safe to test, not safe to migrate."
• Host: CT123 (10.0.0.123).
• Service: beacon-next-sandbox.service — "Beacon-next sandbox edge model."
• Listen: 0.0.0.0:18080 (public sandbox edge), 127.0.0.1:19090 (admin).
• Source: /opt/beacon-next-sandbox/ (Rust workspace, axum 0.7.9, version 0.1.0).
• Manifest: /opt/bea....yaml (34 routes + 3 Satisfactory game forwards); refreshed draft at routes.yaml.refreshed-20260620.
• Explorer entities: 182 in the beacon-next namespace.
• Phase 4 commit: ccc837c1....
• Port 18080 collision: Beacon-next listens 0.0.0.0:18080 on CT123; the Rust UAI Explorer listens 100.119.16.109:18080 on Beacon. Same port, different hosts — discovery must be explicit.

Key Components / Locations

• Source: /opt/beacon-next-sandbox/ (CT123).
• Manifests: /opt/bea....yaml.
• Design docs: 30+ at /opt/beacon-next-sandbox/docs/ covering route parity, migration readiness, cutover rehearsal, observability, signoff, gate closure.
• Cross-compat design: manifests/...source_policy (copied_from_live vs excluded_from_live field lists).

Relationships

• Production counterpart: uai-doc-ecosystem-product-beacon-v1.
• Sandbox host: uai-doc-ecosystem-hardware-ct123.
• Cutover rehearsal owner: uai-doc-... (WS-C).

Status

sandbox — Phase 4 verified; production cutover operator-gated (G2).

See Also

• uai-doc-ecosystem-product-beacon-v1
• uai-doc-ecosystem-hardware-ct123
• uai-doc-... (WS-C)