# Paper Trail - Game Design Document ## Executive Summary **Paper Trail** is a narrative puzzle game about navigating bureaucratic systems. Players take on the role of a "Fixer" at the Department of Ordinary Things, solving puzzles through paperwork, relationships, and creative problem-solving. The game explores themes of systemic inefficiency, creative problem-solving, and the gap between rules and outcomes. **Platform**: Single HTML5 file **Genre**: Puzzle/Narrative **Target**: Desktop browsers (Chrome, Firefox, Safari) --- ## Core Gameplay Loop ``` ┌─────────────────────────────────────────────────────────────┐ │ │ │ CASE FILE → ANALYZE → IDENTIFY SOLUTIONS → EXECUTE → │ │ │ │ COMPLIANT PATH ─────┐ │ │ ├──→ RESOLUTION → CONSEQUENCES → │ │ CREATIVE PATH ──────┤ (Trust, Progress, Endings) │ │ │ │ │ CONFRONTATIONAL ────┘ │ │ │ └─────────────────────────────────────────────────────────────┘ ``` ### Phase 1: Case File - Read narrative setup - Understand the problem - Identify key NPCs and deadlines - Review available resources ### Phase 2: Analyze - Examine forms and requirements - Identify obstacles and dependencies - Build NPC relationship potential - Choose approach strategy ### Phase 3: Execute - Fill forms (timed minigame) - Talk to NPCs (dialogue choices) - Gather resources (inventory) - Make critical decisions ### Phase 4: Resolution - Submit final solution - See immediate consequences - Track long-term effects - Unlock new cases --- ## Game Mechanics ### 1. Form System Forms are the primary puzzle mechanic. Each form has: - **Required fields**: Must be filled correctly - **Optional fields**: Can provide bonuses or loopholes - **Deadline**: Time pressure mechanic - **Approval rating**: Determines success chance **Filling Mechanics**: - Type answers (auto-complete suggestions) - Select from dropdowns - Attach documents (drag-and-drop) - Sign and submit **Error Types**: - **Syntax errors**: Wrong format (highlighted in red) - **Logic errors**: Inconsistent with other forms (yellow warning) - **Deadline errors**: Missing/expired dates (orange warning) - **Fraud indicators**: Suspicious patterns (red alert) ### 2. NPC Relationship System NPCs have three stats: - **Trust** (0-100): Willingness to help - **Authority** (0-5): Power to approve/deny - **Corruption** (0-5): Openness to bribes/favors **Trust Building Actions**: - Help with personal problems - Remember details from conversations - Complete favors for them - Show competence in shared tasks **Dialogue Choices**: - **Formal**: Safe, builds slow trust, maintains authority - **Casual**: Builds fast trust, risks overstepping - **Strategic**: Tailored to NPC personality, most effective - **Dismissive**: Burns trust, but may unlock confrontational paths ### 3. Time/Deadline System Each case has: - **Hard deadline**: Must submit before this or fail - **Soft checkpoints**: Milestones that affect outcome quality - **Time inventory**: Available time to distribute **Time Usage**: - Talking to NPCs (5-15 minutes per conversation) - Filling forms (2-10 minutes per form) - Searching/Investigating (variable) - Waiting/Procedural delays (simulated time) ### 4. Inventory System Players collect: - **Documents**: Forms, certificates, letters - **Items**: Physical objects needed for puzzles - **Contacts**: NPC phone numbers/addresses - **Knowledge**: Hints, tips, system knowledge ### 5. Consequence System Every action affects: - **Case outcome**: Success, partial, failure - **NPC relationships**: Trust gained/lost - **Department standing**: Career progression - **Story flags**: Unlock/hide future options --- ## Case Scenarios ### Case 1: "The Name Change" (Tutorial) **Difficulty**: Tutorial **Time Limit**: 30 minutes game time **NPCs**: 2 (Martha, Harold) **Setup**: Mrs. Eleanor Finch wants to correct her deceased husband's name on 47 forms. He was listed as "Robert James Finch" but his legal name was "Robert J. Finch." The Social Security office says the death certificate is wrong. The death certificate office says the hospital records are wrong. The hospital says they can't change records from 1987. **Puzzle Solution Paths**: **Compliant Path**: 1. Get court order for name correction 2. Amend death certificate (takes 6-8 weeks) 3. Use amended certificate for all 47 forms 4. Submit and wait **Creative Path**: 1. Find the "Common Name Variants" policy memo from 1995 2. File administrative correction request 3. Leverage Martha's forgotten favor 4. Expedite the process **Confrontational Path**: 1. File complaint with oversight board 2. Threaten media exposure 3. Demand meeting with supervisor 4. Force exception **NPCs**: **Martha Chen** (SS Office Clerk) - Authority: 3, Corruption: 1 - Personal: Dealing with her own paperwork nightmare - Key: Help her with her son's school enrollment forms **Harold Washington** (Supervisor) - Authority: 5, Corruption: 2 - Personal: Close to retirement, wants clean exit - Key: Show understanding of his constraints **Learning Outcomes**: - Form mechanics - NPC relationship basics - Multiple solution awareness - Time management intro --- ### Case 2: "The Permit Problem" **Difficulty**: Easy **Time Limit**: 45 minutes **NPCs**: 3 (Lisa, Mike, Diane) **Setup**: The Corner Café needs a permit to serve coffee. The health inspection requires proof of water access. The water access permit requires proof of floor drainage. The drainage permit requires... a coffee permit? You've been asked to untangle this circular dependency. **Puzzle Solution Paths**: **Compliant Path**: 1. Start from scratch with drainage permit 2. Complete all prerequisite chain (12 weeks) 3. Get final coffee permit 4. Grand opening delayed but legal **Creative Path**: 1. Find grandfather clause for existing businesses 2. Argue "serving" vs "preparing" distinction 3. Get variance approved by board vote 4. Use personal connection to Lisa **Confrontational Path**: 1. File suit claiming unconstitutional burden 2. Gather similar business owners as plaintiffs 3. Media campaign about "small business crushing regulations" 4. Political pressure on approvals office **NPCs**: **Lisa Rodriguez** (Inspector) - Authority: 3, Corruption: 2 - Personal: Wants to help but hands are tied by procedure - Key: She knows the system better than anyone **Mike Thompson** (Owner) - Authority: 0, Corruption: 0 - Personal: Struggling financially, time is money - Key: Source of information and side quests **Diane Walsh** (Board Member) - Authority: 5, Corruption: 1 - Personal: Big-picture thinker, hates paperwork - Key: Approves variances if convinced **Learning Outcomes**: - Circular dependency puzzles - Authority chain navigation - Creative interpretation of rules - Stakeholder management --- ### Case 3: "The Inherited Lease" **Difficulty**: Medium **Time Limit**: 60 minutes **NPCs**: 4 (Tom, Karen, Mr. Petrov, Judge Martinez) **Setup**: After Mr. Henderson died, his three children discovered he had secretly been living in a rent-controlled apartment for 30 years under a lease in his deceased wife's name. Legally, the lease should have transferred to them, but the super says only the wife was on the lease, and she died 15 years ago. The lease is worth approximately $200,000 in difference from market rate. **Puzzle Solution Paths**: **Compliant Path**: 1. Find succession rights law from 1985 2. File petition with housing court 3. Prove continuous residence 4. Pay back rent (~$15,000) 5. Fight through appeals (6 months) **Creative Path**: 1. Discover Mr. Henderson paid rent checks from joint account 2. Argue he was de facto tenant with implied consent 3. Leverage Tom's friendship with the super 4. Settle for 1-year lease with option to renew **Confrontational Path**: 1. Expose building owner's tax fraud (they underreported his unit) 2. Counterclaim harassment 3. Threaten rent strike with other tenants 4. Force buyout negotiation **NPCs**: **Tom Henderson** (Son) - Authority: 0, Corruption: 0 - Personal: Angry, wants justice - Key: Needs emotional support more than legal advice **Karen Chen** (Daughter) - Authority: 1, Corruption: 1 - Personal: Pragmatic, wants compromise - Key: Can bridge family conflicts **Mr. Petrov** (Superintendent) - Authority: 2, Corruption: 4 - Personal: Loyal to building owner but has own problems - Key: Knows where bodies are buried **Judge Martinez** - Authority: 5, Corruption: 0 - Personal: Fair but bound by law - Key: May offer creative solutions within her power **Learning Outcomes**: - Legal document interpretation - Family dynamics in systems - Strategic information gathering - Multi-party negotiation --- ### Case 4: "The Missing File" **Difficulty**: Medium-Hard **Time Limit**: 75 minutes **NPCs**: 5 (Sandra, James, Helen, Richard, Marcus) **Setup**: Your case file has disappeared from the archives. Without it, you can't prove your success on Case 3 (which you already solved). Your boss wants results. HR is asking questions. And you have a bad feeling someone removed that file on purpose. **Puzzle Solution Paths**: **Compliant Path**: 1. File request for records reconstruction 2. Wait for audit (6-8 weeks) 3. Provide alternative documentation 4. Accept reduced credit **Creative Path**: 1. Reconstruct the file from memory 2. Find email chain backup in sent folder 3. Get NPC statements confirming your work 4. Present reconstructed evidence **Confrontational Path**: 1. Check security footage (bribe Marcus) 2. Trace who accessed your files 3. Confront James publicly 4. Force investigation **NPCs**: **Sandra Cole** (HR) - Authority: 3, Corruption: 1 - Personal: Covering her department's mistakes - Key: Has authority to authorize investigation **James Wright** (Colleague) - Authority: 1, Corruption: 2 - Personal: Jealous of your success - Key: May have taken the file (or knows who did) **Helen Park** (Archivist) - Authority: 2, Corruption: 0 - Personal: Meticulous, feels guilty about losing it - Key: Can help reconstruct records **Richard Stone** (Boss) - Authority: 4, Corruption: 1 - Personal: Needs your success for his promotion - Key: Can protect you if you solve this **Marcus Webb** (Security) - Authority: 1, Corruption: 5 - Personal: Gambling debts, needs money - Key: Has access to security footage **Learning Outcomes**: - Investigation mechanics - Evidence reconstruction - Reading people's motivations - When to fight vs. adapt --- ### Case 5: "The Whistleblower" **Difficulty**: Hard **Time Limit**: 90 minutes **NPCs**: 6 (Diana, Councilman Ross, Martha, Chief Davis, Reporter Kim, Governor's Office) **Setup**: Diana, a longtime employee, has discovered that the Department has been falsifying inspection records to approve buildings that fail safety codes. She wants to expose this but fears retaliation. She comes to you for help navigating the whistleblowing process while protecting her job, or at least her pension. **Puzzle Solution Paths**: **Compliant Path**: 1. File official whistleblower complaint 2. Wait for internal investigation (months) 3. Protect her through procedural safeguards 4. Hope system protects her **Creative Path**: 1. Find journalists/media contacts 2. Build evidence package carefully 3. Time disclosure with political pressure 4. Negotiate protection + severance **Confrontational Path**: 1. Go directly to media with evidence 2. Force immediate investigation 3. Blow up the department 4. Diana loses job but gains public support **Multiple Endings**: - **Justice**: Diana exposed wrongdoing, reforms enacted - **Survival**: Diana keeps job, changes happen slowly - **Martyr**: Diana loses job, nothing changes immediately, but seeds planted - **Complicit**: Diana convinced to stay silent, your career advances - **Destroyed**: Both Diana and you lose your jobs, but department exposed **NPCs**: **Diana Foster** (Whistleblower) - Authority: 1, Corruption: 0 - Personal: Torn between duty and survival - Key: Her choice affects ending **Councilman Ross** (Political) - Authority: 5, Corruption: 3 - Personal: Wants to use scandal for political gain - Key: Can pressure for reform or bury story **Martha Chen** (Former Case 1 NPC) - Authority: 3, Corruption: 1 - Personal: Now in oversight position - Key: Can investigate if given evidence **Chief Davis** (Department Head) - Authority: 5, Corruption: 2 - Personal: Ordered the falsifications, fears exposure - Key: Antagonist, will try to stop you **Reporter Kim** - Authority: 0, Corruption: 0 - Personal: Wants the story, ethics vary - Key: Can publish or protect sources **Governor’s Office** - Authority: 5, Corruption: 1 - Personal: Wants scandal contained - Key: Can force reforms or silence **Learning Outcomes**: - Systemic corruption themes - Risk assessment in whistleblowing - Political dimensions of justice - What "fixing systems" actually means --- ## NPC Profiles ### Core NPCs (Appear in Multiple Cases) **Trust Mechanics**: - Starting trust varies by NPC - Trust affects willingness to help - Trust can be negative (enemies) - Trust decay over time **NPC Personality Types**: 1. **Rule Follower** (Authority: 4, Trust threshold: 60) - Values: Procedure, fairness, precedent - Response: Formal, predictable - To influence: Show you respect the system 2. **Helpful Pragmatist** (Authority: 3, Trust threshold: 40) - Values: Outcomes, efficiency, people - Response: Casual, solution-focused - To influence: Focus on helping people 3. **Cynical Insider** (Authority: 4, Trust threshold: 70) - Values: Information, leverage, survival - Response: Cautious, transactional - To influence: Offer useful information 4. **Idealist** (Authority: 2, Trust threshold: 50) - Values: Justice, truth, reform - Response: Passionate, impatient - To influence: Share their vision 5. **Burnt Out** (Authority: 3, Trust threshold: 30) - Values: Peace, money, escape - Response: Tired, bitter - To influence: Appeal to their self-interest 6. **Rising Star** (Authority: 4, Trust threshold: 55) - Values: Career, reputation, advancement - Response: Ambitious, calculating - To influence: Show how helping you helps them --- ## Dialogue System ### Dialogue Tree Structure ``` START ├── GREETING (varies by relationship) │ ├── CASUAL RESPONSE (if trust > 40) │ │ ├── SMALL TALK │ │ │ ├── (Build Trust) │ │ │ └── (Personal Info) │ │ └── DIRECT QUESTION │ │ ├── INFORMATION REQUEST │ │ ├── FAVOR REQUEST │ │ └── LEVERAGE PLAY │ └── FORMAL RESPONSE (if trust <= 40) │ ├── PROCEDURAL STATEMENT │ ├── ESCALATION OPTIONS │ └── DEAD END │ ├── TOPIC INTRODUCTION │ ├── EXPERT OPINION (if knowledge check) │ ├── PERSONAL STORY (if relationship check) │ └── DEFLECTION (if trust too low) │ └── CONCLUSION ├── NEXT STEPS ├── PROMISE └── GOODBYE ``` ### Dialogue Mechanics **Choice Types**: - **Informative**: Reveals information - **Emotional**: Affects relationship - **Strategic**: Opens/closes paths - **Risky**: High reward, high risk **Dialogue Resources**: - Time (each conversation costs time) - Knowledge (some questions need prerequisites) - Trust (low trust = limited options) - Items (evidence can change conversations) --- ## UI/UX Design ### Screen Flow ``` ┌─────────────┐ │ TITLE │ │ SCREEN │ └──────┬──────┘ │ ▼ ┌─────────────┐ │ TUTORIAL │──────────────┐ │ INTRO │ │ └──────┬──────┘ │ │ │ ▼ │ ┌─────────────┐ │ │ CASE │ │ │ SELECT │ │ └──────┬──────┘ │ │ │ ▼ │ ┌─────────────┐ │ │ CASE │ │ │ BRIEFING │ │ └──────┬──────┘ │ │ │ ▼ │ ┌─────────────┐ │ │ PUZZLE │◄─────────────┤ │ SCREEN │ │ └──────┬──────┘ │ │ │ ▼ │ ┌─────────────┐ │ │ RESULTS │──────────────┘ │ SCREEN │ └──────┬──────┘ │ ▼ ┌─────────────┐ │ NEXT │ │ CASE │ └─────────────┘ ``` ### Visual Design Language **Color Palette**: - Primary: `#2D3436` (charcoal gray) - Secondary: `#636E72` (medium gray) - Background: `#DFE6E9` (light gray) - Paper: `#FFEAA7` (manila folder yellow) - Accent Blue: `#0984E3` (formal/government) - Accent Red: `#D63031` (urgent/denied) - Accent Green: `#00B894` (approved/success) - Accent Yellow: `#FDCB6E` (warning/creative) - Text: `#2D3436` (primary), `#636E72` (secondary) **Typography**: - Headers: 'Courier Prime', monospace (typewriter feel) - Body: 'Inter', system-ui, sans-serif - Forms: 'Courier New', monospace (official documents) - UI: 'Inter', sans-serif **Visual Elements**: - Paper textures (subtle noise) - Coffee stains (aesthetic, not gameplay) - Sticky notes (player notes/reminders) - Rubber stamps (approval/denial states) - Folders and clips (organization) - Office supplies (decorative) --- ## Technical Architecture ### State Management ```javascript GameState = { currentCase: null | CaseID, completedCases: [], currentPhase: 'menu' | 'briefing' | 'puzzle' | 'dialogue' | 'results', inventory: Item[], npcRelationships: { [npcId]: { trust: number, authority: number, corruption: number } }, flags: { [flagId]: boolean }, timeRemaining: number, endings: { type: string, conditions: [] } } ``` ### Save System - LocalStorage for persistence - Auto-save after each case - Manual save during cases - Multiple save slots (3) ### Performance Targets - Initial load: < 3 seconds - Save/load: < 500ms - Transitions: < 300ms - Input response: < 100ms --- ## Endings & Consequences ### Ending Types 1. **Systemic Change**: You've fixed a broken process 2. **Personal Victory**: You've succeeded within the system 3. **Pyrrhic Victory**: You've won, but at great cost 4. **System Wins**: The system absorbed your effort 5. **Martyrdom**: You've exposed the system, even if you lose ### Tracking Variables - Cases completed: X/5 - NPCs helped: X/6 - Puzzles solved via confrontation: X - Rules creatively interpreted: X - System violations: X - Trust maintained: X --- ## Success Metrics ### Completion - Can complete all 5 cases - Can achieve all 5 ending types - Can solve each case 3 different ways ### Engagement - Average playtime: 3-5 hours - Replayability: Multiple paths encourage replays - Emotional resonance: Players reflect on real bureaucracy ### Technical - Loads in all modern browsers - No console errors - Responsive to window resize - Sound toggleable --- ## Future Expansion Potential ### Potential Additional Cases: - Immigration paperwork nightmare - Small business license maze - Environmental permit hell - Healthcare billing disputes - Benefits application gauntlet ### Potential Features: - Multiplayer "case competition" - Custom case creator - Real-world form integration - Documentary/story mode --- *"The system isn't broken. It's working exactly as designed. The question is: who designed it, and for whom?"* --- **Document Version**: 1.0 **Created**: 2026-03-22 **Author**: AI Agent (Maya)