"The scheduler owns when; the engine owns a safe, repeatable operation."
How the well grows
A morning passage is a useful ritual. A hidden scheduler inside the writing engine is not. Scheduling already has a family owner, and duplicating it would make two clocks race to create the same day.
Attach it with a narrow contract
Expose a narrow operation: for the caller-supplied entry_date, create a draw only if that date is empty. An external cwkPippa scheduler owns when to call and serializes delivery.
When extension steals sovereignty
Engine-local time guesses the user's day and hides scheduling state. The endpoint's only-if-empty check makes sequential retries safe, while the scheduler's single lease prevents concurrent delivery. The engine does not invent a ritual key or another clock.
Retest the first promise
Even after “The Morning Draw Lives Outside” arrives, the original returns first, the author keeps the pen, and late work asks permission. Trace whether sharing, scheduling, search, or audio invents copied originals, hidden clocks, or broad payloads for convenience. An extension that bypasses old invariants has changed the product rather than grown it.
Run the whole path
Trace a scheduler retry after a timeout and show that the date still holds at most one passage. Add duplicate delivery, source editing, deletion, stale artifacts, and permission denial. Prove that database rows, outbound payloads, and sibling references tell the same story instead of trusting one successful screen.
What it means to close the well
Closing does not mean stopping features. It means one practice is complete from original draw through paper, recovery, rediscovery, and deliberate sharing. When technology appears only to explain itself and otherwise recedes behind the ink, the well has grown useful hands.
The extension's actual contract
The caller supplies entry_date and only_if_empty. cwkPippa owns the singleton schedule; Inkwell checks the date, returns a skipped response when it already has an entry, and otherwise creates from stored defaults.
This is retry safety across the owned serial lane, not a database uniqueness claim the current schema does not make.