Context harvesting
gathers configured messages, meetings, documents and engineering activity, tracking new, changed and unconsumed evidence so interrupted collection can resume without presenting partial coverage as complete.
AI engineering platform at Bob.Pro
Dispatch
Give AI work project context.
Keep people in control.
An AI engineering platform that gives agents source-backed project context, coordinates their work, and keeps people in control.
My role
sole architect and developer of Dispatch at Bob.Pro, from system design through implementation. No other human contributors to Dispatch.
A clear division of responsibility
Dispatch coordinates engineering jobs and context updates. Workers prepare project knowledge and execute the work. Shared memory and job history make both inspectable, with credentials managed separately.
People stay in control
Review a job. Request a stop or recovery.
Dispatch
Coordinate engineering jobs and context updates. Keep execution visible.
Background workers
Use project context. Run assigned jobs and report what happened.
Project memory
Decisions, open work and source references
Shared history
Job activity and resource records
Managed credentials
Access kept separate from job execution
A stop request is not a stopped job. Worker state confirms the outcome.
The problem
AI engineering depends on decisions, requirements and recent changes scattered across conversations and documents. Teams need agents to start with relevant project knowledge while keeping their work visible and recoverable.
The approach
Connected two layers: moc-skills workflows prepare evidence, guide synthesis into shared project memory, and retrieve relevant context; Dispatch runs the context-update jobs, supplies that memory to planning and implementation, and coordinates workers, history, credentials and operator controls.
What it enables
Supports more informed planning and handoffs with reusable project knowledge and traceable sources, while operators can inspect execution, request intervention and see where source coverage is incomplete.
Context that carries forward.
In moc-skills, context is an executable workflow—not just a set of prompts. Dispatch runs the collection and update jobs; the toolkit prepares evidence, guides synthesis and provides retrieval. A shared repository preserves source-linked, versioned project memory between sessions.
Harvest selected evidence
Bring together configured messages, meetings, documents and engineering activity. Track new, changed and unconsumed evidence so interrupted collection can resume, with incomplete source coverage visible.
Curate project memory
Organize decisions, status, people and open work into versioned records with source references. Validate updates before publication so project knowledge carries forward between sessions.
Carry context into work
Give planning and implementation jobs project-scoped briefs and targeted source-linked lookups, rather than the entire history. Record the mounted memory revision when available.
Missing sources and incomplete updates stay visible. Automatic context refresh is separate from human authorization to implement or deploy work. Source references support review; they do not guarantee that every synthesized fact is correct.
The work,
and its boundaries.
Project memory
organizes status, decisions, people and open work into source-linked, versioned project records that carry knowledge between agent sessions. Updates are validated before publication.
Task-focused context
supplies planning and implementation jobs with project-scoped briefs and targeted source lookups, recording the mounted memory revision when available rather than passing the entire history into every prompt.
Job coordination
organizes pending and active work, assigns jobs to available workers, and supports recovery when a worker stops responding.
Operational visibility
brings execution history and resource records into project-scoped views so operators can understand what ran and what needs attention.
Human control
provides stop and recovery requests tied to the execution being reviewed, helping prevent an outdated screen from controlling newer work.
Architecture
separates evidence collection, synthesis and memory publication from job coordination and worker execution, with centrally managed credentials. Dispatch orchestrates the work; moc-skills provides the context workflows and retrieval tools.
Context boundaries
reports partial or unavailable sources and keeps automatic memory updates separate from human authorization to implement or deploy work. Source references support review, not a guarantee that every synthesized fact is correct.
Design boundary
distinguishes a requested intervention from a completed action, keeping the interface honest about what the worker has actually done.
Technology
- TypeScript
- JavaScript
- PostgreSQL
- SQL
- Git
- HTTP APIs
Let’s make your next project workable.
Talk with me about the product, the engineering and the decisions that need to stay with people.