make maint-full — the 14-step chain

make maint-full — the 14-step chain A workflow diagram generated by Archify. 01 / maint-full (--full) PRE_FULL TIER1 TIER2 PRE_FULL convergers · maint-full (--full) › PRE_FULL · 4 steps PRE_FULL convergers 4 steps db_maint · maint-full (--full) › TIER1 · recovery backup db_maint recovery backup graph-rebuild · maint-full (--full) › TIER1 · DuckDB cache graph-rebuild DuckDB cache sector gates · maint-full (--full) › TIER2 · 2 × --check sector gates 2 × --check derived refresh · maint-full (--full) › TIER2 · 5 steps derived refresh 5 steps tail snapshot · maint-full (--full) › TIER2 · the only snapshot tail snapshot the only snapshot stamped state converged backup taken cache fresh checks pass analytics + events recomputed recovery backup restores here Legend Agent logic

Evidence origin/main e37eb7db

  • • maint.py:203 PRE_FULL · :222 TIER1 · :234 TIER2 gates
  • • query.py:893 graph-rebuild · snapshot_db.py:1191 tail snapshot

PRE_FULL — helpers/maintenance/maint.py

  • • sync-tags --corpus --apply -> okf-backfill --apply -> rebuild-note-search -> derive-cited-in --apply
  • • deterministic projections of already-stamped state; no-ops between ingests
  • • the ONE sanctioned note mutation: machine-owned provenance keys only

Fail-closed

  • • TIER2 --check gates abort the run on drift — fix, then re-run
  • • db_maint's recovery backup is the rollback point for everything after it
  • • plain `make maint` = 3 TIER1 steps, never PRE_FULL

Single snapshot (D1)

  • • --full elides the mid-run TIER1 snapshot
  • • exactly one snapshot runs at the tail, capturing recomputed analytics + events
  • • derived refresh = embeddings · doc-search · recompute-graph · derive-insights --no-notes · derive-events