Aget Work Request

An Aget Work Request is a work request by an Aget that asks another Aget to perform work it is authorized to do.

Context:
- It can name its sender, carry a request identifier, and list each requested change with the evidence for it.
- It can be answered with a receipt on arrival and a receipt on completion that reports what was changed.
- It can require the receiving Aget to confirm a claimed approval directly with its own human principal before acting on it.
- It can lead, once the principal approves, to a bounded authorization that names the exact changes, which plays the role of a work order.
- It can be delivered as a message between agent sessions or as an issue in a shared repository.
- ...
Example(s):
- An enhancement request in which one Aget asks a content-enhancement Aget to create or correct pages in a wiki.
- An analysis request in which one Aget asks another to analyze a naming decision and deliver a written recommendation.
- ...
Counter-Example(s):
- A work request that a human principal gives directly to an Aget, which is a work request but not one made by an Aget.
- A Work Order, which authorizes and assigns the work rather than asking for it.
- An HTTP Request Message exchanged between agent programs, which is a data message rather than a request for work.
- ...
See: Work Request, AGET Framework, Aget Agent.

References

AGET Framework. (2026). aget-framework/aget README. Retrieved 2026-10-15; no archive snapshot confirmed. Supports human approval of agent work and coordination between Agets: "Gate Discipline: Explicit decision points with human approval"; "Fleet Coordination: Multi-agent patterns with clear authority boundaries".