GPT Review — Track A Residual Complete

Date: 2026-05-03

Verdict

Track A Legacy Vector Stabilization is accepted as COMPLETE for the current scope.

Evidence accepted from Agent report:

• Trigger/function persisted to deploy asset: /opt/incomex/migrations/track-a-residual-kb-vector-sync-trigger.sql.
• dot-vector-audit URL fixed and cron changed to report-only (--local, no --heal).
• Qdrant backup cron added at 03:00 and manual snapshot created.
• Full-pagination verification: orphan bug = 0, ghost bug = 0, correct-behavior ghosts separated.
• Health and legacy search smoke PASS.

Notes

One operational nuance remains: the trigger/function migration file protects migration-run/redeploy recovery, but does not automatically run on an existing PG volume unless the deploy process applies migrations. This is acceptable for current scope and should be tracked later as an operational deployment invariant, not as a blocker.

/kb/audit-sync still reports 7 ghosts because it includes a blank document_id plus six empty/short docs. Manual classification confirms 0 ghost bugs. Later audit UX should classify correct-behavior ghosts separately to avoid false alarms.

Directive to Opus

Move back to Track B: IU-0 full draft.

Do not reopen vector firefighting unless a new regression appears. In IU-0 full draft, preserve the finalized decisions:

1. Legacy KB vector remains untouched and stabilized.
2. IU vector uses a separate/parallel track, not mutation of production_documents.
3. Duplicate KB+IU content must be handled through collection separation and later search adapter/dedup.
4. Vector projection must be async delayed outbox, with PG CRUD hot path local-only.
5. Track A completion should be cited in §6 as the prerequisite now satisfied for continuing design.

Recommended next Opus task: write IU-0 full draft from OUTLINE-E.1, with emphasis on §5.A CRUD Performance Contract, §6 vector architecture, §8 slice editing workflow, and §10 pilot dogfooding. Keep it design-only; no DDL/code/P44-6 execution.