Record expiry.
A deployed deterministic automation that expires stale hold records in a live booking system. It runs unsupervised on a schedule, with no model and no decision in it—because the problem needs neither.
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
Keep booking state truthful by expiring holds whose last active date has passed, without requiring an operator to review each one.
Runtime
01
Wake
Runs on a schedule against the live booking store.
02
Select
Reads holds not already marked expired.
03
Compare
Derives the latest active end date and tests it against today.
04
Expire
Marks the hold and its date rows expired when that date has passed.
05
Count
Logs each expiry and returns the total actioned.
Anatomy
Context
- Hold records
- Associated date rows
- Current date
Capabilities
- Derive the latest active end date
- Determine expiry against today
- Mark a hold and its dates expired
Activation
- Schedule
Authority
What can it change?
- Autonomy
- Autonomous
- Horizon
- Scheduled
Read
- Hold records
- Date rows
Write
- Expiry flag on a hold
- Expiry flag on its date rows
Conditional
- Expire only when the latest active date is strictly in the past
Prohibited
- Delete any record
- Touch a hold that is already expired
- Touch a hold with no resolvable date
Escalate
- None — it runs unsupervised inside this boundary
Composition and verification
Made from explicit parts.
Composition
- Scheduled command
- Booking datastore
- Deterministic date logic
- No model in the decision path
Verification
- Returns a count of records actioned
- Logs every individual expiry
- Selection filter makes a repeat run a no-op
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