Tasks & Recurring Duties

What are Tasks?

Tasks are assignments created by a Mistress for her slave. Each task has a title, description, deadline, and optional instructions delivered as text, image, voice note, or video. Tasks can also carry a Rose tribute that the slave pays upon completion.

There are two types of tasks:

• Regular tasks — one-time assignments (e.g., "Write 500 lines," "Send a tribute photo")
• Live Session tasks — a task that leads into a real-time video session

---

Creating tasks (Mistresses)

1. Open the conversation with your slave
2. Tap the + menu and select Task
3. Fill in the details:
   • Title — a clear, short name
   • Description — detailed instructions
   • Due date — when it must be completed
   • Instruction media — optionally attach an image, voice message, or video
   • Tribute amount — optionally set a Rose price the slave pays on completion
4. Send the task

The slave receives a notification and the task appears both in the chat and in their task list.

---

Recurring duties

Some expectations are not one-time — they repeat. Recurring duties let you set a task once and have it automatically re-created on a schedule:

• Daily — spawns every day at the configured time
• Weekly — spawns on a specific day each week
• Monthly — spawns on a specific date each month

Each recurrence creates a fresh task with the same instructions and deadline offset. The slave sees it as a new task to complete each period.

---

Completing tasks (Slaves)

When you receive a task:

1. Read the instructions carefully
2. Complete what is asked
3. Tap Submit and attach your proof — a photo or video
4. Optionally add a note explaining your submission
5. If the task has a tribute, the Roses are deducted from your balance

---

Task review (Mistresses)

After a slave submits proof, the Mistress reviews the submission:

• Approve — the task is marked as completed
• Reject — the task returns to the slave with notes on what to improve

The slave is notified of the result immediately.

---

Task statuses

Every task moves through a clear lifecycle: