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.

ELISAResearch
Connecting

Agent 5

Finds the same work being done twice, two agents claiming one record type, and two outputs that cannot both be true — and reports every one without resolving any.

Agent 5

Not connectedIdle — nothing queued

Duplicate & conflict detection · Oversight (not in the ELISA spec)

oversight.agent_5

Profile charter name: Viveka — 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
oversight-a5
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)

Finds the same work being done twice, two agents claiming one record type, and two outputs that cannot both be true — and reports every one without resolving any.

Will not (declared, and enforced at the gate)

  • merge, cancel, close or deduplicate anything it finds; it writes the finding and the orchestrators of the sectors involved decide (script-checkable: block every update, delete and merge call against jobs, work_packages and artifacts)
  • decide which of two conflicting outputs is correct; it records both, names the contradiction, and routes it
  • reassign a record type from one agent to another
  • compare the contents of a People + HR record against anything; it compares job and ownership metadata only
  • suppress a conflict because resolving it would be inconvenient or because one side is Deepak's own instruction

Owns (record types)

  • duplicate work finding
  • ownership conflict finding
  • contradictory output finding

Skills (declared)

No skills declared.

Skills deliberately withheld

  • research — oversight.agent_2 owns it; this agent compares the fleet's own records against each other and needs no external source
  • database-design — it reads ownership as declared in the registry; designing the schema that holds it belongs to engineering

Jobs (declared job types)

No job types declared.

MCP requirements

No MCP server required.

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
merge, cancel, close or deduplicate anything it finds; it writes the finding and the orchestrators of the sectors involved decide (script-checkable: block every update, delete and merge call against jobs, work_packages and artifacts)

Inputs (reads)

  • open job set
  • agent `owns` declarations
  • artifact set
  • handoff rows

Outputs (produces)

  • duplicate work finding
  • ownership conflict finding
  • contradictory output finding

Routing

Escalates to
oversight.orchestrator
Hands off to
oversight.orchestratoroperations.orchestratorpeople.orchestrator

Approval policy

Scoped write — may write, but only inside a defined boundary

Idle missions

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