diff --git a/README.md b/README.md
index 190dc6b4..2b659614 100644
--- a/README.md
+++ b/README.md
@@ -634,16 +634,28 @@ notification and a live toast carrying its message (the **Reminders** notificati
 you can toggle like any other on your profile), in addition to the result appearing in the
 terminal.
 
-**Scheduling is restricted to administrators**, and every scheduled task is bounded. Members can
-list and delete tasks they already own but cannot create, change, or trigger one. A repeating
-task must leave at least fifteen minutes between runs, carries a maximum number of executions,
-and expires at most thirty days after its first run, so nothing runs forever. A task that fails
-several times in a row, whose owner has been inactive for a month, whose owner stops being an
-administrator, or that passes its automation spend limit is disabled automatically with the
-reason recorded in the audit log. Across the whole platform only a few scheduled tasks run at
-the same time, handed out one at a time per owner, so a single account can never monopolise the
-scheduler. Administrators see every task, its owner, and its bounds at **Admin -> Devii tasks**,
-where any task can be disabled or deleted, and the same is available from the command line with
+**Every account may schedule, within two rolling 24-hour quotas.** A member may create 5 tasks
+and execute 10 task runs per 24 hours; an administrator may create 5 and execute 100. Deleting a
+task does not give a creation slot back, and a run that would exceed the quota is **postponed
+until a slot frees, never dropped or disabled** - the task simply runs later, and the exact time
+its next slot opens is reported. All four numbers are adjustable on the Devii service page, where
+0 means unlimited. Guests cannot schedule at all.
+
+**A task knows when it is running as a task, and a member's task cannot spawn more tasks.** While
+a scheduled run is executing, creating a task, re-enabling one, or triggering one immediately is
+refused for members - so a member's automation can never fan out into more automation. An
+administrator's task may schedule follow-up work, and every new task and run still counts against
+the same quotas. The assistant is told which environment it is in, and the restriction itself is
+enforced by the server rather than by the instruction, so no prompt can talk its way around it.
+
+Every scheduled task is also bounded in time: a repeating task must leave at least fifteen minutes
+between runs, carries a maximum number of executions, and expires at most thirty days after its
+first run. A task that fails several times in a row, whose owner has been inactive for a month, or
+that passes its automation spend limit is disabled automatically with the reason recorded in the
+audit log. Across the whole platform only a few scheduled tasks run at the same time, handed out
+one at a time per owner, so a single account can never monopolise the scheduler. Administrators
+see every task, its owner, its 24-hour usage, and its bounds at **Admin -> Devii tasks**, where any
+task can be disabled or deleted, and the same is available from the command line with
 `devplace devii tasks`.
 
 Configuration on the Services tab:
@@ -668,6 +680,10 @@ Configuration on the Services tab:
 | `devii_rsearch_timeout` | `300` | Read timeout (seconds) for `rsearch_*` calls; web-grounded answers can take minutes; minimum five minutes |
 | `devii_email_enabled` | on | Enable the email tools (`email_*`) for signed-in users |
 | `devii_email_timeout` | `30` | Connection/read timeout (seconds) for IMAP and SMTP calls |
+| `devii_task_member_create_24h` | `5` | Tasks a member may create per rolling 24 hours (`0` = unlimited) |
+| `devii_task_member_runs_24h` | `10` | Task runs a member may execute per rolling 24 hours; excess runs are postponed |
+| `devii_task_admin_create_24h` | `5` | Tasks an administrator may create per rolling 24 hours |
+| `devii_task_admin_runs_24h` | `100` | Task runs an administrator may execute per rolling 24 hours |
 | `devii_task_max_concurrent` | `4` | Scheduled tasks running at once across all owners, handed out round-robin, one at a time per owner |
 | `devii_task_max_per_owner` | `10` | Active scheduled tasks one administrator may hold (`0` = no cap) |
 | `devii_task_daily_usd` | `0.5` | Rolling 24h spend cap for scheduled runs, separate from the interactive quota (`0` = unlimited) |