Service delivery
Service delivery runs each job to its Outcome Contract: steps, oversight per Verb, delivery, acceptance, remedy and proof.
Done is not accepted: the Customer pays for the outcome once it is accepted.
Summary
| Part | This System |
|---|---|
| Group | Commerce and fulfillment |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Reference: documented, never offered first |
You can ask:
- “Deliver this job to the contract”
- “Which jobs are late?”
- “Redo this delivery”
- “Show the customer proof of each step”
What you get
| Part | This System |
|---|---|
| Starts | Opt-in: it wakes with the Product Templates that need it (Services-as-Software, E2E managed service). |
| Built from | Workflows, Functions, AI gateway, Event streams, Agents |
Nouns it owns
| Noun | Definition |
|---|---|
| Outcome Contract | An Outcome Contract is the terms on an Offer that warrant a Service’s result: done, acceptance, assurance, remedy, and earnings. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Order.deliver | Order | None | Order.delivered |
| Order.confirm | Order | Asks first; waits 1 business hour | Order.confirmed |
| Order.dispute | Order | None | Order.disputed |
| Order.revise | Order | None | Order.revised |
| Order.start | Order | None | Order.started |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Order.delivered | By Order.deliver |
| Emits | Order.confirmed | By Order.confirm |
| Emits | Order.disputed | By Order.dispute |
| Emits | Order.revised | By Order.revise |
| Emits | Order.started | By Order.start |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Delivery Manager |
| Team | Operations Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
Approvals and limits
| Verb | Rule | Detail |
|---|---|---|
| Order.confirm | A person says yes first | Waits 1 business hour |
Processes that use it
| Process | How it uses it |
|---|---|
| Delivery | A step calls Order.deliver |
| Licensed review | A step calls Order.deliver |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Delivery Manager’s view | The Metrics its accountable Role answers for. | Accepted outcomes |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (8) |
admin | All but 1 of 8: Order.confirm |
member | All but 1 of 8: Order.confirm |
viewer | Read only (2 of 8) |
Import and export
None.
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Controls it carries:
Related Systems
Example
A Services-as-Software site audit promises 50 fixed technical errors within ten days. Agents deliver the fixes with a before-and-after crawl; the buyer accepts 47 and rejects three. Service delivery runs the remedy on those three, then bills the accepted outcome.