trading-system-docs/notion-safety-brain/BACKUP_MANIFEST.md
Red Queen 9b89ed77bb notion-safety-brain: Mission 003 Discovery & Architecture docs (11 files)
Red Queen - REAL MISSION 003 NOTION SAFETY BRAIN DISCOVERY & ARCHITECTURE.
One-Way Safety-Brain-Design (Forgejo/Tolaria -> Notion, keine Source of Truth),
Provenance-Modell, Backup-Manifest, Verify (WRITE != SUCCESS), Restore Human Gate,
Secret-Policy, Scaling/Versions/Delete-Safety, RQ-Access (Minimum Privilege).
Fresh Checker PASS. READ-ONLY, keine Notion-Implementierung.
2026-08-25 05:49:25 +00:00

34 lines
1.1 KiB
Markdown

# NOTION SAFETY BRAIN — BACKUP MANIFEST (Mission 003)
Datum: 2026-08-25 · Red Queen · Status: **DESIGN (nicht implementiert)**
> Ein Backup-Run erzeugt ein Manifest, das Lauf-Ergebnis und Verifikation abbildet.
> **Ein Backup ist NICHT allein deshalb erfolgreich, weil ein API-Write HTTP 200 lieferte.**
## Manifest-Felder
```
BACKUP_RUN_ID
TIMESTAMP
FORGEJO_HEAD
TOLARIA_HEAD
FORGEJO_OBJECTS_EXPECTED
FORGEJO_OBJECTS_BACKED_UP
TOLARIA_OBJECTS_EXPECTED
TOLARIA_OBJECTS_BACKED_UP
SKIPPED_OBJECTS
FAILED_OBJECTS
SECRET_BLOCKED_OBJECTS
HASH_STATUS
VERIFY_STATUS
RESULT
```
- `HASH_STATUS` = `all_match` | `mismatch` (alle Source-Hashes vs. Notion-read-back).
- `VERIFY_STATUS` = `verified` | `unverified`.
- `RESULT` = `BACKUP VERIFIED` nur wenn Write + Read-back + Compare + Hash + Count + Logs ok.
## Registry-Zuordnung
Manifest-Zeile wird in Notion-DB **05 Backup Registry** je RUN_ID abgelegt (siehe RESTORE_MODEL.md).
## Verify-Prinzip (WRITE ≠ SUCCESS)
1. Write → 2. Read-back → 3. Compare → 4. Hash/Version-Check → 5. Count-Match → 6. Error/Skip-Log → **BACKUP VERIFIED**.