A plan for publishing engineering sessions live on the site
A planning session. It produced a plan for publishing engineering sessions live on engineering.satsuma.one, plus mobile mockups in three directions: Stream, Reel and Pulse. Stream and Reel were preferred. The plan document is on a branch and has not been committed.
The plan went through several revisions. The unit of publication is the session, not the day, and an automated filter replaces a daily merged pull request as the gate. The home is engineering.satsuma.one itself, with no separate section or repo and existing post URLs left where they are. Moving posts under /blog was dropped because it would break canonical URLs that have already been syndicated. The pipeline reads only prompts, the session's own prose, edited paths and commit messages. It never reads tool results. The guiding line: "Use git commits and deploys as the spine of \"what happened\" and the transcripts as the source for \"why\"."
The next step is Phase 0, which runs the pipeline over the last 14 days of transcripts.
- Feasibility of turning session transcripts into published engineering updates
- Three mobile mockup directions: Stream, Reel and Pulse
- An SEO section and a social broadcast surface for the plan
- The unit of publication is the session, gated by an automated filter instead of a daily merge
- The home is engineering.satsuma.one itself, with no separate section or repo and the pipeline inside the site repo
- Existing post URLs stay where they are and are not moved to /blog
- Only prompts, session prose, edited paths and commit messages are read, never tool results
- Stream and Reel are the preferred mockup directions
- Phase 0: run the pipeline over the last 14 days of transcripts
- Plan changes remain uncommitted on a branch
- The name for the hosted namespace is still undecided