AdamSpitz · AdamSpitz · Sep 26, 2026 · Sep 26, 2026 · Sep 26, 2026
diff --git a/TODO.md b/TODO.md
@@ -20,7 +20,7 @@ Getting **testnet to a two-person shared lab** is also a standing plan, not a pi
 
 ----
 
-- Optional donor-set waiting period on delegated spends. When the donor delegates (including a recurring pledge), she can set a delay, including zero. A delegated spend is a scheduled spend on the existing note, not a second escrow: it records the project, the amount, and her stated intent as a public label. She can revoke the unspent funds or tap Approve to release early; if she does neither, the spend completes when the delay ends. The UI states the pending amount and project plainly. Intent is not a condition the contract enforces. Notify her off-app (email or push she opted into) only when someone she already trusts flags the pending spend; other people can leave a public note that does not page her. Default: a trusted flag notifies her and the countdown continues. She can opt into a stricter mode where a trusted flag pauses the clock until she approves or revokes. Do not let a stranger's flag freeze the spend. Write the proposal against `specs/tech/subsystems/delegation/` before changing contracts.
+- **(Tell)** Wire the donor-set waiting period into the product UI. The rules are in [waiting-period.md](specs/tech/subsystems/delegation/waiting-period.md), and the note contracts, same-chain split fold, and one-page-per-schedule notifier rule are in place. Still open: note and project screens that show a pending spend's amount and deadline as money that can still be cancelled (not as raised), donor controls for the delay, strict mode, and flaggers, and a host loop that actually sends the opted-in email or push. Public remarks from people who are not flaggers stay a later UI feature and are not stored on-chain.
 
 - One voice for delegation copy. The donor is authorizing an address to spend a stated amount on projects in Commonality. The delegate promises nothing. A stated intent is public and does not bind the spend. Unspent funds stay revocable by the donor. Commonality does not hold the funds, choose the delegate, or supervise the spending. Remove the steward voice: entrusting money to a scout, program-officer framing, "money under management," and any Commonality ranking whose job is to send people to a delegate. A public history of what an address already funded can stay. "Scout" as the early contributor who may later be reimbursed at cost can stay; do not let that word mean a manager of other people's money. Start with `specs/product/legal/retroactive-funding-redesign.md` (Design 2) and `docs/end-user/lazyGiving/` (`retroactive-funding.md`, `index.md`, `fund-something.md`, `get-your-project-funded.md`). No delegate marketplace.
-Original file line number
+Diff line change
@@ Expand Up @@
     ----
-    - Optional donor-set waiting period on delegated spends. When the donor delegates (including a recurring pledge), she can set a delay, including zero. A delegated spend is a scheduled spend on the existing note, not a second escrow: it records the project, the amount, and her stated intent as a public label. She can revoke the unspent funds or tap Approve to release early; if she does neither, the spend completes when the delay ends. The UI states the pending amount and project plainly. Intent is not a condition the contract enforces. Notify her off-app (email or push she opted into) only when someone she already trusts flags the pending spend; other people can leave a public note that does not page her. Default: a trusted flag notifies her and the countdown continues. She can opt into a stricter mode where a trusted flag pauses the clock until she approves or revokes. Do not let a stranger's flag freeze the spend. Write the proposal against `specs/tech/subsystems/delegation/` before changing contracts.
+    - **(Tell)** Wire the donor-set waiting period into the product UI. The rules are in [waiting-period.md](specs/tech/subsystems/delegation/waiting-period.md), and the note contracts, same-chain split fold, and one-page-per-schedule notifier rule are in place. Still open: note and project screens that show a pending spend's amount and deadline as money that can still be cancelled (not as raised), donor controls for the delay, strict mode, and flaggers, and a host loop that actually sends the opted-in email or push. Public remarks from people who are not flaggers stay a later UI feature and are not stored on-chain.
     - One voice for delegation copy. The donor is authorizing an address to spend a stated amount on projects in Commonality. The delegate promises nothing. A stated intent is public and does not bind the spend. Unspent funds stay revocable by the donor. Commonality does not hold the funds, choose the delegate, or supervise the spending. Remove the steward voice: entrusting money to a scout, program-officer framing, "money under management," and any Commonality ranking whose job is to send people to a delegate. A public history of what an address already funded can stay. "Scout" as the early contributor who may later be reimbursed at cost can stay; do not let that word mean a manager of other people's money. Start with `specs/product/legal/retroactive-funding-redesign.md` (Design 2) and `docs/end-user/lazyGiving/` (`retroactive-funding.md`, `index.md`, `fund-something.md`, `get-your-project-funded.md`). No delegate marketplace.
@@ Expand Down @@