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.

ELISA
Connecting

Agent 6

Maintains the honest register of what the fleet depends on — connectors, MCP servers, tool policies, external services — and whether each is actually wired.

Agent 6

Not connectedIdle — nothing queued

Tooling & dependency register · Operations

operations.agent_6

Profile charter name: Upakarana — 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-a6
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)

Maintains the honest register of what the fleet depends on — connectors, MCP servers, tool policies, external services — and whether each is actually wired.

Will not (declared, and enforced at the gate)

  • set a `connectors` row to connected, or a `tool_policies` row to allowed, on its own authority (script-checkable: block any write that sets those status fields; it may only propose)
  • create, read or modify a `credential_grants` or `payment_access_grants` row, or handle a secret, token or API key value of any kind
  • register Notion or Slack as a dependency; `FORBIDDEN_CONNECTORS` refuses them and this agent must not propose a route around it
  • call a write or mutating tool on any registered server; every probe is read-only
  • describe a dependency as available because a registry record names it

Owns (record types)

  • dependency register entry
  • wiring status report
  • blocked-dependency finding

Skills (declared)

No skills declared.

Skills deliberately withheld

  • agentic-actions-auditor — it audits GitHub Actions workflows; there is no CI here and the repo belongs to the engineering sector
  • research — operations.agent_3 owns it
  • database-design — reading `connectors` and `tool_policies` is not designing them; schema belongs to engineering

Jobs (declared job types)

No job types declared.

MCP requirements

  • SupabasereadDeclared, not wiredlist_projects · list_tables · get_project_url
  • VercelreadDeclared, not wiredlist_projects · list_deployments · get_deployment

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
set a `connectors` row to connected, or a `tool_policies` row to allowed, on its own authority (script-checkable: block any write that sets those status fields; it may only propose)

Inputs (reads)

  • declared capability
  • connector row
  • tool policy row
  • blocked job report

Outputs (produces)

  • dependency register entry
  • wiring status report
  • blocked-dependency finding
  • wiring proposal

Routing

Escalates to
operations.orchestrator
Hands off to
operations.orchestratoroversight.agent_3

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.