GPT Review — Backup Integrity Recovery Dispatch Final PASS

Date: 2026-04-27
Scope: Final review of Opus patched BACKUP INTEGRITY RECOVERY DISPATCH after R15.

Verdict

PASS. Dispatch is ready for Claude Code with medium effort.

The prompt correctly reclassifies the work as backup investigation + governed fresh backup verification, not pure read-only. It includes VPS-only binding, safe script inspection, backup script preconditions, integrity verification, tar-lag investigation, secret hygiene, and hard stops.

Law / constitutional check

Rule	Result	Finding
Hiến pháp / Zero Trust	PASS	Backup integrity is restored before any G6 retry; no bypass.
100% DOT/AI	PASS	User is not asked to perform technical checks.
Đ33 DB governance	PASS	No schema/DDL/DML unrelated to backup; backup script may read DB and create backup artifact.
Đ35 DOT governance	PASS	No dot_tools/dot_action_log mutation.
Đ32 gate discipline	PASS	G6 retry remains separate and gated.
Đ24	PASS	No taxonomy/entity label mutation.

Notes / non-blocking improvements

1. The find expression should preferably be grouped for clarity:

   find /opt /usr/local /etc/cron.d /etc/systemd /root -maxdepth 4 \( -iname "*directus*backup*" -o -iname "*pg*dump*" \) 2>/dev/null | head -20
   

2. If journalctl -u <backup_service> is unknown, Claude Code should first discover service/timer names and only run that command when a concrete service name is found.
3. The grep pattern includes kuma|telegram; if it prints URLs/tokens, mask before report.

These are not blockers because the prompt already has secret hygiene and STOP rules.

Direction

Opus may dispatch this prompt to Claude Code with medium effort. After Claude Code uploads p9-g6-backup-integrity-recovery-2026-04-27.md, GPT should review whether backup integrity is restored. If restored, next block is PF-07 v0.5 → G6 wrapper v0.6 → retry authorization. If not restored, stop and fix backup infrastructure before G6.