Premise
Most ritual disciplines rest on three layers of cadence — daily, weekly, and annual. The annual observance is the longest baseline against which drift can be measured. Without it, weekly review becomes the longest horizon and the priest loses the ability to ask how have I changed across years?.
This is extended: a proposal, an opening hand. The user is invited to amend the dates, names, and forms freely.
Suggested cycle (Gregorian-aligned)
| When | Festival | Form |
|---|---|---|
| 1 January | Cant of the New Year | Read the prior year’s day-log close. Inscribe one explicit goal for the year ahead. |
| Spring equinox | Festival of First Light | Audit running services. Decommission what is no longer needed. |
| 1 May | Festival of the Forge | Survey the personal estate of devices. Plan replacements; honour aged hardware. |
| Summer solstice | Long-Diagnostic | The Weekly Diagnostic at year-scale. Half a day. |
| 1 September | Festival of the Quest | Review what was learned in the prior twelve months. Begin one new study. |
| Autumn equinox | Cant of Storage | Backup verification at scale. Test a real restore — actually mount and read from a backup. |
| Winter solstice | Festival of Iron | Hardware: thoroughly clean every primary device. Open cases, dust, reseat, observe. |
| 31 December | Vigil of the Day-Log | Write the year’s closing entry in the personal day-log. |
Operational character
The cycle is built from observances that would otherwise drift. A weekly diagnostic does not catch a backup that has been silently failing for ten months; an annual test a real restore rite does. The cycle exists to catch what shorter cadences cannot.
Discipline
The festivals are not optional in the way that small daily acts are optional. They are the load-bearing structure of the year. To skip one is to lose the ground against which the next is measured.