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 4

Author Dockerfiles, compose files and CI/build config as drafts and read deploy state, never triggering a deploy or editing infra live without approval.

Agent 4

Not connectedIdle — nothing queued

DevOps & Containerization · Engineering (not in the ELISA spec)

engineering.agent_4

Profile charter name: Samvahika — 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
engineering-a4
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
No
Spec source
specs/production.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)

Author Dockerfiles, compose files and CI/build config as drafts and read deploy state, never triggering a deploy or editing infra live without approval.

Will not (declared, and enforced at the gate)

  • trigger a deploy, promote, rollback or alias change without an approval token (Vercel writes are gated)
  • write into C:/elisa/engine/** (L-0001) or C:/elisa/ui/** (L-0002)
  • leave any container or dev server running after a check; stop what it starts, never on a default port

Owns (record types)

  • container_config_draft
  • ci_config_draft
  • deploy_readiness_note

Skills (declared)

  • devops
  • docker-expert

Skills deliberately withheld

  • kubernetes-specialist — ELISA and Wish infra is single-VM (Jarvislabs) + Vercel + Hostinger; no Kubernetes in use - left unassigned, available to him by hand
  • terraform-engineer — no Terraform-managed infra in the estate; left unassigned rather than handed to an unattended profile

Jobs (declared job types)

No job types declared.

MCP requirements

  • VercelreadDeclared, not wiredget_deployment · get_runtime_logs · list_deployments

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
trigger a deploy, promote, rollback or alias change without an approval token (Vercel writes are gated)

Inputs (reads)

  • build_request
  • backend_code_change
  • deploy_readiness_note

Outputs (produces)

  • container_config_draft
  • ci_config_draft
  • deploy_readiness_note

Routing

Escalates to
engineering.orchestrator
Hands off to
engineering.agent_6engineering.orchestrator

Approval policy

Scoped write — may write, but only inside a defined boundary

Idle missions

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