Consignment notices.
A deployed automation that sends consignment deadline notices at three fixed points around the end date. It sends the matching notice or nothing at all — there is no judgment in it, and none is needed.
Deployed automation — this configuration is running in production. Client identities are withheld.
Classified as automation: it executes a predefined path, interpreting nothing and selecting between nothing. It is a deployed component of a working system, built this way because the problem required no decision.
No model anywhere in this entry. It is deterministic end to end — the behaviour comes from rules, arithmetic and explicit boundaries.
Objective
Tell depositors where their consignment period stands without anyone tracking dates by hand, on a schedule tight enough that no one is surprised by an expiry.
Runtime
01
Wake
Runs daily against the depositor records, in a fixed timezone.
02
Resolve
Compares each deadline to today and maps it to one of three stages, or to none.
03
Match
Selects the notice for that stage: ten days out, on the day, or fifteen days past.
04
Send
Emails the depositor, skipping any record without a usable address.
05
Count
Reports what was sent per stage, what was skipped, and what errored.
Anatomy
Context
- Depositor records and contact addresses
- Each consignment's deadline
- Today's date in a fixed timezone
Capabilities
- Map a deadline to a notice stage
- Select the matching notice
- Send it to the depositor
Activation
- Daily schedule
Authority
What can it change?
- Autonomy
- Autonomous
- Horizon
- Scheduled
Read
- Depositor records
- Consignment deadlines
Write
- Outbound notices to depositors
Conditional
- Send only when the deadline falls exactly on a defined stage
Prohibited
- Change a deadline
- Change a price or a consignment's status
- Send to a record without a valid address
- Send anything on a date between stages
Escalate
- None — it runs unsupervised inside this boundary
Composition and verification
Made from explicit parts.
Composition
- Scheduled job
- Depositor and inventory records
- Timezone-aware date arithmetic
- Transactional email
- A dry-run mode that sends nothing
Verification
- Dates resolved in an explicit timezone, not the host's
- A deadline off-stage produces no notice at all
- Dry-run mode logs every send without performing one
- Per-stage counts of sent, skipped and errored
No evidence is published for this entry. The items above are our own account of its source, read before publishing — not something you can check without taking our word for it.
Next step
What you can do with this.
This configuration runs in production, client identity withheld. To discuss the same for your operation, start with the problem rather than the system: a first call is thirty minutes and costs nothing.
Related entries