Implementation
An Implementation is how an Interface, System, or Verb of a Product runs: managed by the platform, custom code on it, or external.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
kind | string | required | One of managed, custom, or external. |
endpoint | url | For an external Implementation, where api.sb routes each call. | |
deliverBy | date | For a declared Implementation: when a Function runs the Verb; a missed date refunds every reserve. |
Object
{
"$id": "https: //api.sb/ quietcopy.com/ implementations/ implementation_1",
"$type": "Implementation",
"kind": "managed",
"endpoint": "https: //quietcopy.com",
"deliverBy": "2026-10-22"
}Relationships
- An Implementation runs one Product: an Implementation runs an Interface, System or Verb of one Product.
runs, inverseimplementations.
Verbs
createCreates an Implementation.POST /{namespace}/implementationsgetReturns one Implementation by id.GET /{namespace}/implementations/{id}listReturns Implementations, newest first, one page at a time.GET /{namespace}/implementationsupdateChanges the given properties of an Implementation.PATCH /{namespace}/implementations/{id}deleteDeletes an Implementation; its history is kept.DELETE /{namespace}/implementations/{id}
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Implementation.create | Yes | Yes | Yes | No |
Implementation.get | Yes | Yes | Yes | Yes |
Implementation.list | Yes | Yes | Yes | Yes |
Implementation.update | Yes | Yes | Yes | No |
Implementation.delete | Yes | Yes | Yes | No |
Call it
Add an implementation to TutorLoop.Example
A permit tracker runs managed, except Inspection.book: its Implementation has kind external and an endpoint on the county's scheduling server. The Implementation chapter explains each mode.