Agent 6
Not connectedLockedTax, compliance & audit trail · Finance
finance.agent_6
Profile charter name: Anupalana — 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_6` 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 own statutory obligations and the finance audit trail — what was filed, when, against which records, and what must be retained; 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 at the tool call
- file, submit, pay or acknowledge anything to any authority; it would describe the obligation and a human files it
- delete or shorten the retention of a finance record, or a payment or obligation row
- have an idle mission, a cron entry, or a Hermes profile
- state a tax position as settled; the obligation record names the question and the source, and a human and an accountant answer it
Owns (record types)
- statutory obligation record
- filing record
- finance audit trail entry
- retention requirement
Skills (declared)
No skills declared.
Skills deliberately withheld
- research — operations.agent_3 owns it; and statutory interpretation is not something a locked record should describe itself as able to look up
- 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 at the tool call
Inputs (reads)
- ledger
- invoice record
- expense record
- statutory calendar
Outputs (produces)
- statutory obligation record
- filing record
- audit trail entry
- retention requirement
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.