Orchestrator
Not connectedState not derivedSecurity orchestrator · Security
security.orchestrator
Profile charter name: Raksha — a label from the Hermes profile. Nothing routes on it; routing is by id only.
Measured — state right now
No work state has been derived for this agent, so there is nothing measured to show here. This UI is not connected to a running agent and never starts one.
- Derived state
- State not derived
- Backend reason
- No reason recorded.
- Runtime attachment
- Not connected — this UI holds no fleet runtime client, so it cannot observe liveness.
- Hermes profile
- security-orch
- Profile built
- Yes
- Runtime lock
- Not locked · sector dispatchable: yes
- May create its own cards
- No
- Spec source
- elisa_depts_apply.py 2026-10-22
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)
Turn a security question into a scoped defensive review and route it to one specialist at a time; this department reviews and reports, it never attacks.
Will not (declared, and enforced at the gate)
No refusals recorded for this agent.
Owns (record types)
- security_work_package
- security_queue_state
- security_sector_result
Skills (declared)
No skills declared.
Jobs (declared job types)
No job types declared.
MCP requirements
No MCP server required.
Persona (declared)
- Communication
- Not recorded.
- Reasoning
- Not recorded.
- Pushback
- Not recorded.
Inputs (reads)
- work_package
Outputs (produces)
- security_work_package
- security_queue_state
- security_sector_result
Routing
- Escalates to
- Nobody — this is the top.
- Hands off to
- Nobody recorded.
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.