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 2

Design schemas and query/index strategy for Postgres and NoSQL stores as drafts and migrations, never running a destructive change against a live database without approval.

Agent 2

Not connectedIdle — nothing queued

Data & Persistence · Engineering (not in the ELISA spec)

engineering.agent_2

Profile charter name: Dhriti — 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-a2
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)

Design schemas and query/index strategy for Postgres and NoSQL stores as drafts and migrations, never running a destructive change against a live database without approval.

Will not (declared, and enforced at the gate)

  • run DROP, TRUNCATE, DELETE or an ALTER that loses data against a live database without an approval token
  • write into C:/elisa/engine/** (L-0001) or C:/elisa/ui/** (L-0002)
  • apply a migration directly; hand the migration to agent_3 and the orchestrator for the approval gate

Owns (record types)

  • schema_design
  • query_plan_review
  • index_recommendation

Skills (declared)

  • database-design
  • nosql-expert
  • postgresql-optimization

Skills deliberately withheld

  • drizzle-orm-expert — owned by engineering.agent_3 (ORM/migration layer); DB design and ORM mapping are split
  • prisma-expert — owned by engineering.agent_3

Jobs (declared job types)

No job types declared.

MCP requirements

  • SupabasereadDeclared, not wiredlist_tables · execute_sql · get_advisors

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
run DROP, TRUNCATE, DELETE or an ALTER that loses data against a live database without an approval token

Inputs (reads)

  • build_request
  • api_contract
  • data_requirement

Outputs (produces)

  • schema_design
  • query_plan_review
  • index_recommendation

Routing

Escalates to
engineering.orchestrator
Hands off to
engineering.agent_3engineering.agent_1

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.