Role

The work and its Permissions stay with the seat when a new filler takes it.

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/kilnbakery.com/roles/role_1",
  "$type": "Role",
  "name": "Kiln Bakery",
  "responsibilities": "Example responsibilities",
  "status": "vacant",
  "autonomy": {
    "default": "supervised",
    "byClass": {
      "high": "assist"
    }
  }
}

RelationshipsCopy Anchor Link

• A Role is filled by many Workers: a Worker, human or agent, fills a Role and acts under its Permissions; one Agent can fill Roles in many Startups. filledBy, inverse fills.
• A Role holds many Permissions: a Role’s Permissions are what its Worker may do: Verbs on Nouns within a scope and a Limit. holds, inverse heldBy.
• A Role has many Openings: an Opening is a need for a Human in one Role, taking a share of that Role’s work. openings, inverse staffs.
• A Role has many Personas: the Role whose Permissions a Persona signs in with, so an App compiles its Dashboards and Verbs from one record. personas, inverse holds.
• A Role requires many Skills: the Skills, each at a level, a Worker needs to fill the Role. requires, inverse requiredBy.
• A Role has many Role Reviews: each Role Review checks one Role, and a Role keeps every review it has had. roleReviews, inverse reviews.
• A Role has one Team: a Team groups the Roles that do one kind of work under one owner. team, inverse groups.

LifecycleCopy Anchor Link

VerbsCopy Anchor Link

1. createCreates a Role.
   POST /{namespace}/rolesdoRole.created
2. getReturns one Role by id.
   GET /{namespace}/roles/{id}readNo Event
3. listReturns Roles, newest first, one page at a time.
   GET /{namespace}/rolesreadNo Event
4. updateChanges the given properties of a Role.
   PATCH /{namespace}/roles/{id}doRole.updated
5. deleteDeletes a Role; its history is kept.
   DELETE /{namespace}/roles/{id}doRole.deleted
6. reviewReview checks one Role against its contract for a period and records a Role Review.
   POST /{namespace}/roles/{role}/reviewdoRole.reviewed
7. staffStaff fills a Role with a Worker, human or agent, who then performs the Role’s Verbs under its Permissions.
   POST /{namespace}/roles/{role}/staffdoRole.staffed
8. vacateVacate takes the Worker out of a Role, and the seat’s Tasks route to the Role it escalates to until a new Worker is staffed.
   POST /{namespace}/roles/{role}/vacatedoRole.vacated

PermissionsCopy Anchor Link

Which Access level may call each Verb. One-way Verbs wait their delay window.

Call itCopy Anchor Link

Staff the latest role with a worker.

ExampleCopy Anchor Link

The Customer Lead Role at a tutoring marketplace owns first replies and refunds under $100. An Agent fills it on weekdays and the Founder on weekends; the $100 refund Limit binds both.