📜Contract

Relationship

👑This feature requires a Kinkster membership.

---

📋 Overview

The Contract Module provides a comprehensive BDSM contract creation and management system for formal power exchange relationships. Users can create detailed contracts with customizable sections covering various aspects of the dynamic including roles, responsibilities, boundaries, consent, communication protocols, and more. Features include interactive step-by-step contract building in private threads, mutual consent requirements at every stage, contract editing with amendment tracking, contract termination by either party, automatic DM delivery of finalized contracts, and unique contract ID generation for reference. Both dominant and submissive must agree to each section and the final contract before it's stored and delivered.

---

⚙️ How It Works

Contract Creation Flow:

Step 1 - Initiation:

• Dominant executes /contract new

• Private thread created automatically

• Dominant mentions the submissive partner

• System validates the mentioned user (not bot, not self, no existing contract)

Step 2 - Submissive Confirmation:

• Submissive receives ping in private thread

• "I am here" button appears

• Submissive must confirm participation

• Process cannot continue without confirmation

Step 3 - Contract Building:

• System presents multiple contract sections sequentially

• Each section includes:

  • Agreement statement

  • Agreement question

  • Include/Exclude/Skip buttons

• If included, both parties discuss and enter mutual agreement

• Progress indicator shows current step out of total

• Either party can timeout or exclude sections

Step 4 - Review & Consent:

• Complete contract displayed in thread

• Both parties review all agreed sections

• Submissive presented with Accept/Decline buttons

• Contract locked during review period

Step 5 - Finalization:

• If accepted:

  • Unique contract ID generated (UUID)

  • Contract stored in database

  • Signatures and dates added

  • 2-minute wait period before DM delivery

  • Both parties receive full contract via DM

  • Thread archived automatically

• If declined:

  • Contract not stored

  • Decline notification sent

  • Thread archived

Contract Sections System:

The system walks through predefined contract steps covering:

• Role definitions and expectations

• Boundaries and limits

• Communication protocols

• Safety measures and safe words

• Duration and termination clauses

• Privacy and discretion

• Other relationship-specific agreements

Each section can be:

• Included: Both parties write agreement text

• Excluded: Section not part of contract

• Skipped: Move to next section without including

Contract Editing System:

Edit Flow:

1. Dominant executes /contract edit with contract number

2. System validates contract exists

3. Private thread created

4. Submissive must confirm participation

5. Existing agreements shown for each section

6. Both parties can modify any section

7. Same review and consent process as new contracts

8. Amendment date added to contract

9. Updated contract delivered via DM

Edit Features:

• Shows previous agreements for reference

• Can add previously excluded sections

• Can remove previously included sections

• Can modify existing agreement text

• Maintains original creation date

• Records amendment date

Contract Termination:

Termination Process:

• Either party can terminate using /contract terminate

• Must provide valid contract number

• Only parties involved can terminate

• Contract removed from database immediately

• Both parties receive termination confirmation via DM

• 2-minute delay before confirmation sent

Private Thread Management:

Thread Features:

• Created automatically in current channel

• Named: "[User]'s Contract"

• Private thread type (invite-only)

• Locked during review periods

• Archived after completion/decline

• Prevents outside interference

Database Storage:

Contract Document Structure:

{
  "_id": unique_contract_id (UUID),
  "dome_id": dominant_user_id,
  "sub_id": submissive_user_id,
  "guild_id": server_id,
  "created_at": timestamp,
  "contract_elements": {section_name: agreement_text},
  "amendent_date": timestamp (if edited)
}

Validation & Error Handling:

User Validation:

• Cannot create with bots

• Cannot create with self

• Cannot create duplicate contracts

• Member must exist in server

Location Validation:

• Cannot use inside existing threads

• Must use in regular text channels

Contract Validation:

• Must include at least one section

• Contract number must be valid

• Only participants can edit/terminate

Consent Requirements:

Multiple Consent Checkpoints:

1. Submissive confirms participation initially

