Skip to content

The plan gate

The model proposes; the plan gate judges. Before PULSE keeps something its model proposed, a second pass, PULSE’s reviewer, checks it against the evidence that run actually gathered: the pages read, the web research, your connected accounts’ figures, your check-up. The app calls it “PULSE’s reviewer”; these docs call it the plan gate.

The reviewer runs on the same model server, with its own instructions and at a near-zero temperature, so the same evidence gets the same verdict.

What the verdict does

VerdictIn the appEffect
Agreed“The reviewer agreed with it.”Kept.
Could not judge“The reviewer could not check it, so it is not approved by the reviewer.”Kept, and marked. It is never shown as agreement.
DisagreedWithheld / held back, with the reasonNot kept. It is listed as withheld, never shown as a proposal.
Switched off“The reviewer is switched off on this server.”Kept without review, and marked.

“Could not judge” covers every case where no verdict was reached: nothing to judge against, no model available, or no answer in time.

Where you meet it

  • Your check-up: the plan in the diagnosis, and the New groups of customers to try (withheld ones are not shown).
  • Content ideas: ideas that do not pass are listed as held back, with the reason.
  • Studio drafts written by a skill: the verdict is shown under What PULSE checked.
  • Campaign plans: “PULSE’s reviewer checked this plan against your audit”, or why it could not.
  • Site fixes: a pull request the reviewer does not agree with says Withheld by the plan gate, and nothing is opened.
  • Autopilot replies: a reply goes out by itself only when PULSE’s safety rules and the reviewer both agree; otherwise it waits for you.
  • Automations the assistant proposes and AI calls.

The plan gate is one check among several. Skills also run their own rule checks (see The checks), and PULSE’s safety rules screen inputs and drafts. None of them publishes anything: that still needs your approval and the publishing switches.

For administrators

The gate is on by default. PULSE_JUDGEMENT=off turns it off: proposals then pass unjudged and the app says the reviewer is switched off. A verdict the model wrote into its own proposal is removed before judging; the reviewer is the only source of a verdict. In the API, judged messages carry a judgement field and responses a judgements set listing every verdict, kept or withheld (accepted=false). See Common types and Configuration.