All runbooks
planuai-explorerredacted view

Cortex VPS Target Correction 2026-07-01

Correction for Cortex lane truth: CT103 is preservation and index only, CT124 is the current sandbox, and future live Cortex should be hosted on the VPS. Migration and cutover remain unauthorized.

Updated 2026-07-03·Freshness: Reference·No secret-like patterns were observed in this view.

Cortex VPS Target Correction 2026-07-01

Correction for Cortex lane truth: CT103 is preservation and index only, CT124 is the current sandbox, and future live Cortex should be hosted on the VPS. Migration and cutover remain unauthorized.

Body

title: Cortex VPS Target Correction 2026-07-01 project: uai-explorer kind: plan authority: ai-lane-direct-author author_user_id: 2 ai_visible: True human_visible: True created_at: 2026-07-01T23:58:37.735726+00:00

Cortex VPS Target Correction 2026-07-01

Correction for Cortex lane truth: CT103 is preservation and index only, CT124 is the current sandbox, and future live Cortex should be hosted on the VPS. Migration and cutover remain unauthorized.

Body

Cortex VPS Target Correction

This correction records current Cortex lane truth after an authenticated Explorer refresh and read-only runtime checks.

Corrected Lane Model

  • CT103 and Engineering are preservation and index-only for Cortex. They should not be treated as the future active Cortex host.
  • CT124 is the sandbox and current-work lane for Cortex vNext packaging.
  • Future live Cortex should be hosted on the VPS, private and CPU-first by default. Any public route or API exposure needs separate operator approval.
  • Fast local storage on Forge or Engineering is not a reason to host Cortex there. If future Cortex needs that storage class, use a bounded storage or vector API and prove the need with benchmarks first.
  • Migration and live cutover remain unauthorized.

Why This Exists

The currently readable Cortex product and hardware records still describe CT103 as active production and describe CT124 as an older sandbox state. Fresh runtime proof shows the sandbox has advanced to a project-ready review state while migration remains disabled. The records should be superseded or edited so future workers do not rebuild around CT103.

Required Follow-Up

  • Update the Cortex product and host records to show CT103 as legacy or preservation only.
  • Update the CT124 record to show the current project-ready sandbox state.
  • Add capability cards for Cortex, CT103 legacy, CT124 sandbox, and the VPS Cortex candidate.
  • Keep CT103 preservation-only until a separate approved preservation pass proves backup and index status.