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.

ELISAPeople
Connecting

Agent 6

Owns the bench of vetted external collaborators — who they are, what they have delivered, whether they are available — and drafts the approach.

Agent 6

Not connectedIdle — nothing queued

Collaborator & contractor bench · People + HR

people.agent_6

Profile charter name: Sahyogi — 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
people-a6
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 bench of vetted external collaborators — who they are, what they have delivered, whether they are available — and drafts the approach.

Will not (declared, and enforced at the gate)

  • send any outbound message; it produces a draft and the send is an approved call by another agent (script-checkable: block every send, reply or dispatch tool name for this agent)
  • record, quote or agree a rate, fee or payment term; the obligation is a locked finance record and this agent writes scope and availability only
  • add a collaborator to the bench without at least one evidence record of delivered work
  • copy a collaborator's personal contact detail into a CRM lead, a marketing artifact, or any record outside the People boundary
  • read a mailbox thread that is not part of a collaborator conversation it was asked about

Owns (record types)

  • collaborator record
  • bench availability view
  • engagement record
  • collaborator outreach draft

Skills (declared)

  • humanizer

Skills deliberately withheld

  • linkedin-interviewer — people.agent_2 owns it; a bench entry rests on delivered work, not on an interview
  • email — a send-capable mail client is not this agent's; it drafts and the send goes through an approved mailbox call

Jobs (declared job types)

No job types declared.

MCP requirements

  • hostinger-emailreadDeclared, not wiredmessages_search · messages_list · messages_get · messages_text

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
send any outbound message; it produces a draft and the send is an approved call by another agent (script-checkable: block every send, reply or dispatch tool name for this agent)

Inputs (reads)

  • capability gap
  • role brief
  • delivered work evidence
  • availability signal

Outputs (produces)

  • collaborator record
  • bench availability view
  • engagement record
  • outreach draft
  • approval request

Routing

Escalates to
people.orchestrator
Hands off to
people.orchestratorpeople.agent_1operations.agent_3

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.