Practical guide

Trust the sender, not a public checksum

Bind the complete message to an explicitly trusted authority.

Reviewed 15 October 2026 · scope: Implemented library

Integrity and identity

A public hash can reveal changed bytes but anyone can recompute it. A session identifier is a label, not a private signing key. Authentication must be anchored outside the received message.

Complete and bounded envelopes

The implemented library supports a full-envelope checksum and optional trusted HMAC authority scoped to sender, session, task, recipient and message kind. Expiry and atomic one-use receipts protect the strict receiving path. Legacy digests remain readable as integrity-only records.

What has been tested

Isolated tests exercise changed routing, changed content, wrong keys, expiry and concurrent replay. This establishes the library contract; it does not claim every bot and worker has migrated or that a process with access to the trusted key is isolated.

Engineering guidance, reviewed 15 October 2026. Proposed scopes require agreed acceptance.

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.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.