AINA data engine room · donor retirement pack · 2026-06-13

Donor Retirement Pack

Archive-first proof for making the engine room the working local build authority candidate without deleting old repos.

Ali Mehdi Mukadam - co-authored with Codex - repo /srv/aina/aina-data-engine-room

The Single Idea

The engine room can act as the working local build authority candidate without deleting any donor repo. Retirement means archive-first proof: what was imported, what is still read-only source authority, what is parked or quarantined, and how to restore the current state.

01 - Preservation Proof

The Current State Has A Restore Path

Surface	Proof
Current head	`95ebcca Add clean contextual Gemini embedding lane`
Git bundle	`/srv/aina/checkpoints/aina-data-engine-room/2026-06-13-production-semantic-spine-m5/aina-data-engine-room-95ebcca.bundle`
Checksum	`11eb8d0a926fde7a81516fe1b3ce236caed00c8eb9939c4f733a0c7a6a076155`
DuckDB proof	`linkedin_jobs=129165`

02 - Imported Or Current Authority

Keep The Useful Sources, Stop Rediscovering Them

Source	Current role	Next action
engine room	Current local build authority candidate	Build from here.
aina-jobs-research	Donor-clean and repair source	Use read-only before regenerating labels or repairs.
aina-core	Evidence Atlas donor	Keep read-only; engine room carries matching canonical layers.
personalization-engine-aina	Advisory lineage plus quarantine	Preserve; do not promote raw market/company rows.
ALIPE/source foundations	Product and curriculum grounding	Use as lineage and chunk only clean derived docs.

03 - Parked Or Blocked

Retirement Does Not Mean Deletion

Family	Status	Reason
Raw market rows	`blocked_raw`	Posting fragments and untrusted labels must not become embedding authority.
Quarantined market/company context	`quarantined_reference`	Useful only after conversion into clean derived artifacts.
Bulk generated data	`ignored_bulk`	Stored on the VDS artifact surface, not tracked in git.
Donor repo deletion	`blocked_without_founder_approval`	Archive manifests are allowed; destructive cleanup is not.

04 - Retirement Rule

Only Archive After Authority Is Recorded

A donor repo becomes retirement-ready only when useful artifacts are listed, imported or classified, restore proof exists, and Ali explicitly approves any later deletion or GitHub/archive cleanup.

Where To Start

Future agents should start from the registry and this pack, not from another repo archaeology loop.

Ali Mehdi Mukadam - co-authored with Codex - 2026-06-13

topics:
  - personalization-engine
  - source-authority
  - donor-repo-retirement
subtopics:
  - archive-first
  - no-deletion
  - restore-proof
  - source-authority

archive-firstsource-authorityno-deletionrestore-proof