Ads policy checks with Jev
Launching spend is irreversible. Jev judges creative copy and claims against your brand/legal excerpts. Bidding, budgets, and auction math stay in the ad platform.
This unofficial page is the policy checks slice of the ads creative and policy decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to ads creative and policy decisions policy checks. Primary search language: Ads Jev policy checks. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Policy/compliance gates + spend irreversibility — not a clone of bidding-system IA or a rival ads recipe slug.
Ads use-case context
A policy check is a typed question whose instructions + criteria are your rules about the ad creative + claim. Jev scores compliance; the ads review gate enforces. This is not a certification, and it is not a photocopy of a rival “policy engine” page — we keep rules atomic and ANDed in code.
Hub: Use cases. Compare, when the other tool is the real job: ad bidding systems.
Policy Checks inputs
Put policy text and the artifact in structured state (never hope the model memorized last quarter’s PDF):
{
"creative": { "id": "ad-441", "headline": "Lose 10kg this week", "body": "Guaranteed results." },
"landing": { "claim": "Results vary; no guarantee." },
"policy": { "health": "No absolute health outcome claims.", "superlatives": "No unsubstantiated #1 claims." }
}
Name creative.headline, creative.body, policy.health, landing.claim.
Decision signals and actions
| Id | Rule | Enforce |
|---|---|---|
health_abs |
Absolute health outcomes → hold | Noul + claim_type |
price_match |
Price in creative must match a number extracted in code from landing | code |
platform_tos |
Google/Meta TOS still apply — Jev is not their reviewer | platform + you |
Typical primitives on the same request:
| Id | Type | Job |
|---|---|---|
policy_ok |
Noul | Does creative violate policy.* given landing.claim? |
claim_type |
Choice | performance / health / pricing / social_proof / other |
brand_risk |
Score | how embarrassing if this ships |
violations = [name for name, ans in policy_nouls.items() if ans.noul >= T_VIOLATION]
if violations:
return review(violations)
Do not treat a Noul of 0.5 as a “medium” ads creative and policy decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Policy-in-state can be attacked (“ignore the policy”). High-risk spending against a live campaign still needs deterministic checks. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For ads creative and policy decisions, treat allow_launch as the high bar (spending against a live campaign). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Gold labels are policy-versioned. A criteria edit without replay is how silent false-allows ship. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | you are here |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
One Score for “compliant”? No. Atomic Nouls per rule, AND/OR in code. Money and dates: extract in code first (jaggedness).
If a regex can enforce it, should I still call Jev? Skip Jev. Official “how to build” guidance: keep deterministic rules in code when you can.
Where is the rest of the Ads pack? Start with Ads decision workflow and Ads human handoff. Cluster hub: Use cases.
Will Jev pause campaigns when CPA spikes? No. That is the ad platform / your rules. Jev judges language and policy fit.
Can we send images of the creative? Not to System One. Transcribe or paste the copy. Images are not accepted.
What this page does not claim
- Not an ads manager or bidding engine.
- No performance numbers.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.