2. Both parties agree on each section content

3. Both parties review complete contract

4. Submissive explicitly accepts final contract

5. Either party can decline at any point

DM Delivery System:

Delivery Process:

• 2-minute wait after finalization

• Contract split into 2000-character chunks

• Sent sequentially to both parties

• Includes separator lines between sections

• Graceful handling if DMs closed

• Warning to open DMs provided in advance

Cooldown Management:

Cooldown Behavior:

• Normal cooldown: 10 minutes

• Resets on validation failures

• Resets on timeouts

• Resets on user errors

• Prevents spam while allowing retries

---

🔑 Key Commands

/contract new

Description: Create a new BDSM contract with a submissive Access: All members (as dominant) Cooldown: 10 minutes per user Default Permissions: None required

Process Overview:

Step 1 - Thread Creation:

Confirmation Embed:
Title: 📜 Contract Thread Created
Description: "The contract has been moved to your [private thread]({link}) for easier management."
Color: Blue
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Delivery: Ephemeral

Step 2 - Partner Selection:

• Prompt: "Hey {user}, i'll help you set up a contract. Mention the other party, and we'll get started."

• Timeout: 120 seconds

• Validation: Must be valid user mention

• Format: @username

Step 3 - Section Building:

Section Embed (per step):
Title: Not used
Description:
  ### {Section Name}
  **Agreement:**
  {Agreement statement}
  *Agreement Question:*
  {Question text}
Color: Blue
Footer: "Made by DIVINITY • Pleasure Corner • Step {current}/{total}"
Timestamp: Current UTC time
Buttons: Include | Exclude | Skip

Step 4 - Final Review:

Submit Embed:
Title: ✅ Contract Created
Description: "Your contract has been successfully created. You will receive a DM confirmation shortly.
> **NOTE:** Please ensure your DMs are open within the next 2 minutes to receive the contract."
Color: Green
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time

Step 5 - Submissive Consent:

• Contract displayed in full text (chunked if needed)

• Buttons: ✅ Accept | ❌ Decline

• Thread locked during decision

• Only submissive can interact

Success Outcome:

Completion Embed:
Title: ✅ Contract Created
Description: "Your contract has been created. You'll receive a DM confirmation shortly.
> **NOTE:** Make sure your DMs are open within the next 2 minutes to receive the contract, or you won't be able to."
Color: Green
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time

Contract Format in DM:
--------------------------------------------
[Introduction paragraph]

### 1. {Section Name}

**Agreement:**
{Agreement statement}
*Agreement Question:*
{Question text}
🖋️ **Your mutual agreement:**
{Custom agreement text}

[Repeat for all sections]

🖊️ **Signatures**
By signing below, both parties agree to the terms outlined in this contract and commit to upholding their respective roles and responsibilities. Consent is paramount, and both parties have the right to revisit or renegotiate any part of this agreement at any time.

Dominant: @username
Date: YYYY/MM/DD

Submissive: @username
Date: YYYY/MM/DD

Contract Number: ``{UUID}``

**Made by {Bot Name}**

Decline Outcome:

Decline Embed:
Title: ❌ Contract Declined
Description: "Consent for this contract has been declined. Thank you for your time."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Thread archived

Error Responses:

Thread Location Error:

Title: ❌ Invalid Location
Description: "This command cannot be used inside a thread."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Delivery: Ephemeral

No Mention Error:

Title: ❌ Contract Creation Failed
Description: "Please mention a user to create a contract with. You can try again by typing `/contract new`."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Bot Mention Error:

Title: ❌ Contract Creation Failed
Description: "Contracts cannot be created with bots."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Self Mention Error:

Title: ❌ Contract Creation Failed
Description: "You cannot create a contract with yourself."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Existing Contract Error:

Title: ℹ️ Contract Exists
Description: "You already have an existing contract with this user. To edit it, use `/contract edit`."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Incomplete Contract Error:

