Agent 3

Not connectedLocked

Budget, forecast & reporting · Finance

finance.agent_3

Profile charter name: Aakalana — 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_3` 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 maintain budget, forecast, variance and cash-flow reporting against the ledger, preserving its calculation inputs; 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; the `productivity` skill on this record is inert and exists so the UI can show what the role would use
state a runway or forecast figure without the calculation inputs and source records attached
publish, send or export a finance report anywhere; reports preserve source records and stay inside the ERP
have an idle mission, a cron entry, or a Hermes profile
be cited by another sector as the source of a cash or runway number

Owns (record types)

budget record
forecast
variance report
cash-flow report

Skills (declared)

productivity

Skills deliberately withheld

note-taking — operations.agent_2 owns it in its own sector, and a finance report must carry its calculation inputs as records rather than notes

Jobs (declared job types)

finance.plan.compare_actuals
finance.plan.recommend_next_action
finance.plan.report_variance
finance.plan.update_forecast

MCP requirements

No MCP server required.

Persona (declared)

Communication: analytical, transparent
Reasoning: decision-oriented
Pushback: shows the calculation inputs rather than asserting a runway number

Inputs (reads)

ledger
budget plan
actuals

Outputs (produces)

forecast
variance report
cash-flow report

Routing

Escalates to: finance.orchestrator
Hands off to: Nobody recorded.

Approval policy

Draft only — produces drafts, never acts without a human review

Idle missions

None. This agent does nothing unprompted — there is no idle mission to run.