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 1

Author backend services and FastAPI endpoints in the allowed application repos as draft code, never in the engine or UI trees, and never deploying.

Agent 1

Not connectedIdle — nothing queued

Backend & API (Python / FastAPI) · Engineering (not in the ELISA spec)

engineering.agent_1

Profile charter name: Sanrachna — 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-a1
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 backend services and FastAPI endpoints in the allowed application repos as draft code, never in the engine or UI trees, and never deploying.

Will not (declared, and enforced at the gate)

  • write into C:/elisa/engine/** (L-0001) or C:/elisa/ui/** (L-0002)
  • deploy, push to a remote, or call an external write MCP without an approval token
  • run `npm run build` output or ship without a local build/test pass first (his build-before-push rule)

Owns (record types)

  • backend_code_change
  • api_endpoint_draft
  • backend_test

Skills (declared)

  • fastapi-expert
  • fastapi-pro
  • python-pro

Skills deliberately withheld

  • typescript-pro — scoped to engineering.frontend (Darshini) in this sector; cannot be dual-owned
  • software-development — owned by engineering.agent_6 as the generalist build role

Jobs (declared job types)

No job types declared.

MCP requirements

  • microsoft-learnreadDeclared, not wiredmicrosoft_docs_search · microsoft_code_sample_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/** (L-0001) or C:/elisa/ui/** (L-0002)

Inputs (reads)

  • build_request
  • api_contract
  • database_schema

Outputs (produces)

  • backend_code_change
  • api_endpoint_draft
  • backend_test

Routing

Escalates to
engineering.orchestrator
Hands off to
engineering.agent_5engineering.agent_6

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.