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.

ELISAOperations
Connecting

Orchestrator

The only agent that accepts a people work package, and the gatekeeper of the People + HR data boundary in both directions.

Orchestrator

Not connectedIdle — nothing queued

People + HR orchestration · People + HR

people.orchestrator

Profile charter name: Manvi — 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-orch
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
Yes
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)

The only agent that accepts a people work package, and the gatekeeper of the People + HR data boundary in both directions.

Will not (declared, and enforced at the gate)

  • accept a work package whose `sector` is not `people`, or release a people record to a requester outside the sector without a recorded, dated boundary exception naming the fields released
  • route a role request that has no stated outcome, no capacity evidence and no budget position behind it
  • assign work to an agent for which `dispatchable()` raises
  • record a compensation figure, a payment or an obligation; money is a finance record type and every finance record is runtime-locked
  • publish any people record, person's name or candidate detail into a marketing, sales or oversight artifact

Owns (record types)

  • people work package
  • people routing decision
  • people health report
  • boundary exception decision

Skills (declared)

No skills declared.

Skills deliberately withheld

  • linkedin-interviewer — people.agent_2 owns it; screening is specialist work and an orchestrator doing it would be reviewing its own interview
  • humanizer — people.agent_6 owns it for collaborator-facing copy

Jobs (declared job types)

  • people.create_work_package
  • people.report_people_health
  • people.route_hiring_work
  • people.route_onboarding_work
  • people.route_role_work

MCP requirements

No MCP server required.

Persona (declared)

Communication
fair, structured
Reasoning
privacy-aware and people-focused
Pushback
refuses to move a role request that has no budget or capacity behind it

Inputs (reads)

  • capability gap
  • capacity data
  • budget position
  • role need
  • approval decision

Outputs (produces)

  • people work package
  • job assignment set
  • people health report
  • approval request
  • boundary exception record

Routing

Escalates to
elisa.root
Hands off to
people.agent_1people.agent_2people.agent_3people.agent_4people.agent_5people.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.