A public record of what actually shipped.
Updates documents product, reliability, and company changes after they have a verifiable shipped or active operating state.
It is intentionally narrower than a roadmap: planned work, experiments, and internal discussion do not appear here as completed capability.
Release notes describe the verified scope at publication time. Product availability can still depend on the deployed product, tenant, integration, or release.
Newest first. Evidence before announcement.
Each entry identifies what changed, why it matters, and the public product surface where more context is available.
A public decision doctrine now explains the standards used when product, architecture, automation, evidence, safety, and commercial pressure pull in different directions.
A neutral maturity framework now explains when spreadsheets remain the right tool and when coordination responsibility starts to justify purpose-built software.
The HOS Evidence layer now documents verifiable first-party operating evidence from Kay House without presenting it as independent customer endorsement.
HOS now has a public implementation architecture covering moves from spreadsheets and PMS tools, data migration, and go-live readiness.
A control-plane workflow now classifies eligible failures and can perform one bounded recovery attempt for retry-safe workflows before escalation.
Eligible no-schema-change production promotions can now move through an owner-authorized release workflow with current-head gate enforcement and post-deploy closure verification.
The scheduled recovery control plane now covers both database backup evidence and physical Supabase Storage backup assurance.
Production assurance now runs on a recurring control-plane schedule with structured evidence and an incident lifecycle for meaningful failures.
We separate release history from roadmap intent.
An update belongs here only when the underlying work has a verifiable shipped or active operating state.
That means the public record can stay useful as the product evolves without requiring readers to distinguish promises from completed work.