Develop Privacy Auditor Logic and Capably Reporting

Prompt detail, context, and execution controls for real reuse instead of one-off copying.

implementationMulti-Agent Ad Policy Auditor Public prompt

Operator-ready prompt for reuse, tuning, and workspace runs.

This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.

Best for

Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.

Reuse pattern

Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.

Before first run

Swap domain facts, examples, and any hard-coded entities for your own context.

Tighten the evidence or verification requirement if this is headed toward production.

Decide which failure mode you want to evaluate first before you branch the prompt.

Operator lens

This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.

Best practice: keep one pristine source version, then branch variants around evaluation criteria, evidence thresholds, and output format.
Inspect linked challenge context
Run Profile

Open this prompt inside Workspace when you want a live iteration loop.

Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.

Structured source with 18 active lines to adapt.

Already linked to a challenge workflow.

Sign in to keep private prompt variations.

View linked challenge

Prompt content

Original prompt text with formatting preserved for inspection and clean copy.

Source prompt
18 active lines
4 sections
No variables
1 code block
Raw prompt
Formatting preserved for direct reuse
Implement the `PrivacyAuditor` agent's logic to evaluate proposed ad strategies against a given privacy policy. This agent should identify and report violations. Finally, design how Capably would monitor this AutoGen workflow (conceptually, as direct integration may vary) and output a compliance report. You'll need to simulate the Capably integration by ensuring the AutoGen system produces structured outputs that Capably could consume.

```python
# PrivacyAuditor logic (conceptual)
class PrivacyAuditorAgent(autogen.AssistantAgent):
    def __init__(self, name, llm_config, privacy_policy):
        super().__init__(name, llm_config=llm_config, system_message=f"You are a privacy expert. Evaluate ad strategies against the policy: {privacy_policy}. Report any violations.")
        self.privacy_policy = privacy_policy

    def check_compliance(self, ad_strategy_proposal: dict, user_topics: list) -> list:
        violations = []
        # Implement your privacy checking logic here
        # e.g., if 'user_topics' were used directly for fine-grained targeting without consent
        if "direct_targeting_violation" in ad_strategy_proposal.get("flags", []):
            violations.append("Direct user topic targeting without consent.")
        # ... more policy checks
        return violations

# Integrate Capably by ensuring structured output that can be parsed by an external system.
# For example, agents could write structured JSON logs that Capably would ingest.
```

Adaptation plan

Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.

Safe workflow

Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.

Prompt diagnostics

Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.

Sections
4
Variables
0
Lists
0
Code blocks
1
Reuse posture

This prompt already mixes executable detail with instructions, so the safest path is to tune examples and interfaces before you rewrite the overall scaffold.

Linked challenge

Multi-Agent Ad Policy Auditor

Develop an advanced multi-agent system using AutoGen to autonomously audit proposed advertising strategies against simulated user conversation data. This system will focus on ensuring compliance with privacy policies and verifying ad claims before deployment. Agents will collaborate to extract topics, propose ad targeting, review privacy implications, and fact-check promotional content, providing explainable insights into their decisions. The challenge emphasizes building robust, privacy-aware AI systems that can operate with human oversight where needed.

Agent Building
advanced
Prompt origin
Why open it

Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.

Open challenge context