Skip to content

Bot mode & project bot

Kido Bot

Automation

An enrolled Profile with a trigger and target Room; Bot mode runs the record.

Concept study
Kido Bot: A Profile, a trigger and a RoomAn inbound message meets a Bot record tied to a Room and a Profile, then returns as a reply. No autonomous schedule is depicted. A conceptual illustration, not a released architecture or deployment diagram.RoomBot recordProfileTriggerRoom

A Profile, a trigger and a Room

  • Inbound trigger
  • Enrolled Profile
  • Target Room

Conceptual illustration. See current scope & status below.

What is Kido Bot?

Bot mode runs a Bot: an enrolled Profile given a trigger and a target Room, with a long-lived conversation that answers the Room’s inbound messages. A Bot is a record over a Profile, not a Workflow or a separate automation engine. Within the Kido project, “Kido Bot” specifically means the Bot over hermes/kido-worker in kido/main, the Kido Bot Room; a Bot that speaks first on a schedule or event is an NPC.

What it is designed to do

  • Connect an enrolled Profile, a trigger and a target Room while keeping Profile identity separate from the Bot record.
  • Answer inbound Room messages through a long-lived conversation; distinguish this from an NPC that speaks first.
  • For the Kido project’s execution desk, take ready kidos through dispatch, verification, review, approval, merge on instruction and close, while reporting to the operator’s command center.

Illustrative use case

How it could fit into your work

In the documented managed setup, an operator prompts the worker in kido/main. The Room checks ready work, coordinates implementation and review, and asks home/main for the approval decision; it merges only after an instruction.

An example of the intended role, not a claim of a released workflow.