Mixed freshness. Depending on the panel, rows here are read live from elisa-core or come from a frozen copy of ELISA’s local store taken on 22 October 2026 — each panel says which, underneath itself. No agent is running.

ELISASales
Connecting

Agent 4

Owns the calendar as a commitment record: what was promised to whom, by when, and whether the slot still exists.

Agent 4

Not connectedIdle — nothing queued

Scheduling & commitments · Operations

operations.agent_4

Profile charter name: Samaya — a label from the Hermes profile. Nothing routes on it; routing is by id only.

Measured — state right now

Idle — nothing queued. A profile exists, its queue is empty and nothing is pending. Idle describes the queue, not a live process. This UI is not connected to a running agent and never starts one.

Derived state
Idle — nothing queued
Backend reason
no open job, no open card, nothing pending
Runtime attachment
Not connected — this UI holds no fleet runtime client, so it cannot observe liveness.
Hermes profile
operations-a4
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
No
Spec source
specs/governance.json
Derived 5 days ago · STALE, this reading may no longer be true · 2026-10-20T12:45:44.000Zfrom elisa.db:agents.runtime_locked+sectors.runnable (via dispatchable()) · elisa.db:approvals.status='pending' · elisa.db:jobs.status · kanban.db:tasks.status (assignee=profile)

Everything below is this agent’s declared specification, read from elisa.db. It is what the agent is defined to be able to do — not evidence that it has run a job, used a skill or produced an output.

Mission (declared)

Owns the calendar as a commitment record: what was promised to whom, by when, and whether the slot still exists.

Will not (declared, and enforced at the gate)

  • create, move or delete a calendar event that has an external invitee without an approval token on that specific event (script-checkable: block `create_event`/`update_event`/`delete_event` when `attendees` is non-empty and no approval id is present)
  • accept or decline an invitation on Deepak's behalf
  • schedule anything inside a block a human marked private or busy without saying so in the proposal
  • read an event's description or attachment contents to enrich another sector's record; it reads time, title and participants
  • commit to a date that a project record does not support, without naming the dependency that breaks

Owns (record types)

  • commitment record
  • calendar hold
  • scheduling proposal
  • availability view

Skills (declared)

No skills declared.

Skills deliberately withheld

  • productivity — operations.agent_1 owns the bundle. Its `google-workspace`, `maps` and `meeting-action-items` sub-skills are the ones this agent needs, which is why sub-skill scoping is in skills_wanted rather than a second claim on the same directory
  • email — nothing in operations sends mail; outbound belongs to the sales and marketing sectors and to people.agent_6 for collaborators

Jobs (declared job types)

No job types declared.

MCP requirements

  • Google CalendarreadDeclared, not wiredlist_calendars · list_events · search_events · suggest_time
  • Google CalendarwriteDeclared, not wiredcreate_event · update_event · delete_event

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
create, move or delete a calendar event that has an external invitee without an approval token on that specific event (script-checkable: block `create_event`/`update_event`/`delete_event` when `attendees` is non-empty and no approval id is present)

Inputs (reads)

  • commitment request
  • project deadline
  • availability window
  • approval decision

Outputs (produces)

  • scheduling proposal
  • commitment record
  • calendar hold
  • conflict report

Approval policy

Approval required — every action waits on a human decision

Idle missions

None. This agent does nothing unprompted — there is no idle mission to run.