GPT Review — 20B-P2 Manifest and P3 Option Decision

Date: 2026-05-05 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed:

• knowledge/dev/laws/dieu44-trien-khai/reports/20b-p2-context-pack-kb-delete-manifest-dryrun-report.md
• knowledge/dev/laws/dieu44-trien-khai/reviews/opus-review-20b-p2-manifest-and-p3-proposal-2026-05-05.md

Verdict

20B-P2 PASS. Choose Option A with archive guard.

Decision

Proceed with Option A:

• Delete all 1,175 KB docs under context-pack/.
• Keep zero context-pack docs in KB/vector after purge.
• Before delete, archive the 8 missing_recovery docs from build 20260418-023221-0bfb97 to VPS filesystem backup.

Rationale

Option A is the cleanest and best aligned with the confirmed architecture:

• Runtime/agent consumers read context-pack from filesystem, not KB search.
• PG manifest is the audit source for normal builds.
• KB mirror is redundant and has caused severe vector pollution.
• Keeping 9 docs as anchor is unnecessary and risks preserving a special-case exception.
• If a KB anchor is needed later, it can be re-uploaded deliberately from filesystem/manifest under a new governed lifecycle.

Required 20B-P3 prompt

Opus should create:

knowledge/dev/laws/dieu44-trien-khai/prompts/20b-p3-context-pack-kb-purge-execution-prompt.md

Scope

Execute purge of context-pack KB docs using the P2 manifest.

Required steps

1. Read:

   • P2 dry-run report;
   • Opus review P2;
   • this GPT decision;
   • P1 report.

2. Reconfirm current list:

   • list documents under context-pack/;
   • expected roughly 1,175; if count differs, print diff and continue only if all docs are still under context-pack/ and no non-context docs appear.

3. Archive 8 missing_recovery docs before delete:

   • build 20260418-023221-0bfb97;
   • export full content + metadata to VPS filesystem, not KB;
   • suggested path: /opt/incomex/backups/context-pack-orphans/20260418-023221-0bfb97/
   • include a manifest file with document_id, title, metadata, checksum if possible;
   • verify archive has 8 files + manifest before delete.

4. Delete all docs under context-pack/ via Agent Data deleteDocument or available KB API.

   • Use batching if needed.
   • Log successes/failures.
   • If any delete fails, continue collecting failures, then report; do not retry endlessly.

5. Verify after delete:

   • list context-pack/ prefix count should be 0.
   • If not 0, list remaining document_ids.

6. Run search regression after purge using the 7 queries from vector hygiene report:

   • report top results;
   • context-pack share should be 0 in default KB search;
   • canonical docs should move up.

7. Upload report:

knowledge/dev/laws/dieu44-trien-khai/reports/20b-p3-context-pack-kb-purge-execution-report.md

Hard boundaries

• no DOT patch;
• no Đ43 patch;
• no cron;
• no filesystem cleanup beyond writing the orphan archive;
• no search API patch;
• no service restart;
• no Pack 2C/IU;
• no deletion outside context-pack/.

After P3

If purge succeeds and search regression improves, next is 20B-P4 filesystem retention / Đ43 lifecycle semantics, including kb_mirror_status truthfulness.