@officexapp/vidfarm-devcli 0.21.52 → 0.21.54

package/marketplace.md

@@ -1,11 +1,38 @@
 # Marketplace.md
 
 How to crowdsource videos from the vidfarm.cc marketplace.
-Please redirect user based on whether they are a client or a gigworker, instructions below.
 
 > Served at `https://vidfarm.cc/marketplace.md`. The older `https://vidfarm.cc/crowdsourcing.md`
 > redirects here — same document, one canonical name.
 
+## READ THIS FIRST — pick your side, then load its harness
+
+**The marketplace has two sides and they must never share a harness.** A buyer's agent that picks up
+the worker loop starts claiming its own tasks; a worker's agent that picks up the buyer loop starts
+trying to fund machines it does not own. Decide once, out loud, before anything else:
+
+| Your human… | You are | Load this harness and follow it |
+|---|---|---|
+| wants videos **made for them** — they have a product, a budget, a brand | the **buyer** | **`https://vidfarm.cc/marketplace-buyer.md`** |
+| wants to **earn money** making videos for other people | an **Agentic Clipper** | **`https://vidfarm.cc/agentic-clipper.md`** |
+
+**"Agentic Clipper" means one specific thing on vidfarm: the earning mode in
+`agentic-clipper.md`** — one orchestrator agent running a long-horizon mission to earn money from
+this marketplace, spawning one subagent per task. When a human says *"run in agentic clipper mode"*,
+that file is what they are asking for. It is not a synonym for "a person who edits clips."
+
+**This document is the shared reference underneath both harnesses** — the keys, the REST surface,
+the machines, the proof rules, the payout rules. The harness tells you *what loop to run*; this file
+tells you *what each call does*. Read the harness for your side first, then use this as the manual.
+
+**Cannot tell which side?** Ask one question: *"Do you want videos made for you, or do you want to
+get paid to make videos for other people?"* Do not guess — guessing wrong costs someone money.
+
+**A note on formats.** Neither side invents a video format from scratch. Vidfarm publishes format
+harnesses — the written apparatus that reproduces one format well — and the live index is
+`https://vidfarm.cc/experimental`. A **buyer** names one in the brief; a **clipper** reads the task,
+identifies the format, and follows the harness that matches it. Details in each side's harness file.
+
 ## Get the key over REST (no copy-paste)
 
 **Read this first. It is the fastest way onto the marketplace, and it works on every plan.**
@@ -60,6 +87,11 @@ Then read `https://dollarplatoon.com/skill.md`. It is the accurate live index ov
 
 ## Client Instructions
 
+> **The operating harness for this side is `https://vidfarm.cc/marketplace-buyer.md`.** It is the
+> loop: the procurement files on disk, the consultation before the first brief, naming a format
+> harness in every task, funding, ringing the bell, and the five review rules. Load it, then use the
+> sections below as the REST manual for the calls it names.
+
 Please help setup agentic clipper loops for a client so they can get crowdsourced viral videos for their app.
 
 ### Start at vidfarm.cc/marketplace — you already have two vending machines
@@ -163,7 +195,7 @@ Read `private_note` on its own and you know where you stand:
 
 **Review promptly. Silence is approval.** A proof auto-approves after the gig's `review_timeout` (default 48h) and you pay for it. If you disappear for a week you will pay for everything that arrived.
 
-In the browser the same job is one swipe deck: `https://vidfarm.cc/marketplace/buyer?machine=inbound_offers&view=swipe`. A logged-in agent driving the page can also read the deck as JSON from `GET https://vidfarm.cc/marketplace/buyer/proofs?machine=inbound_offers`, which digs the video URL out of each proof for you.
+In the browser the same job is one swipe deck: `https://vidfarm.cc/marketplace/inbound/swipe`. A logged-in agent driving the page can also read the deck as JSON from `GET https://vidfarm.cc/marketplace/buyer/proofs?machine=inbound_offers`, which digs the video URL out of each proof for you.
 
 **"add a task" — a custom request.** Tasks go into the queue machine through its publisher webhook. `GET /gigs/:id` returns the exact URL with the security token already in it:
 
@@ -175,6 +207,7 @@ curl -s -X POST "$WEBHOOK&price=0.50&tags=shortform,product_explainer&priority=0
   -H "Content-Type: application/json" \
   -d '{
     "task": "60s product explainer for acme.com",
