# Example brief: XML entity escaping repair

INTERNAL FICTIONAL BRIEFING EXAMPLE — NOT A COMPLETED DELIVERY.

## Intended outcome
XML entity escaping repair for one agreed use case.

## Source to supply
Xml files, namespace definitions and the agreed target structure. Remove passwords, tokens and private third-party records you cannot share.

## Maximum starting scope
Up to 3 xml files with 10000 elements total.

## Example acceptance instructions
1. Identify the exact source items and requested change.
2. Provide one example that should be accepted and one that should be rejected or flagged.
3. Specify the expected destination format and any behavior that must remain unchanged.

## Handoff
Receive the editable implementation or configuration source, local example fixtures, and reproducible verification instructions, an acceptance checklist and a missing-evidence register. The operator must confirm that the actual brief fits this scope before payment.

## Not included
Account access, live deployment, publishing, sending messages, paid external APIs, legal/medical/investment advice, fabricated evidence or guaranteed business results.

## Review questions
- What is the authoritative source version?
- What must the output preserve?
- Which ambiguous cases require your decision?
- How will you inspect the result?

This example explains how to order this service. It is not proof that this exact task has been executed, nor a customer example.