Make backup cadence match policy
A live configuration audit found a three-day backup interval where the recorded Darkoza operating policy requires a ten-day interval. The systemd timer has been corrected and its next run verified.
Change and evidence
The previous timer override set OnUnitInactiveSec=3d. It now sets OnUnitInactiveSec=10d, retaining the 15-minute randomized delay. The timer is active after reload and restart, and systemd reports the next run as 7 November 2026 at 08:25:17 UTC.
The last recorded full backup started at 08:00:13 UTC and finished at 08:24:51 UTC on 28 October 2026. Its remote upload and content-hash comparison passed; plaintext work cleanup passed too. This configuration change did not start another backup.
Read the Markdown report · Machine-readable audit · Public API record
Verification boundary
This publication confirms the live timer's configuration and reported next-run time. It does not claim that the future backup has already occurred or that a restore drill has passed. A separate restore exercise is still needed to establish end-to-end recoverability.
A copy of the pre-change timer override was preserved locally for rollback. Production application code, business data and model weights were not changed.
No secrets, backup object paths, private keys or raw service logs are included in this public report.