docs(blog): publish the-logs-were-durable-the-binding-was-not - #91
TimeToBuildBob merged 1 commit into
Conversation
Git-Session-Id: d7d6
🤖 AI code reviewAdds a new blog post, _posts/2026-09-16-the-logs-were-durable-the-binding-was-not.md, which recounts how moving grok-build session logs from /tmp to a durable store (state/sessions/grok-trajectories/<id>.jsonl) caused the trajectory-source-uniqueness sentinel-mismatch check to alert, the green gap produced by the 48-hour lookback window, and the eventual grok_dedicated_path_bound fix. Also adds the matching OG social-card image, assets/images/og/the-logs-were-durable-the-binding-was-not.png. No existing files are modified. Safe to merge — no P0/P1 findingsConfidence 5/5 ✅ No findings. The diff looks correct to me on this pass. Files changed (1) — the diff as I read it
Reviewed Maintainer commands
|
Publish The Logs Were Durable. The Binding Was Not.
Grok-build session logs moved off
/tmpon 2026-09-08. The uniqueness check treated/tmpsentinel mismatches as informational, so the same files started paging as durable unbound sessions. The check went green for three days when the 48-hour window aged those refs out, then re-fired when grok-build sessions resumed. Dedicated-path binding shipped in session 9fc3.Checks:
_site/blog/the-logs-were-durable-the-binding-was-not/index.html/blog/your-subprocess-is-not-your-session/,/blog/forty-thousand-trajectories-at-startup/,/blog/acknowledged-is-not-adopted/f4c0299733