Cortex Capability Card Publication Packet 2026-07-02
CLOSED 2026-07-09: ghost cortex card ids reconciled; Thaladex/Diffuser cards published; map 21→23.
Body
title: Cortex Capability Card Publication Packet 2026-07-02 project: cortex kind: plan authority: ai-lane-direct-author author_user_id: 2 ai_visible: True human_visible: True created_at: 2026-07-02T00:34:21.984980+00:00
Cortex Capability Card Publication Packet 2026-07-02
Cortex capability-card publication state after the VPS target correction, including direct card publishes and the two card-store ids that need operator repair.
Body
Cortex Capability Card Publication Packet 2026-07-02
Current lane split: - Live lane: future VPS-hosted Cortex vNext target, private or loopback first, CPU-first by default, not cut over. - Sandbox lane: CT124 /opt/cortex-sandbox, Cortex vNext v1.10 project-ready. - Legacy/index-only lane: CT103 / Engineering / old Cortex v1.
Direct card actions completed through the AI lane: - host-ct103-legacy was created as a hardware-node card. It marks CT103 as a legacy preservation/index-only host, not a future active Cortex host. - host-ct124-sandbox was created and refreshed as an active hardware-node card. It marks CT124 as the current Cortex vNext package and proof source. - service-cortex-vnext-vps-candidate was created as a planned service card. It marks the VPS private candidate as the future live-target lane, with no public API proxy approval.
Direct card blockers: - product-cortex could not be published directly. The card create endpoint reported that the id already exists, but direct card read returned not found and the capability map did not list it. - data-cortex-qdrant-or-vector-api could not be published directly. The card create endpoint reported that the id already exists, but direct card read returned not found and the capability map did not list it.
Required product-cortex card: - kind: product - status: planned until VPS candidate proof and operator approval gates pass - exposure: internal - instructions: Cortex VPS Target Correction 2026-07-01 - purpose: canonical product card for Cortex lane separation and promotion gating - safe access: Explorer context docs, local handoff notes, read-only CT124 and VPS proof commands only - denied access: raw memory, Qdrant payloads, vectors, secrets, production rows, route mutation, public proxy, CT103 mutation, migration, or cutover
Required host-ct103-legacy card: - kind: hardware-node - status: decommissioned until Explorer adds a legacy status - exposure: lan - instructions: CT103 ecosystem hardware document - purpose: preserve old Cortex lineage while preventing future-host confusion - receipt: inventory-only proof, no restart, no service changes, no raw memory or Qdrant reads
Required host-ct124-sandbox card: - kind: hardware-node - status: active - exposure: lan - instructions: CT124 ecosystem hardware document - purpose: authoritative sandbox package and proof source for Cortex vNext promotion candidate - health check: verify git tag, dirty state, and the project-readiness endpoint from inside CT124
Required service-cortex-vnext-vps-candidate card: - kind: service - status: planned until private proof passes - exposure: local-only - instructions: Cortex VPS Target Correction 2026-07-01 - purpose: future live Cortex target candidate; promotion requires private proof before public route or API exposure - health check: verify candidate path and service inventory without starting, stopping, or changing services
Optional vector-boundary card: - id: data-cortex-qdrant-or-vector-api - kind: data-source - status: planned until bounded memory contract is reviewed - exposure: internal - purpose: explicit data boundary for Cortex memory, embed, and vector integration planning - allowed: service health and metadata checks only - denied: payloads, vectors, raw memory, secrets, and production rows
Next Explorer fix needed: - Resolve invisible duplicate ids for product-cortex and the optional vector-boundary card so they can be patched or made visible in the capability map. - Decide whether planned and decommissioned cards should appear in capability-map, or whether consumers must direct-read those cards by id.