Open standards & artifacts for accountable systems.

Specification sheet

Permanent link /mechanisms/patterns/maintenance-windowing

MEC-03 Maintenance windowing

Schedule improvements, monitoring, and resourcing using a visible stewardship window.

Where it fits

Filters and handoffs

Tagged for Governance, Policy with validator handshakes. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.

Scholarly metadata

Authorship

Contact: research@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Jan 9, 2026
  • Version: v1.1.0
  • DOI: Pending Zenodo deposit

License: CC BY-SA 4.0

Credit Ethotechnics Institute, include the page title + version, and link to the canonical permalink.

Archive snapshot: Wayback capture

Changelog

  • v1.1.0 · 2026-01-09 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · 2025-12-03 — Initial public mechanisms release.

Copy citation (APA/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.1.0

Last updated

Jan 9, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Institute Research Team. (2026). MEC-03 Maintenance windowing. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/maintenance-windowing

MLA

Ethotechnics Institute Research Team. "MEC-03 Maintenance windowing." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/maintenance-windowing.

Chicago

Ethotechnics Institute Research Team. "MEC-03 Maintenance windowing." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/maintenance-windowing.

BibTeX

@misc{mechanism_maintenance-windowing,
  title={MEC-03 Maintenance windowing},
  author={Ethotechnics Institute Research Team},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/maintenance-windowing},
  version={v1.1.0}
}

RIS

TY  - WEB
TI  - MEC-03 Maintenance windowing
AU  - Ethotechnics Institute Research Team
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/maintenance-windowing
ER  -

Specification overview

At-a-glance details for planning and handoffs.

Capture the scope, assets, and validator handshakes before diving into the steps.

Spec essentials

What ships with this mechanism

  • 3 steps with checklist-ready owners.
  • 3 reusable assets for briefs and runbooks.
  • 4 reuse-ready snippet blocks.
  • 3 glossary anchors for shared terms.

Filters & validators

Where this spec sits in the system

Tagged in 2 filters with 1 linked validators.

Glossary anchors

Link back to the definitions.

Jump to the glossary terms that frame this mechanism.

Steps

Put the mechanism in motion.

Start with the field cues, then use the assets to keep the work legible.

3 steps with checklist-ready owners, plus linked assets for handoffs.

Assets

Keep outputs reusable.

Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.

Window calendar

Shared schedule with owners, coverage, and success criteria.

Comms templates

Prewritten updates for high, medium, and low-risk changes tied to roles.

Fallback matrix

Lists degraded modes and who is paged when dependencies fail.

Reuse-ready snippets

Copy policy, audit, and incident language.

Use these snippets in requirements, audits, and postmortems with the mechanism permalink.

Policy requirement

Policy requirement (MEC-03 Maintenance windowing)
- Publish stewardship windows with named owners, success criteria, and rollback authority.
- Require comms cadences by risk tier before shipping changes.
Reference: https://ethotechnics.org/mechanisms/patterns/maintenance-windowing

Product requirement

Product requirement (MEC-03)
- Release plans include a window ID and owner in change tickets.
- Status updates and fallback behavior are visible to affected users.

Audit evidence checklist

Audit evidence checklist (MEC-03)
[ ] Window calendar lists owners, coverage, and success criteria.
[ ] Comms templates are published by risk level and audience.
[ ] Fallback matrix confirms safe degraded modes for dependencies.

Postmortem trigger

Postmortem trigger (MEC-03)
Trigger review if changes ship outside the stewardship window or without comms.

Example usage

Coordinating a stewardship sprint

A concrete scenario to help teams see how the pieces fit together.

How it plays out

Engineering and operations publish a two-week window with a fallback matrix, schedule status updates by audience, and rehearse degraded-mode protocols before shipping changes.

Anti-patterns

Common failure cases and counterfactuals

Use these to avoid superficial compliance and clarify what success requires.

Stewardship without owners

Publishes a maintenance window without naming accountable owners or success criteria.

Counterfactual: Each window has a named owner, success criteria, and rollback authority.

False-positive warning: Shared ownership is fine if responsibilities are explicit and visible.

Silent maintenance

Ships changes without comms or status updates, leaving users unaware of risks.

Counterfactual: Comms are published by audience and risk tier, with fallback coverage noted.

False-positive warning: Emergency patches can shorten comms, but they still require an after-action log.

Validators

Pair validators with this mechanism.

Use these tools to size risk and keep the stewardship path visible.

Validator

Maintenance Simulator

Tabletop simulation that plays through outages, maintenance windows, and handoffs to stress-test coverage.