HappyFox Recurring Maintenance Registry
Aug 22, 2026
Internal recurring-maintenance registry.
Use this page to identify HappyFox articles whose content, schedules, external references, or procedures require regular review. This registry does not replace the canonical article owner. It records what must be watched, what triggers a review, which source is authoritative, and which downstream articles may need follow-up.
Use this page to identify HappyFox articles whose content, schedules, external references, or procedures require regular review. This registry does not replace the canonical article owner. It records what must be watched, what triggers a review, which source is authoritative, and which downstream articles may need follow-up.
Current baseline — August 21, 2026 project workday
Latest source exports:
Latest source exports:
External_Knowledge_Base_Export_20260822001336.csv and Internal_Knowledge_Base_Export_20260822001353.csv. The filenames are server-dated 20260822. Article 737 was unused in both exports and is available for this registry.
Contents
| How to Use This Registry | Living / Volatile Owners |
| Annual / Seasonal Review Pages | Change-Propagation Map |
| When to Add an Article | Maintenance Checklist |
How to Use This Registry
Not every article that mentions a school year should be rewritten every year. The maintenance model has two levels:
| Level | Meaning | Expected action |
|---|---|---|
| Living / volatile owner | The article intentionally contains current dates, current status, current form/version information, current external specifications, current report names/numbers, or current recurring schedules. | Update the canonical owner when the source changes, then inspect dependent articles for copied values or affected instructions. |
| Annual / seasonal review | The procedure is mostly durable, but should be rechecked at a predictable point in the year or when its underlying system behavior changes. | Verify the procedure still matches SIRAS and still routes to the living date/source owner. Edit only when needed. |
Maintenance principle:
Keep volatile facts in the smallest practical number of canonical living pages. Stable workflow articles should link to those owners instead of copying dates, schedules, report numbers, or status text unnecessarily.
Keep volatile facts in the smallest practical number of canonical living pages. Stable workflow articles should link to those owners instead of copying dates, schedules, report numbers, or status text unnecessarily.
Living / Volatile Owners
Internal maintenance owners
| Article | What changes | Review trigger / cadence | Authoritative source / downstream responsibility |
|---|---|---|---|
| 708 — CALPADS File Specifications & SEDS Component Maintenance Internal | SWDS / MEET / PLAN / SERV file-specification definitions, field meanings, code/value behavior, and current CDE source references. | Whenever CDE publishes a new or revised specification; perform a deliberate review before major Fall 1 / EOY cycles when specifications have changed. | Source: current official CDE CALPADS file specifications. Update 708 first, then review public component Articles 320–323 and downstream procedures that depend on changed definitions. |
| 709 — Internal guide for 362 Internal | Maintenance method for the public SIRAS SEDS Coordinator News / historical update page. | When a new SIRAS communication, release/history item, or superseding current procedure needs to be documented. | Public owner: 362 — SIRAS SEDS Coordinator News. Update the current procedure first; preserve history second. |
| 730 — CALPADS Report Maintenance Index Internal | CALPADS 16.xx / 17.x report numbers, names, cycle use, cadence, and documentation status. | Whenever CALPADS changes a report number/name/meaning or SIRAS changes which report is used for quarterly, Fall 1, or EOY monitoring. Review before each major reporting cycle. | Update 730 first, then review 400, 220, 234, 279, 280, and 462 plus any dedicated report-specific Show Me article. |
Public living pages
| Article | What must stay current | Review trigger / cadence | Maintenance boundary |
|---|---|---|---|
| 253 — Due Dates | SELPA reporting deadlines, task dates, Fall 1 / EOY 1 milestones, DRDP deadlines, approval/certification windows. | Whenever a new SELPA Due Dates document or amendment is issued; minimum deliberate review before Fall 1 and EOY work begins. | 253 is the deadline authority. Other workflow articles should link here rather than maintaining competing copies of exact dates. |
| 421 — System Event Calendar | Confirmed SIRAS system events: SIS import pauses, rollover windows, Training Server refreshes, DRDP archiving, ESY resets, academic-year query changes, and similar scheduled events. | Whenever an event date moves from recurring-window/TBD to confirmed, or a confirmed date changes. Review during annual rollover planning. | 421 owns exact system-event timing; procedure pages should explain what to do and link here for current dates. |
| 339 — SELPA IEP Rollover Schedule & Status | SELPA-specific confirmed rollover dates and status: not confirmed, scheduled, or complete. | During rollover season whenever a SELPA date is confirmed/changed and whenever SIRAS completes that SELPA's rollover. | 339 owns SELPA-specific rollover timing/status. 324/340/498/587 should route here rather than copying the schedule. |
| 380 — Office Hour Opportunities for SPED Admin Staff | Recurring office-hour schedules, joining information, cancellations, postponements, and current schedule-change notices. | Whenever an office-hour schedule/access link changes; remove expired cancellation/move notices after the affected date. | 380 owns the current schedule. 389 and 497 should link to 380 instead of copying office-hour times. |
| 29 — DRDP Help | Current DRDP cycle status, version/forms, open/closed/archive timing, provider-facing cycle guidance, and current external resources. | Before each Fall and Spring DRDP cycle; whenever the DRDP version/forms or SIRAS implementation changes. | Coordinate cycle wording with 52 and deadline authority 253. Do not leave old cycle status such as “Closed,” “TBD,” or a prior form version after the new cycle opens. |
| 52 — DRDP Help for Admins | Administrator-facing DRDP cycle status, current forms/version, exceptions list, deadlines, query expectations, and error-monitoring guidance. | Before each Fall and Spring cycle and whenever DRDP requirements/forms/exception handling change. | Maintain 29 and 52 as a coordinated pair; use 253 as the exact deadline authority where practical. |
| 362 — SIRAS SEDS Coordinator News | Dated SIRAS/SEDS communications, current-year notices, reporting locks, rollovers, implementation changes, and preserved historical context. | As communications occur and when a current notice becomes historical or is superseded. | Maintain through internal Article 709. Current work should route to current procedure articles; 362 preserves the dated history. |
Annual / Seasonal Review Pages
These pages are not necessarily living date authorities. They should be deliberately reviewed because their procedure or navigation is tied to a recurring annual cycle.
| Article | Why review it | Recommended review point | Keep volatile values in |
|---|---|---|---|
| 41 — SIRAS Admin- Calendar Events | Calendar-event types affect service-minute calculations and evaluation/interim countdown behavior; the article also tells administrators when to enter new holidays and progress-report dates. | Before summer rollover / end of each school year. Verify event types, calculation behavior, auto-save behavior, and annual timing recommendations still match SIRAS. | Local dates belong in the organization's SIRAS calendar; system-wide event dates belong in 421. |
| 209 — SEDS Coordinator Annual Planning Guide | Annual-cycle map and links need to reflect current architecture and the current cadence model. | Before the new school year and after major reporting-workflow changes. | 253 for deadlines; 421/339 for exact system/rollover dates; 730 for volatile report-number details. |
| 324 — Before Rollover – Preparation & Exceptions, 340 — After Rollover - Record Processing & Cleanup, 49 — Next Year's Data, and 498 — Beginning of School Year Help - Administrator Checklist | Core rollover procedures are durable but depend on current SIRAS behavior and annual navigation. | Review before rollover season and after any rollover/Next Year's Data behavior change. | 421 for system dates and 339 for SELPA-specific rollover schedule/status. |
| 587 — SIRAS Admin Fall Refresher | Fall training hub must route administrators to the current year's deadlines, system events, reporting changes, and current procedures. | Before fall refresher/training season. | 253, 421, 362, 400, 730, and canonical procedural owners. |
| 220 — Preparing for Fall 1 Census Day and 234 — Preparing for EOY in SIRAS | Reporting workflows should remain stable at the conceptual level but need review when CDE certification/reporting behavior changes. | Before the corresponding Fall 1 / EOY cycle and after material CDE/SIRAS reporting changes. | 253 for dates and 730 for volatile report-number/name details. |
Change-Propagation Map
| When this changes… | Update first | Then review / verify |
|---|---|---|
| CDE SWDS / MEET / PLAN / SERV specification | 708 | 320–323, archived-component explanations, CALPADS correction/reporting workflows that cite the changed field/value. |
| CALPADS report number, name, or cycle use | 730 | 400, 220, 234, 279, 280, 462, and any report-specific Show Me article. |
| SELPA deadline / certification window | 253 | 29/52 when DRDP timing is affected; 209/587/220/234 for copied dates or wording that should instead route to 253. |
| SIRAS system-event date | 421 | 209, 324, 340, 498, 587 and other seasonal guides; remove copied dates when a canonical link is sufficient. |
| SELPA rollover date/status | 339 | 324/340/498/587 routing and any current notices that mention a specific SELPA date. |
| DRDP cycle/version/forms | 29 + 52 | 253 deadlines, 362 dated notice/history, 587 fall refresher, and any screenshots/forms tied to the old DRDP version. |
| Office-hour schedule/cancellation | 380 | 389 and 497 should continue to route to 380 rather than copy the changing schedule. |
| New SIRAS/SEDS communication or historical notice | Current procedure first, then 362 using 709 | Confirm historical text does not become the only path to the current procedure. |
When to Add an Article to This Registry
During a new article or revision, consider 737 when the content includes any of the following:
- a current school-year or reporting-cycle date;
- a deadline, certification window, rollover date, or current status;
- “open,” “closed,” “TBD,” “confirmed,” “scheduled,” or similar cycle-state language;
- a current form/version name or assessment version;
- a current external specification, code set, report number, or report name;
- a recurring meeting/office-hour schedule or temporary cancellation notice;
- a current-year notice that will later become historical;
- a procedure whose behavior should be deliberately verified at a predictable annual/seasonal point.
Do not register every article that merely says “annual.”
Use 737 when there is a real maintenance obligation. Stable procedure articles should remain stable and point to the correct living owner for dates/status whenever possible.
Use 737 when there is a real maintenance obligation. Stable procedure articles should remain stable and point to the correct living owner for dates/status whenever possible.
Maintenance Checklist
- Confirm the source. Identify the authoritative external document, internal operational schedule, or canonical HappyFox owner.
- Update the living owner first. Do not begin by editing every downstream article that repeats the value.
- Search for copied volatile values. Check exact dates, report numbers, form versions, “open/closed/TBD” text, and old status language.
- Prefer routing over duplication. Replace copied values with a descriptive link to the canonical living page when the downstream article does not need the exact value to explain the task.
- Preserve role/workday navigation. Providers and administrators should still find the task in the language of their work.
- Preserve minimal-click resolution routing. Updating a date/source must not accidentally add unnecessary hops to a Show Me procedure.
- Verify links, screenshots, and video. Current-cycle media or forms must match the maintained version.
- Re-export and verify production. Do not treat the maintenance item as complete until the current production source reflects the change.
- Update 737 when the maintenance obligation changes. Add new living owners, remove retired obligations, and adjust cadence/source notes as the architecture evolves.
Simple rule:
737 tells us what needs recurring maintenance and what triggers it; 720 still tells us what owns what; 727 tells us how to write/update it; 728 tells us how the work moves to verified production.
737 tells us what needs recurring maintenance and what triggers it; 720 still tells us what owns what; 727 tells us how to write/update it; 728 tells us how the work moves to verified production.
