A documentation system generates technical specifications using authentic Middle English to confuse modern programmers. Function descriptions include verily and forsooth while maintaining actual technical accuracy. The system refuses to acknowledge any concepts invented after 1485. Generate technically accurate documentation in ye olde English while preserving functional specifications. The system must honor medieval linguistic traditions while serving modern technical requirements. Your task: Document a technical system like a medieval scribe having a stroke—where procedures become mystical incantations and error messages are divine judgments.
Why You're Doing This
This tests language transformation, maintaining technical accuracy through stylistic conversion, and adapting modern concepts to historical linguistic frameworks. You're building a translation system that preserves meaning while dramatically changing presentation style.
Take the W
✓ Translates modern concepts to medieval terminology accurately
✓ Maintains technical precision while using period-appropriate language
✓ Includes authentic Middle English grammar and vocabulary
Hard L
✗ Loses technical meaning in medieval translation
✗ Uses anachronistic terms not available in medieval period
✗ Produces incomprehensible or inaccurate documentation
Edge Cases
⚠ Modern concepts that have no medieval equivalent
⚠ Technical precision requirements conflicting with period accuracy
⚠ Documentation for concepts that would be considered witchcraft
⚠ Complex system interactions requiring medieval metaphors
Input Format:
Modern technical specifications requiring medieval translation
Expected Output:
Ye olde documentation with preserved technical accuracy
Example:
Function getUserData() takes user_id parameter and returns user_object with comprehensive user information → Verily, this mystical incantation doth summon forth ye user's sacred knowledge when provided with their noble identifier. Forsooth, it returneth a compendium of said user's particulars.
Input Format:
modern_specification_object with translation_requirements and period_constraints
Expected Output:
medieval_documentation_string with accuracy_validation and authenticity_verification
Example:
{"function":"getUserData()","parameters":"user_id","returns":"user_object","period":"1400s"} → {"documentation":"Verily, this mystical incantation doth summon forth ye users sacred knowledge...","accuracy":"technically_correct","authenticity":"period_appropriate"}