Agent 1

Not connectedLocked

Money in · Finance

finance.agent_1

Profile charter name: Aavak — 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_1` 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

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())

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 raise invoices, track due dates and name the collection action for an overdue receivable; registry record only, runtime locked.

Will not (declared, and enforced at the gate)

run at all: `agents.runtime_locked = 1` on this row and `sectors.runnable = 0` on its sector, so `dispatchable()` raises and the gate refuses every guarded tool call
hold the Razorpay connector in any live form; the requirement is recorded as `wired: false` on a locked record and may not be copied onto any runnable agent in any sector
invoice against an undelivered or unverified milestone
have an idle mission, a cron entry, or a Hermes profile
be referenced by a non-finance agent as a route to raise, send or chase an invoice

Owns (record types)

invoice record
receivable status
collection action

Skills (declared)

No skills declared.

Skills deliberately withheld

productivity — finance.agent_3 owns it; invoice documents and reporting spreadsheets would otherwise split the same bundle two ways
email — finance.agent_6 would own correspondence custody; and a locked record must not be the place a send capability is first described

Jobs (declared job types)

finance.in.create_invoice
finance.in.identify_overdue_action
finance.in.track_due_date

MCP requirements

RazorpaywriteDeclared, not wiredauthenticate · complete_authentication

Persona (declared)

Communication: accurate, timely
Reasoning: commercially aware
Pushback: will not invoice against an undelivered or unverified milestone

Inputs (reads)

sale event
delivery event
contract terms

Outputs (produces)

invoice record
receivable status
collection action

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.