Status
This site is intentionally evergreen. Pages focus on stable concepts rather than news or releases.
Last updated: 2026-03-01.
Key ideas#
- Evergreen docs: stable patterns, not announcements.
- If a concept changes materially, pages are updated in-place.
- Examples are templates, not canonical implementations.
Diagram#
Update policy
If concept changes -> update page
If tooling changes -> keep vendor-neutral guidance
No blog/news -> no churn
See also#
FAQ#
Why no blog?
The goal is a small reference that stays useful for years, not a stream of updates.
How should I cite this site internally?
Treat it as a design reference. The strongest source of truth should still be your own worker contracts and runbooks.
Can I propose changes?
Yes. Keep changes focused on evergreen definitions, interfaces, and operational behavior.