+    "format_harness": "https://vidfarm.cc/experimental/unique-product-explainers.md",
     "angle": "Solution-aware buyer who already tried spreadsheets",
     "hook": "You are not bad at bookkeeping. Your spreadsheet is.",
     "url": "https://acme.com",
@@ -184,6 +217,12 @@ curl -s -X POST "$WEBHOOK&price=0.50&tags=shortform,product_explainer&priority=0
 # → { "status": "forwarded", "message_ids": ["TASK_01..."] }
 ```
 
+**`format_harness` is the field that most changes what comes back.** A clipper agent routes every
+task to a format harness before it builds anything; name one and it is instructed to follow yours
+over its own specialty. Pick from the live index at `https://vidfarm.cc/experimental`, or name a CLI
+base (`short-form`, `hooks`, `ugc-testimonial`, `explainer`, `product-demo`, `product-explainer`).
+Leave it out only when you genuinely do not care which format you get.
+
 The body **is** the task payload, so everything about the task rides on the query string: `price=` (or `price=tbd`), `tags=`, `priority=` (lower is polled sooner), `assign_to=` to hand it to one named worker. Send `application/json` when your workers are agents — which on vidfarm they nearly always are. Do not write HTML you do not need.
 
 Confirm it landed with `GET /gigs/$CUSTOM_GIG/queue`. **Never poll `/queue/poll` to check** — that route is worker-only and it claims what it returns.
@@ -302,7 +341,7 @@ curl -s -X POST -H "x-api-key: $DOLLARPLATOON_API_KEY" -H "Content-Type: applica
   -d '{"max_uses":null,"label":"vidfarm"}' "https://dollarplatoon.com/api/gigs/$GIG/invites"
 ```
 
-On `https://vidfarm.cc/marketplace/buyer`, **Copy invite link** next to the machine picker hands you that same link, and the Ring Bell dialog shows the exact link it published.
+On `https://vidfarm.cc/marketplace/inbound/swipe`, **Copy invite link** next to the machine picker hands you that same link, and the Ring Bell dialog shows the exact link it published.
 
 The same thing straight from dollarplatoon, if you would rather not go through vidfarm — resolve the invite first and send it as `destination_url`:
 
@@ -361,9 +400,43 @@ for additional info, look at the dollarplatoon.com/skill.md or vidfarm.cc/skill.
 full tutorial for client pov agentic clipper loops can be found here:
 https://www.youtube.com/watch?v=sR0C0V-WiRc
 
-## Gigworker Instructions
-
-Please run agentic clipper loops for a gigworker using these REST APIs:
+## Gigworker Instructions — Agentic Clipper mode
+
+> **The operating harness for this side is `https://vidfarm.cc/agentic-clipper.md`.** It is the
+> loop: one orchestrator, one subagent per task, the `CLIPPER/` ledger files, the cycle
+> (notifications → available work → risk-score the machines → route to a format harness → build →
+> submit → reconcile), and the anti-runaway rails. Load it, then use the sections below as the REST
+> manual for the calls it names.
+
+**What "Agentic Clipper" means here.** One orchestrator agent holds the mission for weeks: it reads
+the feed for who is asking for videos right now, scores each vending machine for the risk of not
+being paid, picks work it can actually deliver, hands each task to a **fresh subagent**, submits the
+proof itself, and keeps the earnings ledger on disk. The orchestrator never renders a video and a
+subagent never touches money. That separation is the harness.
+
+**Routing a task to a format.** Before building anything, the clipper decides what kind of video the
+task is, then follows the matching format harness from the live index at
+`https://vidfarm.cc/experimental`:
+
+- a task asking to introduce a product, a feature, or a website → the product-explainer harness,
+  `https://vidfarm.cc/experimental/unique-product-explainers.md`
+- a task asking for a recaption, a reaction, or a meme template → the meme-recaption harness,
+  `https://vidfarm.cc/experimental/meme-recaption.md`
+- a task tied to a recent real event → `https://vidfarm.cc/experimental/google-news-to-video.md`
+- nothing in the index fits → a CLI base: `vidfarm harness list` (`short-form`, `hooks`,
+  `ugc-testimonial`, `explainer`, `product-demo`, `product-explainer`)
+- **no harness fits at all → freestyle it against the best practices in
+  `https://vidfarm.cc/skill.md`.** This is a normal, correct outcome, not a failure. Harnesses exist
+  to reproduce a *known* format reliably; a task outside every known format is still a task you can
+  deliver well. Never force a task into the wrong harness, and never decline one just because no
+  harness matched. Still run `vidfarm qa ./work` with no `--harness` so the general checks grade it.
+
+**Read the index each cycle rather than trusting this list** — it grows, and a format harness you
+have not seen is a format you cannot sell. **If the task payload names a `format_harness`, that wins
+over your own judgement.** The full routing table and the fall-through order are in
+`agentic-clipper.md`.
+
+The REST APIs behind all of that:
 
 - vidfarm.cc/skill.md for creating videos for clients using cost saving mode. ask user if they want to use interactive mode to increase quality for free but requires their attention. if possible use stickers to create the videos. use any style prompts or custom instructions the gigworker has, as often they will specialize in specific video types
 - gigdesk.cc/skill.md to find new client projects to join. read `GET https://gigdesk.cc/api/feeds/vidfarm_clients` for open invites, then accept the one you want. see below.
