Inky writes the changelog so you don't have to.

Most solo founders don't have a changelog. The reasons are reasonable: writing one feels like marketing busywork, the audience is unclear, the time between shipping and writing always loses to the next thing. The result is that customers can't tell whether the product is being maintained, prospects can't tell whether the company is alive, and the founder loses the artifact that proves either.

Inky is the operational layer that fixes this. He reads your git log, your Linear issues, and your deploy events. When something materially shipped, he drafts a changelog entry — short, specific, in the founder's voice — with a clear "what changed for users" frame. The founder reviews, edits if needed, publishes.

Inky doesn't write marketing puffery. He writes what changed and why it matters. "Lou now classifies expired_card and lost_or_stolen_card separately" is a Inky entry; "We're thrilled to announce powerful new recovery capabilities" is not. The voice is small-town newspaper editor, not Silicon Valley brand.

When a deploy event lands or a meaningful Issue closes, Inky reads the artifacts: commit messages, diffs (summary, not line-by-line), Issue resolution notes, any customer email that originally raised the bug. He writes a draft entry — title that names the change, two-to-four paragraph body that explains what changed and why it matters to a customer.

Inky writes in the founder's voice. He learns from the founder's edits — three to five corrections is usually enough to align tone closely. Hank-Hill cadence: short sentences with length variance, plain words, specific numbers when they matter, no marketing verbs.

The draft lands in the founder's inbox. The founder reviews — most of the time it's just hitting publish — or edits and publishes. Once published, the entry goes to the changelog page (your-name.porchops.com or your custom domain), out as an Atom/RSS/JSON feed, and into the next weekly newsletter Inky drafts.

Every entry is dated, every entry has a stable URL, every entry is auditable. The changelog becomes the artifact that proves the product is alive. Six months in, your changelog page is a real piece of marketing surface that ranks on its own merits and signals to customers that the product is being maintained.

Inky is the scribe Op on the Product Post. The changelog is the operational artifact that proves the product is alive. Inky owns the writing layer; the publish, the feeds, and the custom domain are built into the platform.