Preventing Duplicate Delivery Across Automation Threads
How a destination-and-content idempotency key, unknown-result handling, and repeated sibling-task checks can stop resumed automation from repeating an external side effect.
TAGTags
automation
9 articles
Making an Unattended Windows Display Blackout Remote-Aware
A remote-aware display guardian uses connection events, local input, cancellable deadlines, and fail-closed evidence to keep an unattended Windows workstation dark without interrupting active remote work.
Handing Off Automation Ownership Without Losing Recovery Evidence
A safe automation handoff separates live authority, recovery evidence, retired execution paths, and disposable local state before anything is removed.
Safely Revising Completed Jobs with a Fail-Closed State Machine
How an explicit revision lifecycle can reopen a completed external-delivery job without duplicating remote objects or trusting stale review evidence.
Pin Policy Snapshots Before Long-Running Automation Executes
How versioned policy snapshots keep active jobs and retries reproducible while new rules roll out prospectively.
Preventing CI Notification Storms on High-Churn State Branches
How to keep required repository checks meaningful when an automation branch frequently commits heartbeats, checkpoints, and other run state.
Turning a Long-Term Learning Roadmap into an Evidence-Driven Feedback Loop
How idempotent daily plans, evidence-gated completion, spaced review, and bounded load changes turn a long roadmap into an executable learning system.
Assigning Incrementing Job IDs Without Duplicating Paid Work on Retry
How a stable allocation key and a process lock let a recurring paid pipeline create several jobs per period without duplicating work when a scheduled run retries.
Launching Codex Without TUN Using the Current Windows Proxy
Making a Codex desktop launcher resilient to local proxy port changes while keeping failure handling safe.