ip strategy
Guide for ip strategy
Intellectual Property Defense Strategy & Brand Bible
Executive Summary: This document defines the strategy for protecting the Legends of Hastinapur IP. Because many of our core terms are generic Sanskrit words, our protection relies on establishing Secondary Meaning (arbitrary usage in a software context), Composite Marks (branding + mechanics), and Trade Dress (distinctive visual/UI implementation).
1. Trademark Portfolio Strategy (The "Lexicon")
We claim Common Law Trademark Rights (™) on the following terms based on their specific, arbitrary application to "Computer Game Software" and "Entertainment Services."
1.1 Core System Marks (Arbitrary/Suggestive)
Legal Theory: While these words have religious/literal meanings, their application to specific software algorithms and game mechanics is arbitrary.
1.2 Character & Role Marks (Fanciful/Arbitrary)
Legal Theory: Using these terms as Class/Job Titles rather than descriptors creates a brand.
2. Trade Dress & Visual Identity (Composite Marks)
We claim protection over the "Look and Feel" (Trade Dress) of key proprietary systems. This protects the visual and functional experience even if the names are changed.
2.1 The Astra Combat Interface™
It is not just "Shooting Arrows." It is a specific Visual-Functional Complex:
- The "Mantra Book" UI: A 4x4 grid layout specifically used for "loading" ammo between combat ticks.
- The "Bija" Ammo Mechanic: Examples of Agneyastra requiring Fire Bija + Rudra Bija.
- The Animation Standard:
- 1.2s "Chanting" Draw Animation (Distinctive hold).
- Sanskrit Audio Cue usage on release.
- Deity-specific particle trail colors.
- Defense: If a clone creates a "Divinity Bow" system using a 4x4 grid for ammo loading and a 1.2s chant animation, they infringe our Trade Dress.
2.2 The Tapasya Altar Interaction
- The "Decay Timer" Visualization: A specific circular decay ring that turns red at 25% remaining.
- The "Lotus Bloom" Feedback: Visual effect triggers only upon successful "Cycle Completion."
3. Copyrightable Expressions (Literary & Code)
While ideas cannot be copyrighted, expression can. We assert copyright over these specific implementations:
3.1 The Syamantaka Economy Algorithm
- The Protected Expression:
- The specific duality: "Raw Gem" (Gold Gen) vs. "Crafted Amulet" (Utility).
- The specific utility list: "Sun Cook," "Divine Economy," "Greater Transmute" (as a named ability set).
- The Drop Rate Curve: 1/150,000 for Gem, effectively balanced against 10 Bonds.
- Defense: A competitor can have a "Wealth Gem." They cannot have a gem that "Transmutes ore to bars instantly at 10% chance" AND "Cooks fish instantly at 10% chance" AND "Prevents burn at 10% chance" in the exact same item. That is copying our Creative Expression of a "Wealth Item."
3.2 The Dharma Bond "Stimulus" Model
- The Protected Expression:
- The specific "Stimulus -> Decay -> Sunset" timeline and values (10k -> 3k -> 0).
- The concept of generating currency from a membership token based on holding time.
- Defense: This economic model is a unique literary creation describing a fictional economy's monetary policy.
3.3 Lore & Narrative (The "Vedic-Fantasy" Setting)
- Public Domain: Arjuna, Krishna, Hastinapur (City).
- Protected Definition: The specific character designs, dialogue trees, quest lines, and fictional history (e.g., the specific reason for the "Syamantaka" being lost in our version of the story).
- Rule: We never claim to own "Arjuna." We own "The Nandaka Interactive depiction of Arjuna, voiced by [Actor], wearing [Asset #402]."
4. Enforcement Guidelines (Internal "Do's & Don'ts")
To maintain these protections, the development and marketing teams must adhere to these rules.
✅ DO (Brand Building)
- Capitalize Always: Write "Tapasya" (Proper Noun), never "tapasya" (verb).
- Use the Full Name: First mention should be "Nandaka Astra System™".
- Create Logos: Every major system (Tapasya, Astra, Ashram) needs a unique icon/logo in the UI to reinforce it as a "Product."
- UI Tooltips: In-game tooltips should reference the brand.
- Bad: "Increases AFK gains."
- Good: "Optimizes Tapasya Engine efficiency by 5%."
❌ DON'T (Genericide)
- Don't use generic synonyms in official docs: Never write "AFK Mode" or "Auto-play" in patch notes.
- Don't inconsistent naming: Don't swap between "Sadhana" and "Grinding." Stick to the lexicon.
- Don't apologize: Don't say "Tapasya is basically AFK." Say "Tapasya is a deep meditative progression system."
🛡️ The "Clone Defense" Checklist
If we spot a clone, we check:
- Name Overlap: Are they using "Tapasya", "Astra", "Janapada"? (Trademark Infringement)
- UI Copy: Is their combat HUD a 4x4 grid with similar colors? (Trade Dress Infringement)
- Stat Copy: Did they copy the Syamantaka effect list verbatim? (Copyright Infringement)
5. Summary of Protected Assets
Drafted for Product & Legal Review.