Ads audit trail 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 audit trail slice of the ads creative and policy decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to ads creative and policy decisions audit trail. Primary search language: Ads Jev audit trail. 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
An audit trail for ads creative and policy decisions is a decision trace: replayable inputs, typed answers, floors, and the action the ads review gate took. It is not a chat log and not a clone of a SIEM product page.
Hub: Use cases. Compare, when the other tool is the real job: ad bidding systems.
Audit Trail inputs
Persist the filtered payload (the contract), not whatever arrived at the edge:
{
"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." }
}
Redact secrets before the object hits cold storage.
Decision signals and actions
Minimum fields:
- creative.id
- policy version
- answers
- allow vs hold
- platform + campaign id after launch
Also store usage.input_tokens (vendor meter) and the full probabilities map — argmax-only logs cannot explain a close policy_ok.
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
If you cannot explain spending against a live campaign from the trace, you are not ready to auto-act. 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
Traces are the eval warehouse. Replay against hold / allow gold from brand+legal, plus claim_type gold after criteria or alias changes. 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 | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream action as a decision trace.
May I log raw secrets? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Ads pack? Start with Ads human handoff and Ads evaluation. 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.