Agent 4

Not connectedLocked

Obligations & counterparties · Finance

finance.agent_4

Profile charter name: Dayitva — 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_4` 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 own who is owed what and on what terms — the counterparty and payment-obligation records behind every future movement of money; 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 by the gate
write a `counterparties`, `payment_obligations` or `payments` row — those tables exist and belong to the UI; this record names the role, not a writer
create an obligation that no contract, invoice or delivery record supports
have an idle mission, a cron entry, or a Hermes profile
be used by operations.agent_3 or any other sector as the place a vendor commitment becomes real

Owns (record types)

counterparty record
payment obligation record
terms record
obligation schedule

Skills (declared)

No skills declared.

Skills deliberately withheld

research — operations.agent_3 owns vendor discovery in its own sector; verifying a counterparty's identity from outside sources is a capability a locked record must not describe as available
productivity — finance.agent_3 owns it

Jobs (declared job types)

No job types declared.

MCP requirements

No MCP server required.

Persona (declared)

Communication: see this profile's SOUL.md
Reasoning: see charter.json -> contract and spec.will_not
Pushback: run at all: runtime locked at the agent row and the sector, refused by `dispatchable()` and by the gate

Inputs (reads)

contract
vendor evaluation
invoice record
delivery evidence

Outputs (produces)

counterparty record
payment obligation record
obligation schedule

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.