Not a chat. Your process, run by agents, with a gate your people can check.

the process, in the client's words

We have a backlog of small, well-described changes. We want them built, reviewed and released without a developer babysitting each one, and a human only where money or production is touched.

where the agent sits

1. spec merged as its own pull request
2. round on a runner: plan, then implement
3. review by a different vendor's model
4. verify, then a pull request back
5. human approval
6. release cut by the line

the gate

Cross-vendor review is the gate: a reviewer from the same model family blocks nothing, a rival vendor blocks nearly half. The merge flow is CI-aware, and the write rail refuses an unknown token outright rather than writing something it cannot attribute.

what the human approves

Every merge, every deploy, every publication.

the process, in the client's words

The portfolio report goes to the client only after a named person approved it, and no number in it can be unverifiable.

where the agent sits

1. a model drafts from source data
2. a gate recounts every figure
3. the pipeline waits on a human
4. publish
5. journal the cost and the outcome

the gate

A deterministic function with no model in it recounts every claimed number against the source, checks the document's shape and that the shares add up. What does not reproduce goes back to the model with the reason. Three strikes. Three things can refuse: the gate, the person, and the clock.

what the human approves

Publication. One button, after which the document leaves.

the process, in the client's words

A daily commentary on the risk dashboard that people read without checking.

where the agent sits

1. the engine computes the metrics, rounded once
2. the model writes prose and must declare every figure it uses
3. the gate checks each declared figure against the engine, and every number in the prose against the declared list

the gate

Three ways to fail: a figure that disagrees with the engine, a number in the prose that was never declared, or the wrong shape. A sabotage button swaps one figure and shows the refusal happening.

what the human approves

Publication of the commentary.

the process, in the client's words

We need products and content for a storefront and socials, with nothing to photograph and no budget to photograph it.

where the agent sits

1. an intake bot collects finds
2. a draft card is written in the brand voice
3. the catalogue holds the canon
4. photography is generated locally
5. a publish task builds and deploys the storefront

the gate

The bot stores nothing from strangers. Every draft is approved, edited or rejected before it can move, only a ready package ships, images over the size limit are refused, and the runner may only touch allowed paths.

what the human approves

Keep or discard a find, approve a draft and set its price, move it to ready, publish.

the process, in the client's words

Every morning a forecast of the day, as a clip with voice and captions, plus a site in four languages. Monthly, one clip per sign. Weekly, one general post.

where the agent sits

1. ephemeris positions computed
2. a text draft with a self-checking retry loop
3. voice generated
4. the voice is transcribed back and compared
5. captions and render
6. release to site, then channels, on timers

the gate

The finished audio is transcribed by a second model and word-diffed against the source text. One inserted word rejects the take. Two takes, then the release stops and raises an alarm rather than shipping. Every clock time in the text must exist in the engine's event list.

what the human approves

Silence before the deadline is consent, and the human can hold, skip or publish now; uploads to video channels run only from his own timer.

the process, in the client's words

From a track and a storyboard to a published clip: story, frames, beat sync, assembly, publish.

where the agent sits

1. storyboard
2. frame generation
3. a beat grid computed from the audio
4. assembly on the beat grid
5. publication drafts

the gate

The storyboard is approved before a single frame is generated. Every frame is checked against the cast canon, and a drifted character is regenerated by tag rather than accepted. Durations come only from the computed beat grid, because doing that arithmetic by hand once produced a clip two seconds short.

what the human approves

Storyboard, frame contact sheets, the final clip, and the publication itself.

the process, in the client's words

A clip for a song, from the audio file to an upload-ready video with its metadata. And a thirty-second animatic from a track, with subtitles.

where the agent sits

1. timings from the audio
2. storyboard
3. cast canon
4. frame generation
5. compositing of the complex shots
6. upscale
7. assembly with sound and subtitles
8. technical acceptance
9. publication package

the gate

A contact sheet is taken from the finished video and checked. Loudness is measured against a target rather than eyeballed. A frame where the character canon drifted, or the shot is wrong, is regenerated rather than accepted.

what the human approves

The storyboard before generation, the frame checklist before assembly, and the final video.

the process, in the client's words

Photograph a receipt or a banking screen from the phone, and the books propose the missing entries. Monthly totals that match the spreadsheet I keep today.

where the agent sits

1. a document is shared from the phone
2. a local vision model reads it, and nothing leaves the machine
3. candidate entries are extracted
4. each is matched against what is already recorded
5. the person confirms
6. the ledger, the envelopes and the daily allowance update

the gate

Candidates are matched against recorded entries and earlier proposals before anything is shown, so the same document cannot be booked twice. A candidate that names no account asks instead of guessing. Nothing is written without a tick. The release bar is that monthly totals equal the workbook's, or the difference is explained in writing.

what the human approves

Every entry and its category, every balance observation, and both legs of every transfer.

the process, in the client's words

Five historical shorts a week, the same characters, the same style, checked before anything is published.

where the agent sits

1. brief
2. story
3. arc
4. bible
5. breakdown
6. build
7. acceptance
8. publish

the gate

Every gate needs an explicit human yes, and silence is never consent. An unapproved shot list blocks generation, an unapproved contact sheet blocks animation, a failed voice check blocks assembly, an open acceptance line blocks release, and a duplicate or out-of-order push to a channel is refused.

what the human approves

The production card, the logline, the canon and the bible, the shot list, the contact sheet, the acceptance protocol, and each channel it goes to.