Runsheet

Mesh · the job system

Where the factory's work runs.

Mesh is a job system for services. runsheet is one of them: every step it takes — planning a goal, building an item, validating it, reviewing it — is a job it queues in Mesh. Mesh is its own product, with its own home at projectmesh.io.

How it works

Services queue jobs, nodes run them.

Mesh holds the queue and the nodes. What a job is for, and what it does, belongs to the service that queued it.

Services register their kinds

A service tells Mesh the kinds of job it runs — what each needs, the tools it may use, the network it may reach and the shape of its result.

Services queue jobs

A service queues a job of one of its kinds. Mesh orders the queue, places each job on a node with room for it, and reports how it ended back to the service.

Jobs reach your service's MCP servers

A running job is connected to the MCP servers of the service that queued it, so it reads its brief and hands in its result through the service's own tools.

A Latchkey session token per job

Each job gets its own short-lived Latchkey session token: its identity for every call it makes. No job holds a long-lived credential.

Nodes

Yours or ours.

A node is a machine that takes jobs. Run nodes on your own hardware, or use ours; a job runs the same either way, in a rootless container that reaches only the network it is granted.

More on Mesh.

What Mesh is on its own, how nodes work and how to run one: projectmesh.io.