Team Tools

Stage 3 · Tools

Working and proposed Team Tools

Registered Tools are callable now. Research hypotheses remain visibly requested.

Registered

Working Team Tools

kitchen.team.create-member

Add a member

connectedwrite

Creates one active member in the selected Kitchen Team.

Confirmation: required

kitchen.team.read-members

Read the current authorized Kitchen Team member collection.

connectedread

Returns the current bounded Team member list.

Confirmation: none

kitchen.team.update-member

Update a member

connectedwrite

Preserves member identity while updating the supported name field.

Confirmation: required

kitchen.team.delete-member

Delete a member

connectedwrite

Permanently removes the unlinked member from the selected Team.

Confirmation: required

kitchen.team.create-invitation

Create an invitation

connectedwrite

Returns a copyable invitation link for the selected member.

Confirmation: required

Research response

Proposed Team Tools

kitchen.team.record-station-competence

Record Station Competence

humanrequested

Record a reviewed, time-bound competence claim for one member and Station.

Authority: Kitchen Team owns the member evidence; Station owns Station identity and requirements.

Approval: Explicit reviewer submission is required.

kitchen.team.record-training

Record Training Evidence

humanrequested

Record completion or certification evidence without inferring competence from a file or note.

Authority: Team owns the member evidence; Food Safety owns food-safety requirements and compliance interpretation.

Approval: Explicit operator or reviewer submission is required.

kitchen.team.create-handover

Create Shift Handover

compoundrequested

Create a time-bound handover that references unresolved records from their owning capabilities.

Authority: Team owns the handover envelope; every linked operational record retains its owner.

Approval: Publishing and acknowledging a handover require explicit human actions.

Current scope drift

  • `KitchenTeamMember` currently includes `hourly_rate`, `currency` and `shift_label`. Payroll and scheduling are outside the agreed Kitchen Team boundary and require a separate model-consumer-data migration pass.
  • The dossier draft may assist reviewed onboarding, but extracted text is not authoritative training, certification or competence evidence.

TeamAI

  • Use only the selected Kitchen Team and authorized member records.
  • Use the five registered Team Tools according to their input, confirmation and result contracts.
  • Keep member identity, User identity, App membership and access distinct.
  • Never infer competence, certification, availability, employment status, pay or performance.
  • Treat proposed competence, training and handover Tools as unavailable.

KitchenAI

  • Recognise Kitchen Team intent and delegate it to TeamAI.
  • Pass selected Kitchen, member selection and authorized user request.
  • Route Station, Food Safety and operational record questions to their owning specialists.
  • Require confirmation for write and destructive Team Tools.