Factory proof · FDME pod
Watch the FDME pod turn an inquiry into a booking-ready handoff.
This scene shows the FDME pod doing runtime work in production: intake, qualification, commercial handoff, CRM/proof state, and owner-gated proof.
Buyer pain
A marketing lead that sits in an inbox is not revenue. The pod has to structure it, qualify it, create the next commercial action, and log proof.
Live workflow scene
Watch the agent do the work
Production smoke input
FDME self-pod runtime smoke: prove the digital marketing pod writes receipts, creates next actions, and keeps prospect communication owner-gated.
Phase 1
Client Intake Agent
Work happening
Receives a digital marketing lead and converts the request into a clean owner-review record.
Artifact created
FDME lead state
Production smoke wrote an FDME trace and 8 agent_runs.
Phase 2
Qualification Agent
Work happening
Classifies whether the lead needs a service fit check, proposal prep, follow-up, or booking handoff.
Artifact created
Qualified handoff
The qualification output created the next action for the pod.
Phase 3
Offer + Booking Agents
Work happening
Prepare the next commercial step so the team can move from inquiry to booked conversation.
Artifact created
Booking-ready action
Runtime receipt proves the handoff happened inside production.
Phase 4
CRM + Proof Agents
Work happening
Write the pipeline/proof state and make the run reviewable by the owner.
Artifact created
Pending proof curation
Proof curation dc04e2cf-7bc6-430c-a7a9-cf66163c857f was created.
Phase 5
Shadow + Karpathy Gate
Work happening
Checks that the pod performed visible work: input, data write, next action, score, and proof.
Artifact created
8 pass verdicts
Receipt shows owner-gated production execution, not a document-only task.
Output building on screen
Client Intake Agent
FDME lead state
Preserved the stated business context and source before routing the lead.