TVIJO / Wiki
AGENTSORCH / AGENTSJUDJEExplore spatial systems, articles and operator learning →

Practical guide

Shared memory without shared mistakes

Keep facts, hypotheses and permissions distinct across agent sessions.

Reviewed 15 October 2026 · scope: Guide

A handoff is a contract

Save the goal, verified findings, source references, file hashes, remaining limits and next step. The successor checks the current environment. A summary transfers context, not authority.

Preserve negative knowledge

An unsuccessful experiment is useful when its conditions and evidence remain searchable. A later worker should explain changed conditions before repeating it. Several agents quoting one source still provide one source.

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.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.Trust the sender, not a public checksumBind the complete message to an explicitly trusted authority.

Your selection

Selections are stored in this browser on this domain. No account sync is implied.

Send a scoped enquiry to our engineering team. Scope, availability and price are confirmed before any charge or subscription starts.