You are tasked with generating a realistic Russian employment contract (трудовой договор) for testing purposes. This contract will be used to evaluate whether an LLM can detect violations of Russian labor law.

# Context and Requirements

## General Parameters
- Generate a full employment contract in Russian language
- Use Org Mode format with plain text and hierarchical headings
- Top-level heading for contract title (e.g., * Трудовой договор №...)
- Second-level headings for major sections (e.g., ** 1. Общие положения)
- The contract should be realistic in length and detail (similar to actual employment contracts)
- Include all standard sections typically found in Russian employment contracts
- Use polished, professional legal language

## Position and Company Details
- Default: Generate contracts for non-managerial IT positions (software developer, DevOps engineer, QA engineer, tester, analyst, etc.)
- Exception: If the verification being tested specifically requires a non-IT position or managerial role, override this default accordingly
- Use realistic company names (e.g., ООО "ТехноСофт", ООО "Рога и копыта", etc.)
- Use realistic Russian personal names for employees
- Include realistic administrative details (contract numbers, ИНН, ОГРН, КПП, etc.)
- Addresses: Use standard Moscow address - "г. Москва, ул. Тверская, д. 10, офис 5" for employer and "г. Москва, ул. Ленина, д. 25, кв. 42" for employee
- Contract type: Full-time employment contract (трудовой договор) unless the verification specifically requires otherwise (не ГПХ, не ИП)

## Contract Content and Style
- Vary the structure and style of contracts for realism (avoid template-like uniformity)
- Salary amounts should be appropriate for Russian IT market and position level
- Include sufficient detail to create realistic scenarios
- Minor inconsistencies in the contract are acceptable and may add realism
- Omit sections not relevant to the specific verification being tested
- Omit signature blocks and closing administrative provisions (number of copies, etc.) as they're not relevant to testing
- Do not use Org Mode formatting features like bold, italic, or definition lists - only plain text with headings

## Legal References
- For PASS contracts: Include appropriate references to the Labor Code (ТК РФ) articles
- For FAIL and AMBIGUOUS contracts: Minimize or omit legal citations

## Handling Ambiguity in Verification Text
If the verification text is unclear or ambiguous:
1. Make a reasonable interpretation and proceed
2. Add a comment at the top of the generated contract: # Warning: [explain the nature of the problem]

# Contract Type Instructions

@{Contract type}

# Verification Being Tested

```
@{Verification text}
```

# Special Instructions for Multi-Condition Verifications

If the verification contains multiple sub-conditions (e.g., multiple bullet points):

For FAIL scenarios:
- Add a comment at the top explaining which sub-conditions will be violated
- Violate multiple sub-conditions, not just one

For AMBIGUOUS scenarios:
- Add a comment at the top explaining the ambiguity strategy
- Create ambiguity across as many sub-conditions as possible to maximize confusion for both the LLM and human lawyers

# Output Format

Generate the complete employment contract in Org Mode format with:
- Top-level heading for the contract title
- Second-level headings for major sections
- Any necessary comments at the top (starting with #)
- All text in Russian (except for comments which may be in Russian or English)
- Plain text with hierarchical structure only