llm-agent-vs-deterministic-script-decision-hierarchy
Established a formal protocol: cron script > hook > human-directed session > autonomous LLM agent. The Archivist nightly synthesis agent was replaced by a 2-second cron script (vault-hot-cache.sh) at zero API cost — the real-time cascade engine already handled 95% of compounding value. Never deploy an LLM agent for a job a deterministic script can do; highest-grade outcomes at lowest cost.
Related
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- clawteam-openclaw-multi-agent-swarm-evaluation
- 2026-04-04-oracle-001-self-architecture-analysis
- full-system-activation-loop-first-approach
claude-code-to-nova-enterprise-capability-expansion-20260323(archived)- vault-hygiene-four-lane-architecture
- hook-script-executable-permission-silent-failure
- cron-script-log-redirect-missing-causes-silent-failures
- llm-agent-vs-cron-decision-hierarchy
- real-time-cascade-supersedes-nightly-synthesis-agent
- cost-efficiency-decision-hierarchy-for-automation
- caveman-compression-conflicts-with-zero-ambiguity-law