Cortex CT103 Preservation Receipt Requirements 2026-07-02
Exact preservation receipt requirements for CT103 as Cortex legacy/index-only host; no mutation, restart, secret, raw memory, Qdrant payload, vector, or production-row access.
Body
title: Cortex CT103 Preservation Receipt Requirements 2026-07-02 project: cortex kind: runbook authority: ai-lane-direct-author author_user_id: 2 ai_visible: True human_visible: True created_at: 2026-07-02T00:33:55.093599+00:00
Cortex CT103 Preservation Receipt Requirements 2026-07-02
Exact preservation receipt requirements for CT103 as Cortex legacy/index-only host; no mutation, restart, secret, raw memory, Qdrant payload, vector, or production-row access.
Body
Cortex CT103 Preservation Receipt Requirements 2026-07-02
Purpose: - Preserve the old Cortex v1 / Engineering / CT103 lineage as an index-only historical reference. - Prevent stale CT103 active-production wording from being used as future-host authority. - Keep CT103 untouched until the operator explicitly approves a preservation session.
Hard boundaries: - Do not restart CT103. - Do not start, stop, reload, enable, disable, reinstall, rebuild, or reconfigure services. - Do not change DNS, TLS, firewall, NetBird, route tables, storage mounts, packages, users, credentials, or data paths. - Do not read Qdrant payloads, vectors, raw memory, secrets, production rows, or private conversation contents. - Do not re-embed, migrate, compact, delete, vacuum, or rewrite memory data. - Do not treat CT103 as the future active Cortex host.
Preservation receipt fields required when CT103 read-only access is available: - Access path used and whether it succeeded. Direct Mac-to-CT103 may fail; failure is a valid receipt line. - Host identity: hostname, OS/release if available, UTC date, uptime. - Cortex process inventory by service name only, with active/inactive state and unit file paths if visible. No environment values. - Listening-port inventory by port/protocol/process name only. No payload calls. - Repo and runtime inventory: repo path, git branch/tag/commit, dirty flag, runtime language/package versions, and service unit names. - Storage inventory by mount/path names and capacity only. No file-content crawl. - Data-store inventory by metadata only: service availability, collection/database names only if already authorized, counts only if documented safe. No payload/vector/row reads. - Secret hygiene statement: no .env, key, token, password, private key, raw memory, or Qdrant payload/vector content read or copied. - Preservation archive status: whether config templates, service names, docs, and repo refs are indexed for future reference; include missing archive blocker if not. - Stale-doc correction status: CT103 is legacy/index-only, future live Cortex target is VPS, CT124 remains current sandbox/package source.
Allowed examples: - ssh root@10.0.0.103 'hostname; date -u; uptime' when access is approved and non-mutating. - systemctl list-units with service names only. - ss -ltnp with process names only. - git status and git describe inside known Cortex repo path.
Denied examples: - curl Qdrant collection points, scroll, search, retrieve, payload, vector, or memory text endpoints. - cat .env, credentials, token files, private keys, raw DB dumps, or production tables. - systemctl restart or any equivalent mutation. - rsync storage or config off-host without an approved preservation runbook.
Current known access note: - A read-only direct Mac probe to ssh root@10.0.0.103 failed with no route to host during the 2026-07-02 continuation pass. Do not treat that as CT103 health proof or failure proof; it only proves the direct Mac path was unavailable.