Execution proof you can verify.

ChiefLab is not a content generator claim. The loop has to leave receipts: approved action, published or manually posted URL, proof ledger row, measurement readback, and a next-move action created from the result.

102/102 customer-smoke checks passing · runs brand-domain customer smoke suite

Verified execution artifacts

Each row is a real action with a third-party or proof-ledger artifact. Full walkthrough →

Live HN loop — end to end

2026-05-29

customer: Smoke workspace (ws_a420d87bd667)

  1. Launch intent="get first users" + productUrl=github.com/bytedance/deer-flow → 1 publishAction routed to hacker_news (single-action mode, manual_handoff)
  2. Record URL chieflab_record_manual_publish accepted https://news.ycombinator.com/item?id=1 → action.status=executed
  3. Measure chieflab_measure_hacker_news called public HN API → score=57, descendantCount=3, topComments captured
  4. Classify outcome.kind=engage — "HN got real engagement — 57 upvotes / 3 comments"
  5. Next move 1 next-move action auto-created (reply_to_commenters), bodyKind="final_copy", sourceActionId linked back to original

Verify: Reproducible: `CHIEFLAB_SMOKE_AUTH_E2E=1 node scripts/verify-hn-loop.mjs` mints a workspace + runs the 4-phase chain against production. 13/13 PASS on last 3 deploys (commits ab4ea6b → 2c82a7a).

Dogfood — chieflab.io's own launch

2026-05-04

customer: ChiefLab (us, dogfooding)

  1. Publish (X) Zernio post ID 69f8a74fc50416d0f77f852e — real X post in chibaku_x account, scheduled 2027 for safety
  2. Send (email) Resend messageId ba122a9c-2843-4d38-b998-a345990911dc — real send, 2026-05-04

Verify: Both artifact IDs are real third-party objects. Zernio posts have public URLs; Resend message IDs are queryable via Resend API.

Founder loops in flight

These slots wait for design-partner founders whose names go public only after explicit consent. The important proof is not a logo wall; it is whether a founder can post, record proof, get measured, and wake up to the next move.

Solo founder, post-Cursor build

(name pending consent)

LinkedIn · X · Email

Indie SaaS, post-Claude Code build

(name pending consent)

LinkedIn · X

Devtool, post-Codex build

(name pending consent)

X · Product Hunt

Your launch could be next.

Install the MCP →

Build your own proof pack

After your action executes or you record a manual post, one command writes a markdown report with every artifact + readback.

chieflab proof-pack <runId> --out my-launch-proof.md

Quickstart → · Give to your agent · Source

The closed loop

The product only counts when each step leaves a receipt.

  1. Choose — ChiefLab turns the user's intent into the best next action. artifact: launchId · actionId · execution plan
  2. Approve — drafts render inline in the IDE; Launch Room mirrors the approval when a human wants a browser surface. artifact: chat approval event · signed reviewUrl · action status
  3. Execute — connector executes when available, or the founder posts manually. artifact: connector ID or manual published URL
  4. Record proof — every executed or manually posted action writes a proof row. artifact: proof_ledger row · source action link
  5. Measure — cron checks ripe proofs and pulls metrics where a channel supports it. artifact: measuredAt · score/comments/clicks/opens where available
  6. Next move — the result creates the next approval card. artifact: next_move action · workspace memory update