Dentolize · Foreground update-docs Walkthrough
On this pageThe honest framing firstThe one-line storyWhat is actually new (say this, not more)Words that are accurateWords to avoidAssets you can pull from this siteSuggested channelsThe 30-second pitch

For Marketing

The honest framing first

This PR is an internal developer-experience fix to a CI workflow. It is not a product feature customers buy, and there is nothing here to announce to the market on its own. What it improves, though, is a genuinely story-worthy piece of how Dentolize is built — an AI that writes a live walkthrough for every change before it ships — and that capability is worth talking about. Market the capability; treat this PR as the moment it got trustworthy enough to show.

The one-line story

"Every change to Dentolize spins up a private, fully-seeded copy of the app and an AI-written walkthrough of what changed — and now you can watch that walkthrough being written, live, and know the second it's ready."

What is actually new (say this, not more)

  • Before: you asked for a docs refresh and got a thumbs-up that meant

"we started" — the real work happened out of sight.

  • After: the refresh runs in the open. You see the pages it visits, the

code it reads, the screenshots it captures — and the "done" light means the site is genuinely published.

That's the emotional beat: transparency and trust. "No more job finished, but where are my docs?"

Words that are accurate

  • "Live agent progress" ✅ — the job streams the agent's activity.
  • "Done means done" ✅ — job success now equals site published.
  • "Watch the docs build in real time" ✅.

Words to avoid

  • ❌ "Now available to customers" — this is unreleased internal tooling.
  • ❌ "Faster docs" — it is not faster; the agent takes the same time

(roughly 15–40 minutes, up to ~1 hour if a sandbox has to be deployed first). The win is visibility, not speed. Claiming speed is false.

  • ❌ "AI replaces the docs team" — the agent drafts a walkthrough of a code

change for a preview environment; it is a build-time assist, not a product.

Assets you can pull from this site

(login, dashboard, analytics) — proof that "every PR gets a real, running copy of the app."

  • The Overview before/after table is a clean visual for a slide.

Suggested channels

  • Internal engineering blog / changelog — this is the right home.
  • A "how we build" section on the careers or engineering brand page, if the

broader per-PR-AI-docs capability is being promoted. Keep this specific PR as a footnote ("...and we recently made the live progress visible").

The 30-second pitch

"We already give every pull request its own running copy of Dentolize and an AI-authored walkthrough of the change. This update makes that walkthrough build in the open — you watch it happen and you know exactly when it's live. Small change, big trust win for the people reviewing our work."