FragmentBack to Studio

How Fragment works

Fragment separates the work into a visible human workflow and a guarded technical pipeline. You supply the facts, the system builds structured drafts, and your team controls every final decision.

Open Fragment Studio

AI drafts. People decide.Fragment is built for review and editing before publishing.

What your team does

Four stages take a project from source material to review-ready campaign work.

  1. Create the brief

    Add the project name, ticker, narrative, audience, and verified links. This brief becomes the factual boundary for everything Fragment creates.

  2. Choose the working path

    Use Brief Studio for a fast launch pack, or create a persistent Studio campaign when you need clients, approvals, scheduling, credits, and a longer-running workspace.

  3. Generate coordinated drafts

    Fragment sends the relevant project context to the configured model and asks for channel-specific deliverables in a predictable structure.

  4. Review and refine

    Every result returns as editable work. Your team checks the facts, rewrites what needs judgment, changes approval status, and decides what is ready to use.

What happens after you select Generate

This is the Brief Studio request path, from browser validation to an editable launch pack. API credentials remain server-side throughout the process.

  1. 1

    Validate the request

    The browser normalizes the brief, checks required fields and safe links, then sends only the structured inputs needed for generation.

  2. 2

    Reserve capacity in Convex

    A server-side Convex action validates the request again and reserves quota before calling any model, so rejected input never consumes a generation.

  3. 3

    Select a working Groq key

    Brief Studio uses a server-only, ordered Groq key pool. If one provider request fails, Fragment tries the next key without sending any credential to the browser.

  4. 4

    Generate structured output

    The Vercel AI SDK calls Groq with the normalized brief and an exact output schema for the concept, five X posts, and KOL script.

  5. 5

    Parse, ground, and retry

    The response must pass the schema and grounding checks. Invalid structure or claims not supported by the brief are rejected and regenerated instead of shown as finished work.

  6. 6

    Return editable results

    A valid pack returns to the browser and enters local browser history. Brief Studio keeps the latest 20 runs locally; it does not persist those packs in Convex.

Two workspaces, two jobs

Fragment keeps quick generation separate from persistent campaign operations so each surface stays focused.

Brief Studio

For a fast, self-contained launch pack.

  • Uses Groq through the Vercel AI SDK
  • Stores the latest 20 runs in local browser history
  • Does not create server-side campaign records

Fragment Studio

For authenticated, ongoing campaign delivery.

  • Uses Convex Auth and ownership checks
  • Persists projects, clients, campaigns, and deliverables in Convex
  • Generates campaign packs through OpenRouter, then tracks review and approvals

Grounded by design

Generation is treated as a draft, not a source of truth. Schema checks protect the shape of the result; grounding rules reject unsupported claims; human review decides what can be used.

Built with ClaudeKit

Fragment uses ClaudeKit as part of its product-building workflow, helping turn clear requirements into a dependable working interface.

Visit ClaudeKit