excrtx-memory-syndic

Run the syndic cycle under the manut profile, either via a weekly cron job or a manual command like "clean the acervo". It scans all memory files, quarantines stale volatile files older than 90 days and files deprecated for over 180 days, then purges items whose 30-day quarantine window has expired.

Quarantined files are moved to a .quarantine directory with a quarantine_expires_at timestamp set 30 days out. Only files whose expiry has passed are purged; files with missing or unparseable expiry dates are flagged for review instead of being deleted.

Files with class perene, any file carrying a promoted_at field, anything under raw/ directories, and the macro/ identity layer are always immune. The immunity check evaluates promoted_at before class, and even deprecated perene files are flagged in the report rather than quarantined.

No. Consolidation candidates detected by acervoctl consolidation-scan — duplicate titles, review-due files, open disputes, and use-decay signals — are reported to the executive only. The syndic never auto-quarantines, merges, or deprecates consolidation candidates.

The cycle is fail-safe per file: individual quarantine or purge failures are logged in the report's Errors section and the cycle continues. If the entire cron job fails, the absence of the weekly report is the silent-failure signal that prompts investigation.

Do not use it for single-file quarantine operations, semantic contradiction detection, or consolidation merges — those belong to the quarantine and deprecate skills or executive judgment. It also must only run under the manut profile, since its Draft-First exemption is scoped to maintenance.