Recorded case

Budgets and outages belong in the state machine

A reliable operator view distinguishes working, waiting, failed, blocked and accounting uncertainty.

Reviewed 15 October 2026 · scope: implemented

Recorded method and findings

A reservation precedes a paid request; the receipt closes or reconciles it afterward. Estimated provider cost and a reconciled billing statement are different evidence. A timeout can leave the charge uncertain, so repeating immediately may spend twice without a trustworthy total.

Recorded method and findings

A provider incident should be recorded separately from a worker-quality failure. Changing provider can change the model, latency, price and access conditions. Credits belong in accounting as credits; they do not silently remove spending limits.

Practical checklist

Show spent, reserved and uncertain amounts separately. Bound retries and preserve the provider error class. Treat a missing success trace as missing evidence, not proof of inactivity or an outage.

Sources & scope

DSHREM scheduled execution and accounting report 2026-10-14
Provider outage review from operator notice and local logs 2026-10-15

Keep exploring

AI orchestration: from a prompt to an accepted resultA practical design for delegation, evidence and recovery.Shared memory without shared mistakesKeep facts, hypotheses and permissions distinct across agent sessions.Engineering that can show its workTVIJO connects operators, bounded agent work and knowledge that can be checked and reused.AGENTORCH: the orchestrator has a concrete jobAGENTORCH names the orchestration role: plan, assign, observe, reconcile and accept.The task packet is the interfaceA good task describes a verifiable outcome rather than an invitation to improvise without limits.AGENTJUDGE: acceptance follows evidenceA reviewer checks the task, the artifact version and each acceptance criterion.Measure cost per accepted resultSmall task benchmarks illustrate why task class and acceptance matter more than a cheap model label.Keep VECTORBASE, evaluate retrievalUse a private source-linked index to find evidence; do not treat search results as authority.SPIDER: evidence collection and useful progressThe first implementation reads an explicit project-evidence list and produces a dated operator digest without model calls.DSHREMBOT and tmux: one operator viewAuthenticated project commands, budget visibility and explicit schedule controls connect the operator to existing execution lanes.The AI worker–Hugging Face incident: learn from controlsThe incident reports support specific engineering lessons, not a controlled ranking of our system.What the supplied AI worker screenshot actually provesThe screenshot records a safeguard-triggered switch in one session; it does not explain the exact trigger. The observation is the supplied screenshot dated 15 October 2026.Training our own model: a gated research directionA proprietary model is an option to test after retrieval, prompts and routing have measurable limits.A bilingual knowledge product with visible limitsPublish useful explanations first, then expand languages when the evidence and workflow are ready.Free learning, custom projects and future challengesTurn evidence-backed engineering into clear offers and a useful developer community.Trust the sender, not a public checksumBind the complete message to an explicitly trusted authority.