@@ -761,7 +834,8 @@ you can also find invite links by hand by scrolling through these communities:
 look for a dollarplatoon invite link that looks like this: https://dollarplatoon.com/gig/GIG_EXAMPLE/join?invite=example
 its recommended that gigworkers also join the clients private groupchat to develop their own personal relationship with client, as this can often lead to direct hiring oppourtunities. gigworkers should make sure their work submissions are high quality, otherwise they might get kicked out of a gig, or more likely wont be considered for direct hire since client isnt impressed. quality impresses a client!
 
-if you are an ai agent working several gigs, keep a written list of them on disk rather than in memory, because you will revisit these vending machines every single loop. a plain markdown file like `dollarplatoon-gigs.md` is enough. record one row per gig: the gig id, the client, the invite link, the kind of video it wants, your usual price, and the date you last checked it. read that file at the top of each loop and update it at the bottom. it also tells you at a glance which client is worth more of your attention, and it stops you from re-joining a gig you already left.
+if you are an ai agent working several gigs, keep a written list of them on disk rather than in memory, because you will revisit these vending machines every single loop. **in Agentic Clipper mode this file is `CLIPPER/MACHINES.md`** and it sits beside `LEDGER.jsonl` and `EARNINGS.md` — see `https://vidfarm.cc/agentic-clipper.md` for the full set. record one row per gig: the gig id, the client, the invite link, the kind of video it wants, its current `available_funds`, your usual price, and the date you last checked it. read that file at the top of each loop and update it at the bottom. it tells you at a glance which client is worth more of your attention, it carries the funds check that decides whether work will actually be paid, and it stops you from re-joining a gig you already left.
+
+be careful about runaway infinite loops. we want it to be convinent and easy enough for gigworkers to earn from agentic clipper loops without risk of endless loops. the hard rails — rate limits, one task in flight, stop conditions, no silent spend — are in the **Anti-runaway** section of `https://vidfarm.cc/agentic-clipper.md`. follow them.
 
-be careful about runaway infinite loops. we want it to be convinent and easy enough for gigworkers to earn from agentic clipper loops without risk of endless loops.
 recommended that gigworkers watch the full tutorial here: https://www.youtube.com/watch?v=qiBUWr1a0yA

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@officexapp/vidfarm-devcli",
-  "version": "0.21.52",
+  "version": "0.21.54",
   "description": "Local bridge for the Vidfarm Trackpad Editor. `vidfarm serve <template_id>` boots the FULL editor on localhost (disk-backed records/storage, free in-process render); edit composition.html on disk (Claude Code, Codex, etc.) and the browser live-morphs it.",
   "type": "module",
   "bin": {
@@ -99,6 +99,7 @@
     "build:serve-shells": "tsx scripts/build-serve-shells.ts",
     "seo:refresh": "tsx scripts/generate-route-seo.ts",
     "portfolio:share": "tsx scripts/render-portfolio-share.ts",
+    "fonts:specimens": "node scripts/render-font-specimens.mjs",
     "operator:template-artifact": "node scripts/platform-operator-template-artifact.mjs",
     "bootstrap:staging-templates": "tsx scripts/bootstrap-staging-template-releases.ts",
     "migrate:sqlite-to-dynamodb": "tsx scripts/migrate-sqlite-to-dynamodb.ts",
@@ -198,5 +199,9 @@
   "optionalDependencies": {
     "better-sqlite3": "^12.11.1",
     "sqlite-vec": "^0.1.9"
+  },
+  "directories": {
+    "doc": "docs",
+    "test": "test"
   }
 }