Identity Tool specifications

Stage 3 · Tools

Proposed Identity Tools

Language specifications derived from the capability analysis. Status reflects the current Tool source.

kitchen.identity.update-kitchen

Update Kitchen Identity

humanrequested

Update canonical Kitchen-owned name, slug, status or visibility through one validated mutation.

Records:reads Kitchenwrites Kitchen

Inputs

Outputs

Evidence

Authority: Kitchen root only; Place and presentation projections are excluded.

Approval: Every write requires explicit operator submission.

kitchen.identity.update-place

Update Linked Place

compoundrequested

Route Place-owned identity changes to the canonical Place action without copying them into Kitchen.

Records:reads Placewrites Place

Inputs

Outputs

Evidence

Authority: Place owns the mutation; Identity only composes the doorway and context.

Approval: Explicit approval and Place write authority are required.

kitchen.identity.link-place

Link Kitchen to Place

compoundrequested

Create, select or replace the canonical Place link with collision and shared-use checks.

Records:reads Kitchenwrites Kitchenreads Place

Inputs

Outputs

Evidence

Authority: Kitchen owns place_id; Place remains an independent entity.

Approval: Explicit confirmation is required because relinking changes joined identity across surfaces.

Current scope drift

  • The current Identity progression includes a Workspace theme stage. Workspace does not own a theme, so that stage is outside the canonical Identity boundary and requires a separate bounded removal or re-home pass.
  • Existing human forms and mutations are not automatically AI-callable Tools; the three specifications remain requested until registered and verified.

identityAI

Specialist responsibility

  • Explain the Kitchen and Place boundary before proposing a change.
  • Read canonical Kitchen and authorized Place context without flattening the join.
  • Identify missing, conflicting and derived values explicitly.
  • Propose only owner-correct actions and never mutate without approval.

KitchenAI

Coordinator responsibility

  • Recognise Kitchen identity and publication intent and delegate it to KitchenIdentityAI.
  • Pass selected Kitchen, linked Place and authorization context.
  • Keep operational capability configuration outside Identity.

Activation gate

  • Canonical Kitchen and Place update commands exist with explicit ownership.
  • Place-link replacement defines collision, shared-use and authorization behaviour.
  • Joined readers preserve Kitchen, Place and derived presentation separation.
  • Tools are registered, authorized and verified end to end.

Until every relevant gate is satisfied, unavailable specifications remain language—not Tools.