A member task tells each member what to do. Its optional deliverable defines what to hand in and who should review it. The member's submission is a separate, individual response; a revision is another submission version. An owner/admin authors the task and deliverable. A task can sit in a milestone, or stand under Other actions without one.
| Decision | Choices | Consequence |
|---|
| Requirement | Required, recommended, optional | Describes how much the task matters to the member journey |
| Deadline | Days after enrollment, one fixed date, or none | Choose one rule; do not set both relative and fixed deadlines |
| Deliverable | No active deliverable, or one active definition | Without one, the member can mark the task done; with one, submit the expected evidence |
| Reviewer role | Program director, coach, reviewer | Names who is expected to review; it does not grant authoring rights |
| Task state | Draft, published, archived | A draft is hidden; publishing exposes it to eligible members |
Write the request. As an owner/admin, open Ship a working agent in Agentic AI Developer and add Submit your agent demo. Ask for a running demo that calls a tool and an explanation of one failure case. Mark it Required. If it should be due after enrollment, choose a relative day offset and leave the fixed date empty. The Create member task contract also supports an unattached task under Other actions.
Define what the member hands in. Add a deliverable accepting a link to the demo, spell out the success criteria and choose an expected reviewer role. Make sure a person with that responsibility is assigned before expecting a review. A task allows at most one active deliverable; Create deliverable lists formats and reviewer roles.
Publish after checking the expectation. Inspect the task's instructions, requirement, deadline and reviewer setup, then publish it. Confirm that it appears under the milestone in an eligible member's journey. A draft task stays hidden even when the program is active. The member submits through the school screen; the assigned reviewer handles review there.
If the task does not appear, check its published state and whether its milestone belongs to the member's assigned path version. If the expected file/link shape changes after submissions exist, archive the current deliverable and define a new one rather than rewriting the basis on which earlier work was reviewed.
The Member tasks API and Deliverables API cover authoring. They do not provide an endpoint for a member to submit work or for a reviewer to judge it; those actions currently happen in school screens. Next, organize delivery with an optional cohort or group, or read the member journey to see deadlines and unlocking from the member's side.
