freeshard-failure-archaeology

A post-mortem incident chronicle records historical outages and rejected architectural decisions within the Freeshard project. It documents major failures like rclone backup issues and Traefik proxy incidents to prevent repeating past technical mistakes.

To prevent rclone backup failures, review the archived incident chronicle for known traps like incorrect log parsing and silent CronTask death. It provides specific standing rules to ensure your backup pipeline implementation avoids previously resolved bugs.

Freeshard uses embedded OIDC because Authelia was a rejected architectural decision. Reviewing the decision guardrails reveals this settled choice, preventing wasted development effort on abandoned integration paths.

Check standing rules by triggering the failure archaeology skill to review known failure patterns before modifying database subsystems. This ensures your infrastructure migration complies with established guardrails and avoids historical database migration issues.

The limitation is that historical records only prevent re-introducing resolved bugs and abandoned paths; they do not address novel infrastructure issues. You must still actively debug new incidents while using the chronicle to avoid repeating known Traefik or rclone failures.