For product and engineering teams
The engineering story is already in the pull request
Fireside reads merged PRs and commits, reconstructs why the work mattered, and drafts a clear story for people outside the repo. Your team reviews every draft before it goes anywhere.
A real reliability fix from Fireside's own repo
+ Stop after three consecutive 404s
+ Disable the source and tell the operator what to fix
+ Reset the failure count after a successful fetch
+ Do not count timeouts or server errors as a missing repo
Source record: private Fireside repo · PR #109
When a connected GitHub source disappeared, Fireside retried it on every scheduled run. The source could not recover on its own, but the system had no stopping rule.
Fireside now stops after three consecutive 404s, disables the source, and gives the operator a clear next step. A successful fetch resets the count; timeouts and server errors do not count against the repo.
Failures that require a person to fix now stop asking the software to try again.
From code change to company story
Find the consequence
Fireside watches merged work and looks past file counts for the customer, product, or operational change underneath.
Rebuild the context
The draft stays tied to the PR description, linked issue, and commit messages so technical detail survives the trip out of GitHub.
Check and approve
A human confirms the claim, edits the voice, and decides whether the story belongs on LinkedIn, X, or an internal channel.
What the draft keeps
The technical reason
The interesting part is often a constraint or tradeoff. Fireside keeps it instead of flattening the work into a release note.
Your company's voice
Channel rules, examples, and phrases to avoid shape the draft before it reaches the reviewer.
Human judgment
The system can surface evidence and write a first pass. Your team still owns accuracy, timing, and publication.
Part of a bigger idea
Developer stories are one use for a company story engine: a system that finds useful material in work already happening, then turns that evidence into drafts. The source comes first.
What is a company story engine? →Make the reasoning behind the release visible
I connect Fireside to your sources, tune it to your voice, and build the review loop with your team.
Operated by Fireside Systems Pty Ltd, A.C.N. 695827322 · sean@fromfireside.com · Terms · Privacy