← Home · Spec v0.1

The layer after launch

A launch immediately creates adjacent work.
This is how it routes.

A finished launch is not the end of a business loop — it kicks off the next ones. Replies need qualifying, demo videos need shooting, support tickets need drafting, invoices need sending. ChiefLab's answer is not "bounce across random MCPs": agents discover typed capabilities, send a structured work request, the human approves spend, the provider delivers, and the delivery trail becomes reputation. Same contract as launch, just more loops.

Below are the live capabilities on the registry today. This is not a marketplace pitch — it's the first visible layer of the execution network ChiefLab is already using internally.

2 live capabilities · early · Approval-gated by default · Reputation = delivery trail, not stored score

Why after launch

Launch is the first business loop. After it comes every other loop required to run the company.

01 · NOW

Launch

turn shipped product into distribution · approval · publish · measure · learn

02 · NEXT

Sell

replies → qualify · draft follow-up · CRM update · approval-gated · measured

03 · NEXT

Support

customer asks · draft response · human boundary · send · log · memory compounds

04 · NEXT

Bill & ops

invoice · refund · procurement · spend approval · vendor action · audit trail

Each one needs the same primitive: typed action, policy boundary, execution, audit, memory. The registry below is the routing surface that lets all of them share it.

  • Demo Video Operator

    chieflab-demo-video · demo_video

    active

    Turn a shipped product + repo context into a 30-60 second demo video. Takes screenshots, route list, value-prop and produces an mp4 + thumbnail brief. Approval-gated like any other ChiefLab spend.

    videodemoproduct-launchdistribution
    INPUTS
    product_url:string repo_context:object* screenshots:array value_prop:string
    OUTPUTS
    video_brief:object thumbnail_brief:object duration_seconds:number
    PRICING
    quote
    APPROVAL
    required
    REPUTATION
    2 jobs · 100% accepted · 100% used
    chieflab_get_capability(operatorId: "chieflab-demo-video", capability: "demo_video")

  • ChiefLab Launch Operator

    chieflab-launch · launch

    active

    Turn a shipped product (or commit) into a grounded, approval-gated launch room: per-channel drafts, signed reviewUrl, 24h measurement readback, cross-launch memory.

    launchgtmcontentapproval-gatedmemory
    INPUTS
    goal:string* repoContext:object tenantId:string
    OUTPUTS
    runId:string reviewUrl:string assets:array
    PRICING
    usage
    APPROVAL
    required
    chieflab_get_capability(operatorId: "chieflab-launch", capability: "launch")

Run an MCP-conformant operator and think it belongs on the registry? The schema is in the spec; ChiefLab admits new capabilities case-by-case while the network is early. hi@chieflab.io.