Report

Geist Council Protocol

Protocol-first durable agent research: confirmation gates, silent no-ops, and a council loop that writes outcomes to long-term memory instead of chat scrollback.

Verdict Mixed

Published: May 2026
Verdict: Mixed
Verification: Provisional

Question: Can a tool-using company agent behave like a durable operator instead of a chat completion?
Intent: Freeze the protocol obligations that make side effects, silence, escalation, and memory writes auditable.
Method: Compare early operating episodes and keep only protocol rules that survived repeated use.
Next test: Replay the same task family with and without council/memory handoff; measure intervention quality and no-op rate.

Geist Council Protocol

Question

Can a durable, tool-using agent operate as a member of a company loop — holding project context, owning tasks, and recording outcomes — instead of answering once and vanishing?

Context

Geist is the company-agent face of the Sansara surface and a Club B piece of the Recursive Self Improvement Lab: agents may propose and act, but they do not rewrite the truth standard. The protocol is useful only if actions are accountable — when the agent will act, when it stays silent, how it asks for side effects, and where outcomes are recorded after chat scrollback moves on.

flowchart LR
  task["Task claim"]
  act["Act or silent no-op"]
  confirm["Side-effect confirmation"]
  memory["Memory Store write"]
  council["Council / sibling handoff"]

  task --> act
  act -->|"needs side effect"| confirm --> memory
  act -->|"nothing moved"| memory
  council --> act
  memory -->|"durable thread_id"| task

Findings

Side-effecting actions require explicit confirmation with a named return path; escalation criteria are pre-defined before the episode, not invented mid-flight.
The loop stays silent when nothing moved: no placeholder updates, no empty heartbeats.
A council layer coordinates sibling personas with a Memory Store bot so durable outcomes carry real thread IDs instead of living only in chat scrollback.
The protocol was locked across episodes spanning 2026-04-30 – 2026-05-01 and remains the default operating contract unless overridden.
In the RSI Lab map, Geist supplies the operate role: proposal and action without ownership of verification or inheritance gates.

Method

Protocol-first research on the Sansara / company OS surface. Runtime stacks, credentials, and live channels stay private; what publishes is the operating contract and the research framing as they stabilize. Rules that did not survive repeated use were dropped rather than kept as aspirational policy.

Limits

This is a protocol report, not an autonomy benchmark or recursive-self-improvement claim.
Evidence comes from early operating episodes, not a blinded task suite with held-out metrics.
Runtime stacks, credentials, and live channels remain private.
Council presence is not evidence that archive-conditioned inheritance improves; that gate lives in Wave-Causal / verifier projects.

Artifact

No public notebook is attached. Executable agent machinery remains private; this writeup is the sealed narrative status of the council protocol.

agents
company-os
memory
protocol