Work Orders and Work Reports for AI agents. A typed SDK, validator and lifecycle engine for handing work from one agent to another, with checkable results. The MCP server is a separate package, agent-work-layer-mcp.
Work Orders and Work Reports for AI agents: a typed SDK, validator and lifecycle desk. The MCP server is in agent-work-layer-mcp.
2026-11-12
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Work Order (manager → worker): the goal, how "done" is judged, budget, deadline, allowed tools.
Work Report (worker → manager): the result, evidence for each criterion, actual cost, tools used.
Agent Cards say who an agent is. A2A carries messages between agents. MCP connects agents to tools. AWL describes the job itself, so any manager can hand work to any worker and check what came back. The format is defined in SPEC.md.
How it works
A manager issues a Work Order: goal, criteria, budget, deadline, allowed tools.
A worker accepts it and does the job with its tools.
The worker returns a Work Report with evidence for every criterion and what it spent.
Node.js 20.11 or later. ESM only. Types included. The Python package needs Python 3.9 or later.
Quick start
import { WorkDesk } from "agent-work-layer";
const desk = new WorkDesk(); // in-memory; use FileStore, SqliteStore or your own DeskStore to persist
// Manager issues a job
const { order } = await desk.create(
{
to: "agent:researcher",
goal: "Summarize the main risk factors in the latest annual report",
criteria: [
{ id: "c1", text: "Lists three risk factors, each quoted from the filing" },
{ id: "c2", text: "States total debt and its fiscal year" },
],
budget: { usd: 2, tool_calls: 20 },
deadline: new Date(Date.now() + 3_600_000).toISOString(),
tools: ["filings/*"],
},
"agent:manager",
);
// Worker accepts, does the work, reports with evidence
await desk.accept(order.id, "agent:researcher");
const { record } = await desk.submitReport(
order.id,
{
status: "done",
result: { summary: "Refinancing, customer concentration and FX risk. Debt 1.2B USD (FY2025)." },
evidence: [
{ criterion: "c1", type: "tool_call", ref: "filings/get_section#3" },
{ criterion: "c2", type: "citation", ref: "filings/get_section#5" },
],
cost: { usd: 0.84, tool_calls: 7 },
tools_used: ["filings/search", "filings/get_section"],
},
"agent:researcher",
);
// Manager approves, or sends it back with a reason
await desk.review(order.id, "agent:manager", "approve");
For a runnable version, clone the repo, run npm install, then run node examples/two-agents.ts (Node 22.18+). examples/two-agents.ts walks one job through a rejected report, a rework request and approval, printing each event as it happens.
The desk enforces the spec as you go:
Who may do what: only the worker reports, and only the manager approves.
Which state changes are legal.
Evidence for every criterion.
Only allowed tools.
Cost within budget and finishing before the deadline. Going over either expires the order.
Sub-orders can only narrow their parent's authority. Their budgets come out of the parent's, so a whole tree of sub-orders never spends more than the order at its root.
A reissued order can only continue a finished one, so one job never has two live orders.
Optionally, it also signs the worker's authority into a Delegation Pass that gateways and other systems can check without the desk.
Hand off unfinished work
When a worker fails, gets blocked or is cancelled, it can say what the next worker should know. The manager passes that along in the next order:
await desk.submitReport(order.id, {
status: "failed",
error: "Export runs out of memory on files over 2 GB",
handoff: {
decisions: [{ text: "Stream rows instead of buffering", why: "Memory limit" }],
tried: [{ text: "xlsx library", result: "Too slow on large files" }],
next_step: "Add tests for null cells",
},
/* result, evidence, cost, tools_used */
}, "agent:researcher");
const { handoff } = (await desk.get(order.id)).reports.at(-1)!;
await desk.cancel(order.id, "agent:manager", "reissuing"); // a continued order must be finished
await desk.create({ ...nextJob, to: "agent:other-worker", handoff, continues: order.id }, "agent:manager");
await desk.list({ continues: order.id }); // the orders that pick up from this one
context lists what to read; handoff says what was decided and already tried; continues links the new order to the one it replaces, so the chain of orders is the job's full history. Unlike parent_id, it doesn't narrow anything: the new order can have a different worker, budget and tools. See SPEC.md §4.4 and §4.5.
Hold writes until the report is approved
Rejecting a report doesn't unsend an email. For tools whose effects you want to review first, list them in staged:
The worker's MCP gateway then holds back calls to gmail/send: it counts and logs each one and returns a placeholder (pending:gmail/send#4). The worker lists them in its report's effects, which the manager reviews with the rest of the report. Approving lets the gateway run them; rework drops them, and since they never ran, there is nothing to undo. Reads still run normally. A sub-order can't allow a tool its parent stages (C5).
A staged call can use an earlier one's result: pass { "$ref": "github/create_issue#3", "pointer": "/structuredContent/number" } as an argument, and the gateway fills it in when it runs the effects. The manager can also approve only some effects:
Progress notes are progress events: they change no state, but waitForChange and wait_for_update wake on them. A track record counts what happened to the orders a desk holds for one worker. See SPEC.md §6.2 and §6.3.
Every finding carries the rule id from SPEC.md §7. invalid findings reject a document. limit findings (over budget, past deadline) are recorded and expire the order.
Writing a validator in another language? Run it against the JSON test vectors in conformance/: documents with the findings each rule must report.
The JSON Schemas are exported too: workOrderSchema, workReportSchema, or agent-work-layer/schemas/work-order.schema.json.
agent-work-layer/validate has the same checks, types and schemas without the desk. It imports nothing from Node, so it runs in browsers, Deno and Bun. (Cloudflare Workers are not supported: the validator compiles schemas to code at runtime, which Workers block.)
Run as an MCP server
The server lives in its own package, agent-work-layer-mcp, so people who only validate documents don't download the MCP SDK.
For development, over stdio. Each agent session runs its own desk process. Sessions share one folder, and each is locked to the identity it is started with.
# Claude Code: a manager session and a worker session, each added in its own project folder
claude mcp add awl -e AWL_STORE="$HOME/.awl" -e AWL_ACTOR=agent:manager -- npx -y agent-work-layer-mcp
claude mcp add awl -e AWL_STORE="$HOME/.awl" -e AWL_ACTOR=agent:worker -- npx -y agent-work-layer-mcp
For shared use, over HTTP. One desk serves every agent, and each request's credential decides who it acts as, so a worker cannot approve its own work (details):
Tools: create_work_order, list_work_orders, get_work_order, accept_work_order, decline_work_order, start_work_order, report_progress, submit_work_report, answer_question, review_work_report, cancel_work_order, wait_for_update, get_track_record, and renew_work_pass when the desk issues Delegation Passes.
To enforce an order while the worker works, and to hold its staged writes until you approve, connect the worker to its real MCP servers through the gateway: npx -y agent-work-layer-mcp gateway --order <id> --config upstream.json. After approval, --commit runs the approved writes. See the gateway docs.
To embed the server in your own process or transport (npm install agent-work-layer agent-work-layer-mcp):
import { WorkDesk, FileStore } from "agent-work-layer";
import { createDeskServer } from "agent-work-layer-mcp";
const server = createDeskServer({ desk: new WorkDesk({ store: new FileStore("./.awl") }), actor: "agent:manager" });
await server.connect(transport);
CLI
npx agent-work-layer new order > order.json
npx agent-work-layer new report > report.json
npx agent-work-layer validate order.json report.json # exit 1 on invalid, prints rule ids
npx agent-work-layer validate child.json --parent order.json
npx agent-work-layer validate order.json report.json --json
npx agent-work-layer schema order
npx -y agent-work-layer-mcp --store ./.awl --actor agent:worker # the MCP desk on stdio (was "awl desk" before 0.2)
npx -y agent-work-layer-mcp serve --keys keys.json # one shared desk over HTTP; add --pass-key/--issuer to sign passes
npx -y agent-work-layer-mcp gateway --order <id> --config <file> # enforce an order at every tool call; add --pass-keys to use passes
new order starts with one criterion, a USD 1 budget, no allowed tools and a
deadline one hour after creation. new report starts as blocked, with a question
and no evidence of completed work. Both templates validate together as printed.
Replace the placeholder goal, identities, criterion and report contents before
using them; keep the report's order_id equal to the order's id.
Lifecycle
offered ──accept──▶ accepted ──start──▶ working ──report done/failed──▶ submitted ──approve──▶ approved
│ │ ▲ │
decline blocked │ │ answer │ rework (with reason)
▼ ▼ │ ▼
declined blocked working
Any active state ──cancel──▶ cancelled · deadline or budget exceeded ──▶ expired
While working, the worker can post progress notes. They are recorded as events but don't change the state (SPEC.md §6.2).
Action
Who
accept, decline, start, submit report, post progress
the worker (order.to)
approve, rework, cancel
the manager (order.from)
answer a blocked worker
the manager or order.escalate_to
expire
the desk
API
Export
Purpose
WorkDesk
Runs the lifecycle: create, accept, decline, start, progress, submitReport, answer, review, cancel, get, list, subOrders, held, trackRecord, waitForChange, and issuePass when it issues passes
MemoryStore, FileStore, SqliteStore, DeskStore
Storage. Implement DeskStore (4 methods) to use a database
NOT_FOUND, ALREADY_EXISTS, FORBIDDEN, INVALID_TRANSITION, VALIDATION_FAILED (with findings), CONFLICT (a concurrent writer got there first; re-read and retry), BAD_REQUEST.
PassError codes: MALFORMED, UNSUPPORTED, BAD_SIGNATURE, EXPIRED, NOT_YET_VALID, WRONG_ISSUER, WRONG_WORKER, WRONG_ORDER, WRONG_PARENT, WIDER_THAN_PARENT (with findings from C1–C3 and C5).
Custom storage
MemoryStore keeps records in memory, FileStore writes one JSON file per order, and SqliteStore keeps them in a SQLite database using Node's built-in node:sqlite (Node 22.13+, no extra dependency):
import { WorkDesk, SqliteStore } from "agent-work-layer";
const desk = new WorkDesk({ store: new SqliteStore("./awl.db") }); // or ":memory:"
A stdio desk trusts the actor it is started with. In production, run one desk over HTTP that takes the actor from each request's credential: npx -y agent-work-layer-mcp serve --keys keys.json, or createDeskHttpHandler with your own authenticate hook (OAuth 2.1 bearer tokens, API keys, mTLS). See the MCP package README. For real-time enforcement, run the MCP gateway (npx -y agent-work-layer-mcp gateway), which checks tools and budget at each tool call, not only when the report arrives. When the gateway or another team's system can't read the desk, give it Delegation Passes instead. See SPEC.md §9.1 and §10.
Authenticated actor
With stdio, each agent runs its own desk and declares its own actor, so a worker could start one as its manager. Over HTTP, every agent connects to one desk, which takes the actor from the request's credential through a pluggable authenticate(request) hook. Teams plug in what they already use: OAuth 2.1 bearer tokens, API keys or mTLS. An actor argument naming anyone else is refused (#16, SPEC.md §10.1).
Delegation Pass
When a worker starts, the desk signs a short-lived pass (a JWS) carrying the order's tools, budget and deadline. The worker presents it with each tool call, and a gateway or another team's system verifies it on its own, without calling the desk. A sub-order gets a narrower pass that names its parent, so the delegation rules (C1–C3, C5) can be checked offline (#17, SPEC.md §10.2).
A pass lasts 15 minutes by default, never past the deadline. The desk issues a new one each time the order enters working, and the worker renews it while it works.
It carries the order's whole budget; the gateway tracks what has been spent.
Cancelling or expiring the order stops new passes. There is no other revocation, which is why passes are short.
A pass is a JWS whose payload is a claims set, which makes it a JWT too. This diagram shows a pass's three parts and the order to verify them in.
import { WorkDesk, verifyPass } from "agent-work-layer";
const desk = new WorkDesk({ passes: { key: privateJwk, issuer: "https://desk.example.com" } });
// ...create, accept...
const { pass } = await desk.start(id, "agent:worker"); // renew with desk.issuePass(id, "agent:worker")
// Anywhere else, with only the desk's public key:
const verified = await verifyPass(pass, publicJwk, { issuer: "https://desk.example.com", worker: "agent:worker", order: id });
verified.allows("filings/search"); // true
const child = await verifyPass(childPass, publicJwk, { parent: verified }); // throws WIDER_THAN_PARENT if it breaks C1–C3 or C5
Keys are P-256 or Ed25519 JWKs (or WebCrypto keys) that you supply; the SDK does no key management. signPass and verifyPass use WebCrypto only, so they are also in agent-work-layer/validate for browsers, Deno and Bun. To make a key pair in Node:
Over MCP, awl-desk serve --pass-key priv.json --issuer <url> issues passes, and awl-desk gateway --pass-keys pub.json enforces them; see the MCP package README.
Development
The repo is an npm workspace with two packages: the core in packages/core and the MCP server in packages/mcp. The spec, schemas and examples stay at the root; the core copies them in when it is packed.
npm install
npm test # core and MCP tests (builds the core first)
npm run test:coverage
npm run typecheck
npm run test:package # packs both packages, installs them in clean projects and uses them
npm run check # all of the above; runs automatically before npm publish
npm run generate # after editing schemas/*.json: refreshes packages/core/src/generated.ts
The Python package in python/ is separate from the npm workspace:
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
Agent Work Layer ต้องใช้ API key ไหม?
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Agent Work Layer ใช้ทรานสปอร์ตแบบใด?
Agent Work Layer ทำงานแบบโลคัลผ่าน stdio
Agent Work Layer ถูกตรวจสอบล่าสุดเมื่อใด?
ตรวจสอบล่าสุดเมื่อ 2026-11-12 Work Orders and Work Reports for AI agents: a typed SDK, validator and lifecycle desk. The MCP server is in agent-work-layer-mcp.
