Campaign rules
Turn a brand brief into operating rules for disclosure, duration, forbidden claims, payout currency, deliverables, and QA checks.
- Brief parser agent
- Human rule approval
- Persisted campaign rules
Clip strategy
Use the source transcript to identify candidate moments, hooks, captions, risk level, and rationale for short-form clips.
- Transcript-driven candidates
- Hook and caption pass
- Timestamped clip rows
Submission QA
Review clipper submissions with Qwen compliance analysis plus backend hard rules for disclosure, duration, proof, and claims.
- Compliance agent
- QA agent
- Backend constraints applied
Proof verification
Analyze proof screenshots through Qwen vision, extract post metrics, and reject screenshots missing date, username, or valid campaign timing.
- Signed OSS read URLs
- OCR metric extraction
- Campaign date checks
Payout recommendations
Calculate payout only from approved submissions with verified proof metrics, then require human approval before release.
- CPM math in backend code
- Eligibility reasons
- Approval checkpoint
Audit trail
Record every agent run, model provider, payload, result, latency, failure, override, and workflow decision for review.
- AgentRun records
- AgentAuditLog feed
- Evaluation summary
Guardrails
The model is useful, but it is not the source of truth.
Qwen proposes structured decisions; Pydantic schemas validate shape.
Backend rules enforce duration, required disclosure, proof existence, and forbidden-claim handling.
Proof dates and usernames are verified before views become payout-eligible.
Payout math stays deterministic and is not delegated to a model.
Human approvals gate campaign rules and payout release.
Where to start