Source code is not automatically required or automatically persuasive. Select evidence that explains the employee’s knowledge and contributions clearly; an annotated architecture extract, decision history or manager account may be more understandable than a large code export.
Make technical exhibits readable
Identify what the employee did, when and why it demonstrates the claimed capability. Address confidentiality without stripping away all meaningful substance. Include training, foreign employment and the proposed assignment alongside technical examples.
A repository access list proves access, while the petition needs evidence of knowledge and the role involving it. The evidence failure is unreadability. A reviewer who cannot follow an exhibit cannot be persuaded by it, and a large code export is harder to assess than a short annotated extract explaining what the employee decided and why.
The second failure is over-redaction, where confidentiality review removes so much substance that the exhibit no longer demonstrates anything. The earliest signal is an exhibit nobody on the team can summarise in two sentences. Select a small number of examples, state what the employee did, when, and why it demonstrates the claimed capability, and address confidentiality by summarising rather than by deleting.
Include training, foreign employment and the proposed assignment alongside the technical material. Ask who will read the exhibit and write for that reader.