Repository navigation
Workflows team asks and why the Classify with Jev step closed #241
Description
Question
What did the Workflows team ask for when they asked for Jev-based decisions in workflows, and why was the "Classify with Jev" step (PostHog/posthog#107832) closed unmerged a day after it opened?
The answer shapes the primitive: if PostHog#107832 closed because of a product or platform objection, the new step must answer that objection, not repeat it.
This is a HITL task. The agent cannot read Slack in this session. Michael either pastes the gist, or connects the Slack MCP server so a worker can read the Jev channel, the Workflows team channel, and the demo thread where someone showed Jev in HogQL.
Where the answer goes. Slack contents go only into the private note workflows-jev-decisions.md in Silthus/personal. The resolution comment here records only what is safe in public: for example "the closure was about X (platform concern), see the private note", never quotes, names, or numbers.
Activity
Silthus commentedon Oct 4, 2026
Parked for Michael. No agent in this session can read Slack (the Slack MCP server is not connected here).
Decisions locked. Slack contents go only to
workflows-jev-decisions.mdinSilthus/personal. This ticket records only a public-safe gist.Pending question. Why was
PostHog/posthog#107832(Classify with Jev) closed, and what did the Workflows team ask for? Either paste the gist in the conductor thread, or connect the Slack MCP server (/mcp) so a worker can read the Jev channel, the Workflows team channel, and the HogQL demo thread.The spec waits on this ticket. Research and the prototype run in the meantime.
Silthus commentedon Oct 4, 2026
Resolution
Michael's answer: nobody knows why
PostHog/posthog#107832was closed, and the Slack context adds nothing that should block the design.Direction: build on top of PostHog#107832 rather than starting fresh. Its branch
workflows/jev-classify-step(head5af6142) is the base. Its reviews are evidence. The model is the PostHog-hosted Jev on the AI gateway, never TypeSafe.What changes against PostHog#107832: the prototype on #245 chose a native branching step, so the function template plus a condition step becomes one action type. The research on #242 and #243 replaces the inline
callInternalApiand addsprivacy_mode, an 8 KiB state cap, and credit and admission checks. Before the stack goes to the Workflows team, Michael asks its author why it closed.