Actor Agreed
A Knowledge Islands word · its card
Definition
An actor gives each piece of work someone who answers for it, who stays the same while the sessions that act for it come and go.
An actor is whoever acts at a node of the work tree, a person or an agent, the owner among them. An actor persists across sessions and agent hosts, where a session is one run: many sessions may act as one actor, one after another or at once. The industry has no word for it; the Unified Modeling Language's actor, someone outside a system who uses it, is related but not the same, and is not mapped.
An agent actor runs as one of two types (ACTOR-TYPES): a session actor, run as an agent host's session, opened by an opener and a bootstrap and kept by hand, or a bot actor, run as a bot, a named identity its agent host keeps and wakes.
Our conventions
- One roster file each: every actor has one file in the store's roster, named by its id. It opens
ki-id: actor:<id>, thenki-document-type: actor, an optional humanki-name, thenki-kind, the actor's type:agentfor a session actor,botfor a bot actor, orcharacterfor one that never runs, aski-id: actor:waylandwithki-name: Waylandandki-kind: bot(ACTOR-KEY and ACTOR-TYPE-FIELD, in the store contract'ski-fields). - An actor with no name of its own takes the id of its role in its work package,
<package>@<role>, asactor:ki.cairn@information-architect, its roster file named the same (SEAT-AT). - Ids, never copies: a work package's
workersentry points at its actor byid: actor:<id>, and a meeting's participant carries only its actor id and how it is reached, so no file repeats another's fields. - Presence lives in the roster file: an agent actor's agent host and agent harness, as
ki-hostandki-harness(PRESENCE-FIELDS a), and the rig it runs on are its roster file's; who acts where is the work tree's.