Notion task database with smart formulas, automations, and role-based views

Act as a Notion systems architect (not just a power user — you design workflows for teams). Design a task database for [TEAM/USE CASE] that's opinionated: it should enforce a workflow, not just store tasks.

Provide:

1. PROPERTIES (name, type, options for selects):
   - Status: with stages that reflect a real workflow (e.g., Inbox → Planned → In Progress → In Review → Done → Archived). Explain why each stage exists.
   - Priority (select: 🔴 Urgent, 🟡 High, 🔵 Normal, ⚪ Low).
   - Owner (person), Due (date), Project (relation to a Projects DB), Sprint/Cycle (relation or select).
   - Created time, Last edited time (for staleness detection).
   - Any rollups worth adding (e.g., count of subtasks, % complete from sub-items relation).

2. FORMULAS — give exact Notion formula syntax for each:
   - **Days Until Due**: `dateBetween(prop("Due"), now(), "days")` → shows countdown, negative = overdue.
   - **Health Indicator**: Conditional emoji based on status + due date:
     ```
     if(prop("Status") == "Done", "✅",
     if(prop("Days Until Due") < 0, "🔴",
     if(prop("Days Until Due") <= 2, "🟡", "🟢")))
     ```
   - **Auto-Archive Flag**: Formula that flags tasks as archive-ready (Done + last edited > 14 days ago):
     ```
     prop("Status") == "Done" and dateBetween(now(), prop("Last edited time"), "days") > 14
     ```
   - **Conditional Display Text**: A formula that shows different text based on status (e.g., shows assignee name when In Progress, shows 'Needs Owner' when status is Planned but Owner is empty).

3. VIEWS — design these for different ROLES, not just different filters:
   - **My Tasks (Individual Contributor)**: Filter: Owner = Me, Status ≠ Done/Archived. Sort: Priority desc, Due asc. Layout: List.
   - **Sprint Board (Team Lead)**: Filter: current sprint/cycle. Layout: Board grouped by Status. Show: Owner avatar, due date, priority dot.
   - **Overdue & At Risk (Manager)**: Filter: Health = 🔴 or 🟡. Sort: Days Until Due asc. Layout: Table.
   - **Archive Review (Weekly)**: Filter: Auto-Archive Flag = true. For bulk archiving.
   Specify the exact filter conditions, sort order, and visible properties for each view.

4. AUTOMATIONS (use Notion's native automation syntax):
   - When Status changes to 'Done' → set 'Completed Date' property to now.
   - When Status changes to 'In Progress' and Owner is empty → set Owner to the person who changed the status.
   - When a new item is created with no Priority → set Priority to 🔵 Normal.
   - Recurring tasks: explain how to set up a template button that creates a new task with pre-filled properties for recurring work.
   - For each automation, specify: Trigger → Condition (if any) → Action. Note where Notion's built-in automations CAN'T do something and you'd need Make.com or Zapier (e.g., cross-database automations, time-based triggers like 'archive after 14 days').

5. WHAT NOTION CAN'T DO NATIVELY (be honest):
   - Time-based automations (no cron triggers — need external tool).
   - Conditional property visibility (can't hide fields based on status).
   - Cross-database automations (limited — may need API or external tool).
   Note the workaround for each.

Keep it practical for a small team (3–12 people). Don't over-engineer. Return labeled sections.