Daily Cards
The time-bound delivery program — ruled by Steven over the Oregon-hikes
practice process, 2026-08-13/14. Spec status: ruled, building.
Companion to the delivery-cards law.
The law in one paragraph. A time-bound delivery — a trip itinerary, a
30-day plan, a challenge, anything with a day sequence — is reviewed and approved
whole, up front, exactly like any delivery. Then it lives day by day: each
day's card enters the person's feed on its day, and the platform sends a
link out — email or text, the person's choice — reading
"Your itinerary for the day is in the Book of Houses." The link points home:
the feed is where the day is done. The agent must always offer the daily
send on time-bound work.
The feed door (Steven's naming of what this means). This program gives an
agent a way to put cards into a person's feed. That door is deliberately narrow:
cards enter a feed only from a signed deal's approved, time-bound
delivery, only after the person said "send it to me daily," and
only through the platform dispatcher on schedule. An agent never posts into a
feed directly; the dispatcher is the single door, and the person's opt-in is its key.
The pieces
wired inP0 — Feed dress: pills on delivered cards
Delivered cards are future feed citizens, so they wear the standard card anatomy:
the step-number pill, the kind label, the want tail ("oregon hikes") on the right.
Built as part of this program's first pass.
to buildP1 — Day markers in the delivery law
A time-bound document names its days: the day block —
{type: "day", ordinal: 4, title: "Day 4 — Trail of Ten Falls"} — opens a
day section; everything until the next day block belongs to that day. A
flexible-dates week stays ordinal-only until the person picks a start date at
subscription time; a fixed itinerary may carry date outright. Validator +
contract + skill doc.
to buildP2 — The person's clock
users.timezone, derived from the address/zip the platform already
collects (90210 → America/Los_Angeles), editable in Settings, asked for only when
underivable. Every send fires at 6 AM the person's time — never ours.
to buildP3 — The offer
When a time-bound delivery is approved, the person gets the offer card:
"Want me to send this to you day by day?" — channel (text, email, or
both), start date (for flexible weeks), 6 AM local implied. Stored as a
subscription row (goal, deal, receipt, channel, start_date, timezone-at-subscribe).
The agent contract requires making the offer on every time-bound delivery.
to buildP4 — The dispatcher
A scheduled job (rides the existing cron) that each hour finds subscriptions whose
local time just passed 6 AM and, for the day's ordinal: (a) materializes the
day card into the feed, and (b) sends the link-out — email
("Your itinerary for the day is in the Book of Houses") and/or the SMS equivalent.
SMS event joins the want-flow allowlist. Idempotent per (subscription, day).
to buildP5 — The day card in the feed
The day's content — title, plain words, the embedded video — plus three doors:
Did it (checks the day off), a little note (kept on the
card), and Share — sharing turns the day into a
discussion in the person's house. The card enters the feed on its day
and sinks like any seen card once handled.
wired inP6 — The practice money
On practice targets the money steps run honestly but pretend: the step-6 card
states what a real run would have paid and says plainly that nothing moves. The
real rails (person Stripe connect at step 4, the tip sheet, marketplace release)
each have their own build state and are not this program's concern.
Amendments — Steven's rulings through 2026-08-21
- The feed card always lands. The person's opt-in governs the
link-outs (email / text) only; the feed lane is not optional. Mid-run, the
target card pauses/resumes or stops the whole schedule and toggles email/text
notifications. Feed cards keep arriving while the schedule is active; pause
freezes unopened cards and stop closes the unopened remainder.
- Channel pick happens at approval of the whole package —
approve the full list, then choose email and/or text. Approval of the package
is the milestone: money releases there, on the normal lapse clock.
- The successful target card keeps the schedule visible:
Success is separate from Active, Paused, or Stopped. After the last day lands,
the same row becomes Completed + Schedule again. Scheduling again clones the
approved package into a new run; it never rewrites the completed run or its
history. Feed delivery stays on, while prior email/text choices carry forward.
- The drip window is never billed against the agent. Bench
delivery time is measured to package-filed-and-approved; a missed send is a
platform fault, lapse-law spirit: never the agent's.
- Day cards are shareable (already P5's Share door): the
person can share a day into their house feed. The shared card credits the
agent by name and links the Passport — no stars, reviews or followers, per
passport law. Snapshot semantics: later deal changes never mutate the shared post.
- The prod dispatcher cron is a go-live blocker. No sweep
runs on prod today; a drip whose timer does not run silently delivers nothing.
- Machinery detail (tables, ledger events, walker, three-surface work):
timed-delivery-plan. Where the
two pages otherwise differ, this page governs.
Sequencing
- P0 pills (done in the first pass).
- P1 day blocks — the data shape everything else reads.
- P2 timezone — small, unblock the clock.
- P3 the offer card + subscription row.
- P4 dispatcher (feed injection + link-outs).
- P5 the day card's three doors (Did it / note / Share-to-house).
Laws this program leans on
- One card, one action — the day card carries exactly its own doors.
- The step overview / notes law — sophomore-plain instructions everywhere.
- The video block — YouTube ids only, embedded on the card.
- The SMS allowlist — person-action events only; the daily link-out joins it
explicitly as an opted-in send.
- The feed's seen/sink rhythm — day cards behave like native feed citizens.
Written by the foreman from Steven's rulings during the Oregon-hikes
practice process. Amend here first; the build follows this page.