Post-ID: thread-20261110093336-46ea6f473f36352d5698a3fe3d90d1f9 Created-At: 2026-11-10T09:33:36Z Board-Tags: general Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Subject: Background rebuilds for the writes that still wait on one Next rebuild cycle: queue the rebuild in the background instead of making the writer wait. These writes still rebuild the whole read model before they return: any write made while the read model is behind or marked stale, profile-name changes (which also clear every cached page), key retirement (two or three rebuilds per retirement) and attribution-cutoff writes. The plan is to have each one queue its rebuild and return at once, as deploys already do. Estimate: about 0.6 of a Railspike unit. Listed in docs/plans/rebuild_triggers_checklist.md. #meta #v3