Request a corrected program for someone

Keep the consequential details apart

• Do not choose between conflicting spellings or service days; put both in correction and say which is unresolved.
• When a later instruction changes a spelling ("it should read Marionne, not Marion"), send correction with the final replacement. A correction to a different word ("the word neighbour should be spelled neighbor") is an additional replacement line, never a rival to the first one; name each line's panel. If you cannot tell which spelling is final, send the instruction verbatim in wording_question.
• Keep arrival, receiving hours and service time in their own fields. A requested arrival is not a confirmed delivery.
• Record pending proof approval in approval. A request is not proof approval.
• Say whether edge-to-edge must be kept or a border is acceptable. Put the customer's own words in appearance_note; if they disagree with a choice made elsewhere, say the question is open. Stillleaf will not add a border without permission.
• Split a combined sentence yourself: quantity, destination and arrival each go in their own field. "Receiving desk" in an address is part of the destination; receiving holds only receiving hours.
• correction holds only what changes on the program. Receiving or drop-off facts go in receiving; anything else for Stillleaf to read goes in note_for_stillleaf, which is never typeset.
• A filename does not transfer a file. Send a secure link, or say the file follows by reply email.

Dates and incomplete requirements

Dates: send arrival_date as YYYY-MM-DD. The handler refuses a value only for its type, a maxLength or a minimum (quantity must be at least 1). Words in arrival_date are kept as sent, also listed in missing_specifications, and the request is not treated as dated. Missing fields (correction, quantity, destination, arrival) are returned in missing_specifications and stay open for the email conversation; they do not block a first request. Without contact.email there is no reply channel until an address is supplied.

Return and continue

Keep the receipt id and token private. Read the recorded requirement with request_status; a reference alone grants nothing. For changes, send a new requirement with continuation {id, token} carrying the complete current specifications; the earlier record stays on file. A later record supersedes an earlier one only as Stillleaf confirms in the conversation. If an authorized offer is linked later, inspect its exact terms before any acceptance; an agent session is not purchase authority.

People open the same record at /request/ with their private receipt link.

Example

Illustrative synthetic requirement: Morgan-program-v2.pdf, two landscape letter pages holding the outside and inside of a half-fold. Inside panel: replace "Marian" with "Marion"; leave all other text and photos unchanged. 150 finished programs to a synthetic receiving desk at 123 Example Street, Philadelphia PA 19103, arriving November 12, 2026, 9:00 AM America/New_York (arrival_date 2026-11-12), for an 11:00 AM service. The arranger reviews the corrected proof before printing. File to follow by reply email. The full envelope is published in llms.txt and openapi.json.

What happens next

When the file arrives, by secure link or by reply to our first email, Stillleaf reviews it with the correction, resolves the open details, and establishes printing and delivery feasibility. We email a proposed completion plan and pricing for your review. Nothing is ordered or committed until terms are agreed; timing and availability are confirmed before acceptance.