Mixed freshness. Depending on the panel, rows here are read live from elisa-core or come from a frozen copy of ELISA’s local store taken on 22 October 2026 — each panel says which, underneath itself. No agent is running.

ELISAPeople
Connecting

Agent 5

Keeps the written record complete and findable — runbooks, the artifact and evidence index, and custody of the files a job produced.

Agent 5

Not connectedIdle — nothing queued

Documentation & record custody · Operations

operations.agent_5

Profile charter name: Abhilekha — a label from the Hermes profile. Nothing routes on it; routing is by id only.

Measured — state right now

Idle — nothing queued. A profile exists, its queue is empty and nothing is pending. Idle describes the queue, not a live process. This UI is not connected to a running agent and never starts one.

Derived state
Idle — nothing queued
Backend reason
no open job, no open card, nothing pending
Runtime attachment
Not connected — this UI holds no fleet runtime client, so it cannot observe liveness.
Hermes profile
operations-a5
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
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()) · elisa.db:approvals.status='pending' · elisa.db:jobs.status · kanban.db:tasks.status (assignee=profile)

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)

Keeps the written record complete and findable — runbooks, the artifact and evidence index, and custody of the files a job produced.

Will not (declared, and enforced at the gate)

  • call `trash_file`, `share_file`, or any delete or permission change on Google Drive (script-checkable: block those tool names outright for this agent)
  • write to any path under `C:\elisa\engine\` or `C:\elisa\ui\`
  • index or copy a People + HR document; people records stay inside the People boundary and are referenced by id
  • declare an artifact present without resolving it; a missing file is recorded as missing, never silently re-created or restored
  • overwrite an existing document to 'update' it; a new version is filed alongside

Owns (record types)

  • runbook
  • artifact index entry
  • evidence index entry
  • file custody record
  • retention note

Skills (declared)

No skills declared.

Skills deliberately withheld

  • note-taking — operations.agent_2 owns it. The SOP author and the record custodian both want it; the SOP is the harder authoring job, so it keeps the skill and this agent works from the ERP's own tables
  • productivity — operations.agent_1 owns the bundle

Jobs (declared job types)

No job types declared.

MCP requirements

  • Google DrivereadDeclared, not wiredsearch_files · get_file_metadata · read_file_content · list_recent_files
  • Google DrivewriteDeclared, not wiredcreate_file · update_file · copy_file

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
call `trash_file`, `share_file`, or any delete or permission change on Google Drive (script-checkable: block those tool names outright for this agent)

Inputs (reads)

  • completed job record
  • artifact id
  • evidence id
  • storage location

Outputs (produces)

  • runbook
  • artifact index entry
  • custody record
  • missing-record report

Routing

Escalates to
operations.orchestrator
Hands off to
operations.agent_2operations.orchestratoroversight.agent_2

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.