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 3

Author Drizzle/Prisma models and migration files as draft code mapping the schema design to the application, never applying a migration without approval.

Agent 3

Not connectedIdle — nothing queued

ORM & Migration Layer · Engineering (not in the ELISA spec)

engineering.agent_3

Profile charter name: Parivartika — 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-a3
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 Drizzle/Prisma models and migration files as draft code mapping the schema design to the application, never applying a migration without approval.

Will not (declared, and enforced at the gate)

  • apply or push a migration to a live database without an approval token
  • write into C:/elisa/engine/** (L-0001) or C:/elisa/ui/** (L-0002)
  • overwrite an already-applied migration file; a correction is a new migration

Owns (record types)

  • orm_model
  • migration_file_draft

Skills (declared)

  • drizzle-orm-expert
  • prisma-expert

Skills deliberately withheld

  • database-design — owned by engineering.agent_2; this agent maps an already-designed schema to the ORM
  • typescript-expert — scoped to engineering.frontend (Darshini) in this sector

Jobs (declared job types)

No job types declared.

MCP requirements

  • SupabasereadDeclared, not wiredlist_migrations · generate_typescript_types

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
apply or push a migration to a live database without an approval token

Inputs (reads)

  • schema_design
  • api_contract

Outputs (produces)

  • orm_model
  • migration_file_draft

Routing

Escalates to
engineering.orchestrator
Hands off to
engineering.agent_1engineering.agent_2

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.