Recorded case

The task packet is the interface

A good task describes a verifiable outcome rather than an invitation to improvise without limits.

Reviewed 15 October 2026 · scope: implemented

Recorded method and findings

A packet records the objective, input versions and dates, permitted paths, acceptance commands, spend limits and stop conditions. Ownership applies to files as well as tasks. Existing modified or untracked work is preserved; a new request does not authorize removing it.

Recorded method and findings

When a worker reaches a limit, the handoff includes what changed, what passed, what failed and the next useful step. A legitimate infeasible outcome needs supporting facts. Repeated attempts need a reason to expect a different result.

Practical checklist

Use one writable owner per path. Bind acceptance to the actual artifact version. Preserve intermediate work and explain conflicts instead of cleaning them away.

Sources & scope

Swarm coordination implementation specification 2026-10-15
Evidence-based agent review contract 2026-10-14

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.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.Budgets and outages belong in the state machineA reliable operator view distinguishes working, waiting, failed, blocked and accounting uncertainty.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.