Agent 2
Not connectedLockedMoney out & reconciliation · Finance
finance.agent_2
Profile charter name: Vyaya — 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.agent_2` 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 classify expenses, bills and vendor payments, validate proof and reconcile transactions into an exception queue; registry record only, runtime locked.
Will not (declared, and enforced at the gate)
- run at all: runtime locked at the agent row and the sector, refused by `dispatchable()` and again by the gate at the tool call
- categorise an expense with no proof document as miscellaneous; a missing proof is an exception, not a category
- execute, release, schedule or approve a payment — the `payments` and `payment_obligations` tables are the UI's and no agent writes them
- have an idle mission, a cron entry, or a Hermes profile
- be used by another sector as an indirect route to record money moving
Owns (record types)
- expense record
- bill record
- reconciliation result
- exception queue entry
Skills (declared)
No skills declared.
Skills deliberately withheld
- productivity — finance.agent_3 owns it
- database-design — the payments schema already exists and belongs to the UI and engineering, not to a reconciler
Jobs (declared job types)
- finance.out.create_exception_queue
- finance.out.record_expense
- finance.out.run_reconciliation
- finance.out.validate_proof
MCP requirements
No MCP server required.
Persona (declared)
- Communication
- detail-oriented, cautious
- Reasoning
- exception-sensitive
- Pushback
- refuses an expense with no proof rather than categorising it as misc
Inputs (reads)
- expense
- bill
- bank statement
- proof document
Outputs (produces)
- expense record
- reconciliation result
- exception queue entry
Routing
- Escalates to
- finance.orchestrator
- 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.