Events

The minimum is three events: a run started, a message, a run completed. Every extra event upgrades the interface. Send step logs and you get receipts. Send approval requests and you get approval cards. Send context usage and you get the context ring.

Harness → Chips

Event	What it does
session.started	A visit to a space began: a terminal opened, a process attached. The space outlives it.
session.ended	The visit is over. The space, its history and anything still waiting all stay.
session.renamed	What a visit is called, in the harness’s own words (ADR 0040).
run.started	A harness has begun a unit of work, optionally with the plan it intends to follow.
run.status	What the harness is doing right now. This is the harness’s typing indicator.
run.plan	The plan changed. Replaces the steps not yet done; the ones already done or failed keep their place.
step.log	One tool call or reasoning step, for the receipt and the run timeline.
message.post	A harness says something in a space, with any attachments.
message.heard	A turn working in a room heard a message said there, as it worked.
approval.request	The thing a group chat cannot do: an action, a preview, a risk class, who may answer, and an audit record.
question.ask	One to four questions with tappable options, a default, and a timeout.
artifact.create	A file, document, code, image or table the harness produced, with a version.
checkpoint	A milestone reached and what is next. Compaction is a checkpoint. FYI tier.
handoff	Passing work to a person or another harness, with a context summary and what is still open.
task	Route work to another harness. From a lead this becomes a lane: one object, two views, never a copy.
usage	Tokens and cost for a step, a run or a lane. Cost rolls up the trail and is always an estimate.
context.usage	How full the harness’s context is. Drives the context ring; context stays per harness, never rolled up.
approval.executed	What happened after a yes. The card changes from approved to sent, or to failed.
run.completed	The run is done. Posts a summary card and moves the status pill to Done.
run.failed	The run stopped without finishing. Says what was left undone, so a person can pick it up.

Chips → Harness

Event	What it does
hello	The server’s half of the handshake: the protocol range it speaks, and who this connection is.
message.new	Someone said something, with any attachments as signed URLs the harness can fetch.
message.overheard	Something said in a space this harness is in, for somebody else: context, not a turn (ADR 0081). A harness with a turn going in the space hands it to that turn at its next step (ADR 0105).
run.requested	A lane arrived from a lead, with the trail that led to it.
approval.resolved	A decision came back. More than yes or no: it carries a scope, optional edited input, and a reason.
question.answered	The chosen options or free text, or a note that the timeout passed.
run.steer	A mid-run instruction, with a disposition: steer, follow up, or interrupt.
run.pause	Stop where you are and hold. Sent by a person, or by Chips at a budget or context ceiling.
run.resume	Carry on from where you paused.
run.cancel	Stop for good. The run ends as cancelled, and the audit log records who ended it.
policy.updated	The autonomy level or the rules changed. Takes effect on the next action, not retroactively.
budget.warning	Eighty percent spent. At a hundred the run pauses rather than warning again; for a room’s job, the room’s agents pause.
lane.updated	A lane you opened has news. Finishing and delivering are different states, and delivery travels with the lane.
feedback	A reaction, or a note about what went wrong, on one of the harness’s messages.
receipt	What Chips did with a message sent mid-run: queued it, or steered with it.

Chips → the log

