Timed Delivery (Drip Schedule)

Two additive tables. Idempotent prod-replay SQL ships in the commit AND in app/scripts/sql/, per standing law. No changes to existing tables beyond what is listed.

delivery_schedules

• id, deal_id / step_id (whichever step filed it), goal_id, maker_id
• status: proposed → approved → delivering → completed (plus rejected)
• piece_count, cadence (v1: daily only), starts_on (date), approved_at
• email_enabled, sms_enabled (booleans; the feed lane has no column — it is always on by law D2/D3)

delivery_pieces

• id, schedule_id, seq (1..N), title
• document — a sectioned document in the r184 block format (same shape file_document_outcome takes; walls of plain text are refused)
• scheduled_for (date), status: sealed → released (or missed, system-fault marker), released_at
• ledger_event_id of its release event once released

Sealed means sealed: pieces are not readable by the person before their day — not in released_materials, not via any read endpoint. released_materials / released_materials_count keep the always-present-including-zero law and grow by one per release.

The closed event-type list grows by four (canonical RFC8785 envelope + event_hash like the other 41; remember the two-sync rule: rerun extract_rules.py / citations and bump the census literal or 5 tests fail):

A missed day is recorded on the piece row (missed) and released late by the next sweep pass; it is logged as a system fault, never attributed to the agent (D6).

target_path_sweep.py (hourly, pudding crontab, env --chdir pattern) gains a release pass:

for each schedule in status delivering:
    for each piece where scheduled_for <= today(person-local) and status = sealed:
        release piece  -> write delivery.released  -> fan out (feed / email / sms)
    if all pieces released: schedule -> completed, write schedule.completed

Release is idempotent (a released piece is skipped), so a double-run or a late catch-up run is safe.

BLOCKER (D7): install the sweep cron on PROD. It has been on the open list since go-live. This feature does not ship until the prod walker runs and is verified (a piece scheduled for today actually releases within the hour on prod).

Everything hangs off delivery.released. One seam, so the channels can never disagree about what was delivered.

The successful target card shows the schedule separately as Active, Paused, or Stopped, with its serving-through date or progress. Pause/resume and stop act on the whole schedule; email and text controls continue to flip email_enabled / sms_enabled independently. The feed lane shows no independent notification toggle.

Per D5: a Share action on the delivery card, person-only. Sharing creates a house-feed post in the person's house wrapping a snapshot of the piece (the person owns the delivered work; sharing is their call, so consent is built in).

• The shared card credits the agent by name/A-number and links the Agent Passport. No stars, reviews or followers anywhere on it, per passport law.
• It is a snapshot reference: later changes to the deal do not mutate the shared post.
• Share is available on released pieces only — never sealed ones.
• This is the first person-initiated bridge from the private want market into house social space, and it is honest advertising for the bench: a real person choosing to show their house what an agent delivered.

A capability that is not on agent-api.openapi.json AND agent-skill.md AND the MCP tool list does not exist. All three land in the same pass:

• New: file_delivery_schedule — files the full piece list + schedule on a step (analogous to file_document_outcome, but N dated documents). Contract path + skill section + MCP tool together.
• Rejection gates (REJ-series): piece count must equal the list length; dates strictly increasing, daily cadence, start no earlier than tomorrow; every piece a valid r184 sectioned document; length caps per piece same as outcome caps (r178 spirit); no links outside the agent's own materials (r179 spirit).
• Status rides calls the agent already makes: schedule state (approved? delivering? day K of N) appears on current_step and /me/attention. No new polling loop.
• r118 spirit holds: filing a schedule over an unanswered person message is defective.

• Approval clock: the person's review of the full list runs on the normal lapse clock — reminders day 3/7/12, stale at 14 deems approval. Deemed approval starts the drip with default channels (feed only; email/text stay off until the person turns them on).
• Money: releases at approval per D1. Fee unchanged: 15% added on top, marketplace rules as they stand. Nothing about the drip touches checkout beyond the normal milestone release.
• Bench/leaderboard: the deal counts delivered at approval (D6). The field view may show the target as delivering (still going) until schedule.completed, then delivered — the agent's score never waits on the calendar.
• Practice targets: drips on practice deals follow r99 — no funds move. (r99 is still half built; that fix is upstream of this feature touching money at all.)