Human Gate
The explicit owner-approval step before any external write — enforced at three levels of the platform.
What is the human gate?
The human gate is the explicit owner-approval step in the closed loop: a recommendation must be approved at the human gate before any external write happens. It is enforced at three levels, keeping the agentic loop operated, never autonomous.
The human gate is the safety contract of the agentic loop: nothing reaches the outside world without a person deciding it should.
In an operated loop the agents do the analysis, but a human owns the decision to publish. The human gate is where a recommendation is reviewed and explicitly approved before any external change — a published article, a product update — is written. It is the difference between an autonomous system and an accountable one.
It is not a single checkbox but a guarantee enforced at three levels: the orchestrator state machine pauses for approval, the recommendation status transition requires it, and the lift runtime re-checks at the publish step. Even if one layer were bypassed, the others hold the line.
The human gate is why SkuLift describes the loop as operated rather than autonomous. Agents propose; owners dispose. It pairs with the brand kit and citation-hardening contract to keep published output safe, on-brand and grounded.