New piMark is a six-agent autonomous marketing team — now in private preview. Read the manifesto →
Manifesto

The human in command.

"Human in the loop" quietly made people quality-control for machines. We think that is exactly backwards. This is the piMark position on who works for whom.

There is a phrase the AI industry reaches for whenever someone asks about control: human in the loop. It sounds reassuring. Look closer at what it usually describes, and it is a strange bargain: the machine runs the process, sets the pace and defines the work — and the human is inserted at a checkpoint to click approve. The human is in the loop the way a toll booth is in a highway.

We built piMark on a different phrase, borrowed from how militaries and aviation think about autonomy: human in command. The distinction is not semantic. It is about whose intent the system serves and who works for whom.

In the loop versus in command

In a human-in-the-loop system, the machine owns the process and the human is a component of it — a validator, a rubber stamp with a conscience. The failure mode is well documented in every field that has tried it: reviewers presented with an endless stream of machine output stop reviewing and start skimming. Vigilance decays. The checkpoint becomes ceremony. Worse, the human's role shrinks to reacting to what the machine proposes; the machine has quietly taken over the agenda.

In a human-in-command system, the human owns the intent — the strategy, the standards, the boundaries — and the machine owns the execution inside those boundaries. The human is not a step in the machine's process. The machine is a resource in the human's. Command scales in a way that inspection never can: you do not get better outcomes by checking more outputs; you get them by setting clearer direction and better constraints.

In the loop, you approve what the machine decided. In command, the machine executes what you decided.

What stays human, permanently

This is not a transitional arrangement while the models improve. There are three things we believe should stay human even when — especially when — the agents are excellent:

  • Taste. What your brand sounds like, what it would never say, which joke lands and which one is beneath you. Taste is not a quality bar an agent clears; it is an identity only an owner can define. Agents can learn your taste from your decisions — in piMark they do, from every approval and rejection — but learning taste and owning it are different things.
  • Strategy. Which market, which story, which bet. An Analyst agent can tell you what your audience engaged with; it cannot tell you what your company should become. Direction is a decision about the future, and the future is not in the training data.
  • Approval. The final yes on what ships under your name. Not because agents cannot be trusted with mechanics — ours schedule and operate all day — but because accountability cannot be delegated to something that cannot be accountable. When a post goes wrong, "the AI did it" is not an answer any serious company can give.

What goes to the agents, gladly

Everything else — the grind that has been mislabeled as marketing for twenty years. Reading the analytics every week. Turning findings into briefs. Drafting, redrafting, resizing, reformatting. Adapting one idea to five channels. Keeping the calendar full and the queues alive. Chasing the review. Reconciling the spreadsheet. In piMark this is precisely the division: the Analyst reads, the Boss plans, the Writer drafts, the Hustler multiplies, the Wildcard adapts, the Observer pre-reviews — and the human decides.

The unlock is not just saved hours, though the hours are real. It is that command is a better job than production. Ask anyone who has run a small company's marketing what the role actually felt like: 90% production, 10% thinking, and the thinking done at 11 p.m. because production ate the day. Agents invert the ratio. The human's week becomes: set direction, review the plan, approve the queue, override where taste demands it, and think. That is what the job description always pretended the job was.

A note on the word "approve". Command does not mean reading every word of everything forever. In piMark, autonomy is a dial you set per brand and channel — from approving every piece to reviewing by exception under guardrails you defined. Both extremes are command, because in both, the boundaries are yours, every action is logged, and the kill switch is under your hand. What we refuse to build is the version where the boundaries are ours and you are the toll booth.

Why this is a design constraint, not a slogan

Position statements are cheap; architecture is where a company tells the truth. Human-in-command is enforced in piMark by construction, and you can check each claim against the product:

  1. Intent is an input, not an inference. Your strategy, voice and guardrails are explicit configuration the agents work inside — not something a model guesses from vibes and yesterday's posts.
  2. Autonomy is granted, never assumed. Every brand and channel starts at full human approval. The dial moves only when you move it.
  3. Disagreement is preserved. When the Observer objects to a draft and gets overridden, the objection stays in the record. A system that hides its internal dissent is managing you.
  4. Everything is inspectable and reversible. Tamper-evident audit log, visible cost ledger, kill switches at every level. Command without instruments is a figurehead.

There is a version of this industry that treats the human as a legacy component — a compliance requirement to be minimized release by release. We think that version misreads what marketing is. Marketing is a company speaking. The speaking can be manufactured; the meaning cannot. Someone has to intend it.

So our position, stated plainly: the agents work for you. Not alongside you, not with you in their loop — for you. The day that stops being true of piMark, we will have built the wrong product, and we would rather write that sentence here, in public, where it can be held against us.

Talk to us