[{"data":1,"prerenderedAt":153},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fv2\u002Ffleet\u002Fmanagement\u002Fjobs":3},{"id":4,"title":5,"body":6,"description":16,"extension":146,"meta":147,"navigation":148,"path":149,"seo":150,"stem":151,"__hash__":152},"docs\u002Fdocs\u002Fv2\u002Ffleet\u002Fmanagement\u002Fjobs.md","Jobs",{"type":7,"value":8,"toc":139},"minimark",[9,13,17,22,25,30,41,45,53,56,60,68,72,76,79,83,92,96,102,105,109,112,116,123,126],[10,11,5],"h1",{"id":12},"jobs",[14,15,16],"p",{},"A job is a concern you want worked: a bug, a migration, a standing review. It holds a\nbrief, and a log of everything that has happened on it.",[18,19],"terminal-image",{"alt":20,"src":21},"The Workspace view showing jobs grouped by the repo they belong to","\u002Ffleet\u002Fworkspace.png",[14,23,24],{},"Grouped by repo, because that is where contention is. Two agents editing one working tree\nconflict; two agents in different repos do not.",[26,27,29],"h2",{"id":28},"a-job-is-a-directory","A job is a directory",[31,32,37],"pre",{"className":33,"code":35,"language":36},[34],"language-text","jobs\u002F\n└── flaky-auth-test\u002F\n    ├── job.md              ← the brief: what this work is, now\n    └── log\u002F\n        ├── 001.dispatch.md ← what you asked for\n        ├── 002.report.md   ← what the agent found\n        └── 003.proposal.md ← what it suggests doing\n","text",[38,39,35],"code",{"__ignoreMap":40},"",[18,42],{"alt":43,"src":44},"A job opened showing its brief above the log of dispatches, reports and proposals","\u002Ffleet\u002Fjob-detail.png",[14,46,47,48,52],{},"No database, no schema, no client. ",[49,50,51],"strong",{},"An agent participates by writing a file"," — so an\nagent that knows nothing about Fleet can take part with the filesystem tools it already\nhas.",[14,54,55],{},"Jobs live on the branch they belong to. Work on a feature branch travels with it and\narrives with the pull request.",[26,57,59],{"id":58},"the-brief-changes-the-log-does-not","The brief changes; the log does not",[14,61,62,63,67],{},"The brief says what the work is ",[64,65,66],"em",{},"now"," — edit it in place as understanding improves. The\nlog is append-only: an entry records what was true when it landed.",[18,69],{"alt":70,"src":71},"The append-only job log with a report and a proposal from an agent","\u002Ffleet\u002Fjob-log.png",[26,73,75],{"id":74},"dispatching","Dispatching",[14,77,78],{},"Pair an asset with a job: this agent, running this prompt, against this work.",[80,81],"terminal-video",{"src":82},"\u002Ffleet\u002Fdispatch.mp4",[14,84,85,86,91],{},"While it runs, the assignment appears under the job it is working, and the\n",[87,88,90],"a",{"href":89},"\u002Fdocs\u002Fv2\u002Ffleet\u002Fdebugging\u002Fconsole","Console"," points at it like any other instance.",[18,93],{"alt":94,"src":95},"A live assignment nested under the job it is working","\u002Ffleet\u002Flive-assignment.png",[14,97,98,101],{},[49,99,100],{},"The session is the durable record."," Who ran what, what changed, how long it took —\nall of it is in the trace. Nothing is copied into the job, because a copy can disagree\nwith the thing it copied. A job entry naming its session is a claim; the session is the\nevidence.",[14,103,104],{},"When a run exits, how it ended is kept rather than cleared — a run that produced nothing\nstill reports why.",[26,106,108],{"id":107},"the-gradient","The gradient",[14,110,111],{},"A brief can carry keys naming what to run against it: which agent, which prompt. All\noptional.",[18,113],{"alt":114,"src":115},"Three jobs side by side: a plain note, one naming an agent, one fully specified and dispatchable","\u002Ffleet\u002Fjob-gradient.png",[14,117,118,119,122],{},"A job with none is a note you wrote yourself. Add an agent and a prompt and it becomes one\nclick. ",[49,120,121],{},"Filling keys in is how work moves toward automation without changing what the\nfile is"," — no promotion step, no conversion, no second artifact.",[124,125],"hr",{},[14,127,128,129,133,134,138],{},"Back to ",[87,130,132],{"href":131},"\u002Fdocs\u002Fv2\u002Ffleet\u002Fmanagement","Managing Agents",", or on to\n",[87,135,137],{"href":136},"\u002Fdocs\u002Fv2\u002Ffleet\u002Fdebugging","Debugging",".",{"title":40,"searchDepth":140,"depth":140,"links":141},2,[142,143,144,145],{"id":28,"depth":140,"text":29},{"id":58,"depth":140,"text":59},{"id":74,"depth":140,"text":75},{"id":107,"depth":140,"text":108},"md",{},true,"\u002Fdocs\u002Fv2\u002Ffleet\u002Fmanagement\u002Fjobs",{"title":5,"description":16},"docs\u002Fv2\u002Ffleet\u002Fmanagement\u002Fjobs","sIGUGLXol8xIittChgNk1UBrWGuDteIRhJ1aOofMrXo",1786104360891]