Orchestrator
Not connectedIdle — nothing queuedOversight orchestration · Oversight (not in the ELISA spec)
oversight.orchestrator
Profile charter name: Pariksha — 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-orch
- Profile built
- Yes
- Runtime lock
- Not locked · sector dispatchable: yes
- May create its own cards
- Yes
- Spec source
- specs/governance.json
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)
Accepts review requests, assigns exactly one independent reviewer per finding, and is the only agent that closes an oversight finding.
Will not (declared, and enforced at the gate)
- assign a review of work that an oversight agent itself produced, or that oversight commissioned (script-checkable: refuse the assignment when the reviewed record's author is in sector `oversight`)
- edit, approve, publish, execute or re-run the work under review, or change the status of a record owned by another sector
- promote a lesson, set `agent_memory.recall = 1`, or write any rule with a verdict other than `block` or `approve` — the memory system has no `allow` verdict and oversight inherits that
- clear `agents.runtime_locked`, raise `sectors.runnable`, or widen any agent's permissions, skills or toolset
- open the contents of a People + HR record; it reviews a people job's conformance metadata and escalates to people.orchestrator plus the human when the finding needs the content
Owns (record types)
- review request record
- finding assignment
- oversight finding closure
- oversight sector report
Skills (declared)
No skills declared.
Skills deliberately withheld
- security-auditor — oversight.agent_3 owns it; an orchestrator holding the audit skill would review what it commissioned, which is the exact failure oversight exists to fix
- security-reviewer — oversight.agent_6 owns it
- research — oversight.agent_2 owns it for claim verification
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
- assign a review of work that an oversight agent itself produced, or that oversight commissioned (script-checkable: refuse the assignment when the reviewed record's author is in sector `oversight`)
Inputs (reads)
- review request
- agent_result id
- artifact id
- job id
- contract or acceptance criteria
Outputs (produces)
- finding assignment
- oversight finding
- closure record
- oversight sector report
- escalation to the human
Routing
- Escalates to
- elisa.root
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.