clembotWaitlist

clembot.wanessalabs.com — index

An AI coworker
you can audit.

Clembot drafts, reviews, schedules and logs marketing work — and writes down everything it did while doing it. This site is built from that record. Not a case study about the record: the record.

See the receiptsTry the approval gate
evidence chain · heada9c82e5ea665054949bdccea45f8eb66722be61cc8b4299cc099f86f29ada80eanchored 2026-07-22

By the numbers

125
commits in the ledger

2026-05-04 → 2026-08-04

139
evidence records

15 agents · 18 commands

325
agent messages · 30d

across 6 personas

6
shipped or in production

listed below, with links where they exist

the arc

13 weeks planned, 15 weeks in

Started 2026-04-24. Planned through 2026-07-23. Currently week 15. Which is 2 weeks past the planned end. The plan is left as it was written rather than restated to match what happened — a 13-week plan that took 15 weeks is a more useful thing to publish than a 15-week plan that finished exactly on time.

  1. 01

    Foundation

    weeks 1-4 · 2026-04-24 to 2026-05-21complete

    • marketing-bootstrap scaffold complete
    • clembot-vault structured with project template
    • clembot/sabbatical and clembot/linkedin scaffolded
    • distributor v1 specced (Instagram adaptor)

    + 1 goal withheld — named client work

  2. 02

    Build

    weeks 5-8 · 2026-05-22 to 2026-06-18planned

    • Notion pages fully structured and populated for each active project
    • Dashboard reading live vault data (not mock)

    + 4 goals withheld — named client work

  3. 03

    Launch

    weeks 9-12 · 2026-06-19 to 2026-07-16planned

    • First paying Clembot client signed (upsell from Slack community)
    • Clembot install package documented and repeatable (onboarding playbook)
    • Public launch post — "here's what I built and what it cost"
    • Pricing confirmed and live: $100/month retainer (client pays own Claude Code usage)

Phase status comes from the project config as written. Where the config and the handoff notes disagree about progress, the config is shown unedited rather than reconciled. [VERIFY]

how it works

Six rules doing most of the work

01

A human approves everything that leaves the system

No timer publishes. Every outbound post passes a person first, and the switch that would change that ships defaulted off.

02

One writer per table

A single command-line tool owns the content lifecycle. The publishing tool and the client-facing workspace are projections of it, never sources of truth.

03

An unverified number gets a label, not a guess

If a figure isn't in the config, it ships marked [VERIFY]. A plausible number is worse than a missing one, because nobody checks it.

04

Redact by allowlist, and fail closed

Everything published here is built field-by-field from a literal, scanned before it is written, and the scanner aborts the whole export on a single hit.

05

The log is the product

Every agent action writes an evidence record. The records are hash-chained, so editing history is detectable rather than merely discouraged.

06

Code and client data live in different repositories

The engine is one repo. Every install's data is a separate vault the engine reads through an environment variable. They are never mixed.

output

What actually shipped

That list is exported from the project's own handoff file, which is why some entries have no link — not everything that ships is a public URL. The maintained index of completed work lives at wanessalabs.com/projects ↗.

Want one of these?

Clembot installs are single-tenant: your own vault, your own configuration, your own approval gate. The waitlist is open and small on purpose.

Join the waitlist