2026-03-15

Signal

Choosing hourly cron over streaming for the oil model’s auto-refresh revealed a design principle that transfers broadly: reliability matters more than latency for systems where the cost of a missed update is low and the cost of a failed update is high.

Evidence

• Project: projects/oil/_index : 11 sessions: Quant Framework Plan, Dashboard Hourly Auto-Refresh, Geopolitical Auto-Apply System
• Decision: Hourly cron chosen over streaming for model refresh : reliability > latency for this use case
• Architecture: Externalized data pipeline + hourly cron for automated model updates; automatic application of geopolitical events to model parameters
• Project: projects/jobs-apply/_index : AutoSearch integration plan merged into Claude file

So What (Why Should You Care)

The cron vs. streaming decision for the projects/oil/_index model applies to any system that processes real-time data feeds but doesn’t require real-time output. Oil futures prices update continuously, but the model’s downstream consumers : people making positioning decisions : operate on minute-to-hour timescales. Streaming the data would add significant operational complexity: persistent connection management, reconnection logic after failures, backpressure handling when the downstream model can’t keep up. All of that complexity would be spent to deliver updates that arrive faster than they can be acted upon.

The hourly cron is reliable, auditable, and operationally simple. If a cron run fails, you know exactly when it failed and why. If a streaming connection drops, you may not notice until you look at the data and realize it’s been stale for three hours. For systems where the cost of a missed update is low and the cost of an undetected failure is high, cron wins over streaming every time.

The Geopolitical Auto-Apply System for the oil model is worth noting for a different reason: it closes a manual step that was creating inconsistency. When GL-134 was added manually on 2026-03-12, it required remembering to update the model. An auto-apply system that reads geopolitical events and updates model parameters automatically eliminates that manual dependency.

What’s Next

• Validate geopolitical auto-apply system with real events

Log

• projects/oil/_index: 11 sessions : largest oil model day so far
• Quant Framework Plan: full implementation for CL Futures Hormuz Model
• Dashboard Hourly Auto-Refresh: externalized data pipeline, hourly cron for automated model updates
• Geopolitical Auto-Apply System: automatic application of geopolitical events to model parameters
• Multiple ultrathink planning sessions with quant persona
• Key decision: hourly cron over streaming : reliability > latency for this use case
• projects/jobs-apply/_index: merged AutoSearch integration plan into Claude file