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

Orchestrator

Route platform/backend build work to one engineering specialist at a time inside hard repo boundaries, and gate every deploy, migration and external write behind approval.

Orchestrator

Not connectedIdle — nothing queued

Engineering orchestrator (beyond-spec sector) · Engineering (not in the ELISA spec)

engineering.orchestrator

Profile charter name: Nirmiti — 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-orch
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
Yes
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)

Route platform/backend build work to one engineering specialist at a time inside hard repo boundaries, and gate every deploy, migration and external write behind approval.

Will not (declared, and enforced at the gate)

  • write into C:/elisa/engine/** (binding fleet lesson L-0001) or C:/elisa/ui/** (binding fleet lesson L-0002)
  • authorize a deploy, a production migration, or an external write without an approval token
  • assign the same skill to two engineering specialists, or assign any skill already scoped to engineering.frontend

Owns (record types)

  • engineering_work_package
  • engineering_queue_state
  • engineering_sector_result

Skills (declared)

No skills declared.

Skills deliberately withheld

  • software-development — owned by engineering.agent_6; the orchestrator routes, it does not build
  • react-expert — owned by engineering.frontend (Darshini); front-end/UI craft is a separate agent and the UI tree is off-limits to this sector

Jobs (declared job types)

No job types declared.

MCP requirements

  • microsoft-learnreadDeclared, not wiredmicrosoft_docs_search

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
write into C:/elisa/engine/** (binding fleet lesson L-0001) or C:/elisa/ui/** (binding fleet lesson L-0002)

Inputs (reads)

  • engineering_work_package
  • build_request
  • security_review_request

Outputs (produces)

  • engineering_work_package
  • engineering_sector_result

Routing

Escalates to
elisa.root
Hands off to
engineering.agent_1engineering.agent_2engineering.agent_3engineering.agent_4engineering.agent_5engineering.agent_6

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.