Orchestrator
Not connectedLockedFinance orchestration · Finance
finance.orchestrator
Profile charter name: Arthika — a label from the Hermes profile. Nothing routes on it; routing is by id only.
Measured — state right now
Locked. Locked by instruction. Its sector is not runnable or the record is runtime-locked, so a dispatch is refused — not an empty queue, a recorded refusal. Deepak's instruction 2026-10-20: the Finance agent stays OFF in the backend; the finance guardrails live in the UI only for now. Money is the one place where 'nobody gave it work yet' is not a safety property, so this is a recorded refusal rather than an empty queue. The Finance REGISTRY RECORDS and the payments / obligations / counterparties / access-grant tables are fully built; what does not exist is any path by which a Finance agent can run. See docs\ELISA-FLEET.md 'The Finance lock' for the five layers and what undoing it would take.
- Derived state
- Locked
- Backend reason
- `finance.orchestrator` is RUNTIME LOCKED and cannot be given work
- Runtime attachment
- Not connected — this UI holds no fleet runtime client, so it cannot observe liveness.
- Hermes profile
- None built. A registry record with no profile on disk — nothing to spawn.
- Profile built
- No
- Runtime lock
- Locked · sector dispatchable: no
- May create its own cards
- No
- 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)
Would route money-in, money-out, reconciliation, planning and reporting across the six finance specialists; it is a registry record only and no path exists by which it can run.
Will not (declared, and enforced at the gate)
- run at all: `sectors.runnable = 0` and `agents.runtime_locked = 1`, so `dispatchable()` raises before a sector is even consulted and `lesson_gate.py` refuses every guarded tool call at the tool itself
- be given a Hermes profile, a run directory, or an entry in `kanban.dispatch_profiles` — the dispatch allowlist is fail-closed and a card naming an unlisted profile is never claimed
- hold a cron job, an idle mission or any standing scan; there is nothing to schedule and nothing that may be scheduled
- be unlocked by a lesson, a finding, an idle mission or any agent in any sector; the memory system has no `allow` verdict and oversight is explicitly barred from touching the lock
- have its records read as a capability statement: the payments, payment_obligations, counterparties and payment_access_grants tables belong to the UI, and these rows exist so the UI has a role to label
Owns (record types)
- finance work package
- finance exception queue
- finance sector report
Skills (declared)
No skills declared.
Skills deliberately withheld
- productivity — finance.agent_3 owns it for statements and reports; and on a runtime-locked record a skill is inert either way, so ownership is recorded for the UI, not for execution
Jobs (declared job types)
- finance.escalate_exceptions
- finance.issue_reports
- finance.route_events
- finance.validate_records
MCP requirements
No MCP server required.
Persona (declared)
- Communication
- conservative, precise
- Reasoning
- close-readiness first
- Pushback
- unwilling to hide exceptions
Inputs (reads)
- transaction record
- ledger state
- budget
- exception
Outputs (produces)
- finance work package
- exception queue
- finance report
- approval request
Routing
- Escalates to
- elisa.root
- Hands off to
- Nobody recorded.
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.