Title: ❌ Incomplete Contract
Description: "You need to include at least one section in your contract."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time

Timeout Error:

Title: ⏰ Time Expired
Description: "The contract creation has timed out. You can try again by typing `/contract new` when you're ready."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time

---

/contract edit

Description: Modify an existing contract Access: Dominant of the contract Cooldown: 10 minutes per user Parameters:

• contract_number (required): The unique contract ID found in the contract

Process Overview:

Same process as /contract new but with modifications:

• Retrieves existing contract data

• Shows previous agreements for each section

• Allows modification of any section

• Adds amendment date to contract

• Maintains original creation date

Edit Section Display:

Section Embed:
Title: 📋 {Section Name}
Description:
  **Agreement:**
  {Agreement statement}
  *Agreement Question:*
  {Question text}
  🖋️ **Your mutual agreement:**
  {Previous agreement or "No Previous Input."}
Color: Blue
Footer: "Made by DIVINITY • Pleasure Corner • Step {current}/{total}"
Timestamp: Current UTC time
Buttons: Include | Exclude | Skip

Success Outcome:

Update Embed:
Title: ✅ Contract Updated
Description: "Your contract has been successfully edited. You will receive a DM confirmation shortly.
> **NOTE:** Please ensure your DMs are open within the next 2 minutes to receive the updated contract."
Color: Green
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time

Contract includes:
- Original creation date
- Amendment date
- Updated sections
- Same contract number

Error Responses:

Invalid Contract:

Title: ❌ Invalid Contract
Description: "The contract number you provided is invalid. To create a new contract, use `/contract new`."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Member Not Found:

Title: ⚠️ Member Not Found
Description: "The submissive from this contract is no longer a member of this server. To terminate the contract, use `/contract terminate`."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Update Declined:

Title: ❌ Update Declined
Description: "Consent for this contract update has been declined. Thank you for your time."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Thread archived

---

/contract terminate

Description: Terminate a contract Access: Either party in the contract Cooldown: 10 minutes per user Parameters:

• contract_number (required): The unique contract ID found in the contract

Termination Process:

1. Validates contract exists

2. Confirms user is a party to the contract

3. Deletes contract from database immediately

4. Sends confirmation to user

5. Waits 2 minutes

6. Sends DM confirmation to both parties

Success Response:

Termination Embed (in channel):
Title: ✅ Contract Terminated
Description: "Contract #``{contract_number}`` has been successfully terminated. You will receive a DM confirmation shortly.
> **NOTE:** Please ensure your DMs are open within the next 2 minutes to receive the confirmation."
Color: Green
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Delivery: Ephemeral

DM Notification:
Title: 📜 Contract Terminated
Description: "Your contract #``{contract_number}`` has been terminated. Thank you for your time."
Color: Blue
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Sent to: Both parties

Error Responses:

Invalid Contract:

Title: ❌ Invalid Contract
Description: "The contract number you provided is invalid. To create a new contract, use `/contract new`."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

Unauthorized:

Title: 🚫 Unauthorized
Description: "You do not have permission to terminate this contract."
Color: Red
Footer: "Made by DIVINITY • Pleasure Corner"
Timestamp: Current UTC time
Cooldown: Reset to 10 seconds

---

👥 Who It's For

Dominants: Create, edit, and terminate contracts with submissives

Submissives: Participate in contract creation, provide consent, terminate if needed

Contract Partners: Both parties have equal ability to terminate contracts

All Members: Can create contracts if taking dominant role

---

💡 Why This Feature

Formalizes power exchange relationships with clear documentation. Ensures mutual consent at every stage of the process. Provides structured framework for discussing boundaries and expectations. Creates legally-formatted document for reference. Allows relationship evolution through editing system. Protects both parties through explicit consent requirements. Encourages thorough communication before commitment. Maintains privacy through private threads and DM delivery. Enables clean relationship termination when needed. Promotes responsible BDSM practices.

---

Made by DIVINITY • Pleasure Corner