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.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same 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.
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.
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 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
After processing a sample sensitive data request, instruct an 'AuditAgent' to generate a comprehensive 'audit_log' and 'compliance_report'. The audit log should detail every agent action, A2A message, and Model Context Protocol (Model Context Protocol) tool invocation, including security metadata. The compliance report should explicitly state adherence to (or deviations from) the defined policy rules.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Preserve the rubric, target behavior, and pass-fail criteria as the baseline for evaluation.
Adjust fixtures, mocks, and thresholds to the system under test instead of weakening the assertions.
Make sure the prompt catches regressions instead of just mirroring the happy-path examples.
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.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Develop a Secure, A2A Protocol-Enabled GovTech Agent
This challenge focuses on creating a secure, compliance-aware AI agent system designed for sensitive government applications. You will develop a multi-agent system leveraging the A2A Protocol for secure, verifiable agent-to-agent communication and MCP-enabled tool integration for interacting with simulated government APIs and data sources. The core of the challenge is to use GPT-5.1 for advanced reasoning and Semantic Kernel for orchestrating agents that can handle sensitive data, adhere to strict regulatory compliance, and operate across a simulated multi-cloud environment (e.g., AWS and Azure government clouds). The agents should demonstrate extended thinking with adaptive reasoning budgets to perform complex, secure data analysis or policy enforcement tasks, ensuring data integrity and access control through A2A and MCP standards.
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.