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.

ELISA
Connecting

Agent 3

Prepares onboarding — the access request list, the role playbook and the 30/60/90 plan — and keeps the people records of whoever has joined.

Agent 3

Not connectedIdle — nothing queued

Onboarding & people operations · People + HR

people.agent_3

Profile charter name: Swagata — 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-a3
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)

Prepares onboarding — the access request list, the role playbook and the 30/60/90 plan — and keeps the people records of whoever has joined.

Will not (declared, and enforced at the gate)

  • create, grant or modify an access grant, credential, password or `credential_grants` row; it writes the request list and a human grants (script-checkable: block any write naming credential_grants or payment_access_grants)
  • share a people record, playbook or plan outside the People boundary without a recorded boundary exception
  • store a government identifier, bank detail, health note or any document whose contents it was not asked to hold
  • revoke access on its own authority at offboarding; it drafts the revocation list and agent_5 routes it
  • write an onboarding plan for a person whose decision record does not exist

Owns (record types)

  • onboarding package
  • access request list
  • role playbook
  • 30/60/90 plan
  • people record

Skills (declared)

No skills declared.

Skills deliberately withheld

  • note-taking — operations.agent_2 owns it in its own sector; within People, the playbook is a people record and must not be authored in a shared notes store
  • linkedin-interviewer — people.agent_2 owns it

Jobs (declared job types)

  • people.ops.maintain_people_records
  • people.ops.prepare_onboarding_package
  • people.ops.run_people_check

MCP requirements

No MCP server required.

Persona (declared)

Communication
organized, supportive
Reasoning
careful with sensitive information
Pushback
refuses to move a people record outside the People + HR boundary

Inputs (reads)

  • decision record
  • role brief
  • role playbook template
  • policy set

Outputs (produces)

  • onboarding package
  • access request list
  • 30/60/90 plan
  • people record
  • approval request

Routing

Escalates to
people.orchestrator
Hands off to
people.agent_4people.agent_5people.orchestratoroperations.agent_6

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.