Turn every releaseinto a launch.

1. New releaseAcme Billing

   Release title

   Recurring invoices

   Why it matters

   Bill repeat customers without rebuilding the invoice.

   Source links

   github.com/acme/billing/pull/452

   acme.com/changelog/recurring-invoices

   github · release.published201 · signature ok

   01

   Start from what you shipped

   Give the release a title, a reason it matters, and up to twenty source links: the pull request, the changelog, the docs. Or let a signed GitHub, GitLab, or custom webhook send every release on its own.

2. Launch specv2 · draft

   Problem

   Finance teams rebuild the same invoice every month.S1

   What changed

   Invoices repeat on a schedule you set once.S2brief

   Open question

   How many beta teams used it? No source says.

   Answer

   02

   Check a cited brief

   The spec drafts 11 sections, from problem and audience to proof and limitations. Every claim cites the brief or a source. A claim with no source is removed and becomes a question for you. Nothing is invented to fill a gap.

3. Campaign planv1 · approved

   Teaser

   XLinkedIn

   Launch day

   XProduct HuntEmailChangelog

   Follow-up

   LinkedInInstagram

   A1 hero 16:9 · /invoices/recurring · desktop

   A2 feature shot 1:1 · schedule modal

   03

   Approve a plan, not a pile of posts

   Each channel gets a role and a cadence. Each angle maps to a messaging pillar. Each asset names the screen to capture, the device, and the focus. The timeline runs teaser, launch day, follow-up.

4. Asset boardBrand kit · Acme v3

   Invoices that send themselves

   Monthly

   Quarterly

   Monthly

   Yearly

   LegibleOn brandMatches spec

   04

   Get visuals from your real product

   The visuals agent captures your product pages, frames them in the editor, and applies your brand kit. Every render is critiqued for legibility, brand, and fit with the spec before it moves on.

5. X · Launch day241 / 280

   Stop rebuilding the same invoice every month. Recurring invoices are live in Acme: set the schedule once and every cycle sends itself.

   capabilities.0whatChanged.1

   Within limitNo hypeKnown links

   05

   Get copy that cites its claims

   Channel-native posts for X, LinkedIn, Instagram, Product Hunt, your changelog, and email. Each post lists the spec claims it relies on. Posts over the limit, full of hype, or linking somewhere unknown are rejected and rewritten.

6. Review7 posts

   • X · TeaserREADY_FOR_REVIEW
   • LinkedIn · TeaserREADY_FOR_REVIEW
   • X · Launch dayREADY_FOR_REVIEW
   • Product Hunt · Launch dayREADY_FOR_REVIEW

   - every cycle sends itself.

   + every cycle bills on time, by itself.

   Approve all 7Apply revision

   06

   Approve in one click. Revise in one more

   Approve all seven posts at once or pick three. Ask for a revision on a post, a design, the plan, or a spec section and get a diff with its knock-on updates. Nothing changes until you apply it, and every decision teaches the next run your taste.

• 250+ backgrounds
• Export up to 5x
• Annotations and blur
• App Store screenshots
• Templates with your media
• Apache 2.0 licensed

Channel connections are set up with you during early access. Release emails go only to subscribers who consented, with one-click unsubscribe and exactly one delivery per address.

• <source id="S2" trust="untrusted">

  Prompt-injection defense

  Scripts, hidden text, and zero-width characters are stripped. Text that reads like orders to an AI is flagged and shown to the reviewer.

• redirect hop → resolve → public? yes

  SSRF-safe fetching

  Public http(s) only. Every resolved address is checked, every redirect re-checked, and every response capped in size and time.

• proofPoints.2 → openQuestions.0

  Citations enforced

  A claim that cites nothing, or a source that does not exist, is removed and turned into an open question.

• x: 291 > 280 · rewrite

  Copy guards

  Channel limits, hype words, your prohibited terms, unknown links, and uncited claims are rejected. The model gets the reason and fixes the post.

• tools: [] · workspace: session

  Stages without side effects

  Stages that read sources cannot act. The workspace comes from your session, never from model output or a crawled page.

• launch.spec · model · tokens

  Metered and audited

  Each model call is charged AI credits for what it costs, is rate-limited per workspace, and writes an audit event with the model and usage.

curl https://www.screenshot-studio.com/api/v1/releases \
  -H "x-api-key: $SCREENSHOT_STUDIO_API_KEY" \
  -H "Idempotency-Key: release-v2.4.0" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Recurring invoices",
    "benefitStatement": "Bill repeat customers without rebuilding the invoice.",
    "sourceUrls": [
      "https://github.com/acme/billing/pull/452",
      "https://acme.com/changelog/recurring-invoices"
    ]
  }'

201 Created
{
  "created": true,
  "release": { "id": "cm…", "status": "DRAFT", "title": "Recurring invoices" }
}

• API referenceEvery operation, live in Scalar.
• OpenAPI 3.1Generated from the same Zod contracts the routes run.
• Scoped keysFive scopes. Keys create, never approve or publish.
• llms.txtMarkdown for agents. Supported pages answer Accept: text/markdown.

• SSO and SCIM

  SAML and OIDC single sign-on, SCIM provisioning and deprovisioning.

• Six fixed roles

  Owner, admin, creator, approver, publisher, viewer. Least privilege by default.

• Append-only audit log

  The app can insert and read audit rows, never edit or delete them. IPs are hashed.

• SIEM drains

  Signed CloudEvents to any endpoint, or presets for Splunk and Datadog.

• Retention and legal hold

  Ninety days by default. Longer retention and legal hold on Enterprise.

• Private storage

  Files namespaced per organization. Signed URLs expire in two minutes. Uploads are write-once.

• Two-factor

  TOTP, required to connect social channels and to configure SSO.

• Tenant isolation

  Tenancy comes from the signed-in principal, never from input. Foreign IDs return 404, proven by a two-tenant test.

• Self-hosting

  Docker images and a Helm chart in the open-source repository.

1. ShippedLaunch intelligenceRelease, cited spec, plan, visuals and copy, review and revise.
2. ShippedWorkspace and assetsSave designs to the workspace, reopen them in the editor, save again.
3. ShippedRelease intake APIREST, scoped keys, idempotency, and signed GitHub and GitLab webhooks.
4. NextPaste a URL, get seven postsA reviewable product profile in seconds and a first week of posts in minutes.
5. PlannedMerged PR to suggested launchA pull request worth announcing becomes a suggestion, never an automatic post.
6. PlannedScreenshots after every deployFresh captures of changed screens, with before and after pairs.
7. PlannedDemo videosShort, captioned demos rendered from captured product flows.
8. PlannedThe weekly planMonday morning: one plan, seven posts, one approval.
9. PlannedCopilot and AutopilotProactive suggestions, then policy-bound publishing you switch on.