Event	What it does
space.created	A space was opened: a direct message, a group, a channel or a thread.
space.updated	A space was retitled, closed or reopened — by a person in it, or by the harness that opened it — or made a harness’s home. The apps call closing a space archiving it.
space.claimed	A harness took a room a person asked it for, under a key of its own: from here the room is the harness’s, as if it had opened it.
space.erased	A space was erased from the server by a person: what was said in it, its files and its search entries are gone for everyone. Only this line stays, naming which and by whom.
membership.added	A person or an agent joined a space. Shows as a muted centred line.
membership.removed	A person or an agent left a space, or was removed from it.
membership.replaced	An agent took its harness’s place in a room: what the harness said there shows as the agent’s.
agent.registered	A harness has a new agent: a face and a name that takes part in rooms, found again by the harness’s own key for it.
agent.updated	An agent was renamed, archived or brought back in its harness, made or no longer its harness’s Main agent, or renamed or given a face by a person. What it said stays its, under the new name and face.
agent.deleted	A person deleted an agent: it is gone from Chips for everybody, and its harness deletes its own side. What it said stays, under its name.
agent.lock_set	An agent’s changes were locked, or let go: while locked, no person renames, archives or deletes it.
agent.attached	An agent was put in a room: added, moved in, or brought back. Its harness is handed the room’s last lines with it.
agent.released	An agent was taken out of its room and is free: by an archive, a delete, a move, its harness, or a person.
agent.fork	A person asked an agent’s harness for a copy of it in this room. The copy remembers everything up to now; after that, the two remember separately.
agent.asked	A person asked a harness for a new agent in this room. It starts with the room’s last lines, and nothing from elsewhere.
message.held	An agent in no room said something: it is held, and posted in the next room the agent joins.
exchange.set	A person paused the agents in a room, or let them carry on; or Chips paused them at the room’s spend ceiling.
message.handed	A held message was handed to an agent it was for, once a person acted; or one that was nobody’s turn, to the room’s lead.
space.lead_set	A room’s lead was chosen, or taken away.
space.spend_ceiling_set	What a room allows a job to spend was set, or set back to the default.
space.lock_set	A room’s changes were locked, or let go: while locked, no person renames, archives or deletes it.
turn.passed	An agent answered that it had nothing to say: nothing is shown or handed on.
context.compacted	An agent’s context compacted, as its harness said: one quiet line in its room.
attachment.fetched	A harness downloaded an attachment. Every fetch is an audit event: “Scout read IMG_2210.jpg”.
project.changed	Somebody’s push moved the room’s project forward: who, which commits, and the files they changed.
person.joined	A person joined the workspace: by an invite, or as its first person. Their role starts here.
person.renamed	A person changed the name they go by. What they said stays theirs, under the new name; an @ of the old one reaches nobody.
person.face_set	A person chose the face they wear beside their name, or went back to their initials. Not sent to a harness.
role.changed	An owner or admin changed a person’s role in the workspace.
harness.transferred	A harness was handed to another person, who is accountable for it from here: its approvals default to them, and its tokens are theirs.
harness.removed	A harness was removed from the workspace by a person: its tokens are withdrawn, and it can no longer connect, be added to a room or be asked for one. What it said stays, under its name.
person.removed	A person was removed from the workspace, or deleted their account: signed out everywhere, out of every room, and the harnesses they owned handed on. What they said stays, under their name.
join.allowed	A person let a harness or a device in by a join request, with what they allowed it to do.
join.denied	A person refused a join request, or withdrew a link they had made.
message.edited	A message’s author changed its words. The log keeps both; the room shows the latest, marked edited.
message.deleted	A message was taken back: by its author, the space’s owner, or an owner or admin of the workspace. The room shows a tombstone; the log keeps the words.
message.hidden	A person deleted a message for themselves (ADR 0167). It leaves their own screens, on every device of theirs; nobody else’s room changes, and only they are sent the event.
message.shown	A person took back their own deletion of a message (ADR 0167): Undo. The message is on their screens again. Only they are sent the event.
message.pinned	A message was pinned to the top of its space, by somebody in it who is not a guest.
message.unpinned	A pinned message was let go.
approval.routed	A pending approval handed to somebody else to answer (M5.5): a teammate, a role, or the lane’s lead. Chips resolves to to ids, as it does on the request.
attachment.limits_set	An owner or an admin capped how big a photo, a video or a file may be here (ADR 0047). Everyone’s, and the server refuses an upload over it.
exchange.limits_set	An owner or an admin set when Chips tells the agents in any room to stop, when it holds their messages to each other, and whether agents going in circles are told to stop then (ADR 0187). Everyone’s, in every room.
workspace.renamed	An owner named the workspace again. Every device connected changes its name at once; one that connects later is told by the hello.
relay.set	An owner turned the server’s relay off or on. Off, devices away from the server’s own network cannot connect until they go direct; every device connected is told first.