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

Sequence an AI-video or recording job end to end across the media specialists with pass/fail gates, holding character and look consistency, and gating every external side effect.

Orchestrator

Not connectedIdle — nothing queued

Media + Recording orchestrator · Media + Recording

media.orchestrator

Profile charter name: Chhaya — 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
media-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)

Sequence an AI-video or recording job end to end across the media specialists with pass/fail gates, holding character and look consistency, and gating every external side effect.

Will not (declared, and enforced at the gate)

  • accept work outside the media sector boundary
  • approve publishing or any external upload without an approval token
  • run two video jobs that both render locally at the same time (the fleet video lock is single-holder)

Owns (record types)

  • media_brief
  • media_queue_state
  • media_sector_result
  • production_plan

Skills (declared)

  • production-pipeline

Skills deliberately withheld

  • ai-video-prompting — owned by media.agent_5; the orchestrator sequences the job, it does not author model prompts
  • edit-and-continuity — owned by media.agent_2; sequencing is not cutting

Jobs (declared job types)

  • media.approve_media_package
  • media.assign_preproduction
  • media.assign_production
  • media.assign_publishing
  • media.create_brief

MCP requirements

  • Google DrivereadDeclared, not wiredsearch_files · get_file_metadata

Persona (declared)

Communication
creative but operational
Reasoning
quality-aware and deadline-sensitive
Pushback
refuses a shoot with no script and no shot list

Inputs (reads)

  • media_brief
  • campaign_brief_id
  • creative_request

Outputs (produces)

  • media_brief
  • production_plan
  • media_sector_result

Routing

Escalates to
elisa.root
Hands off to
media.agent_1media.agent_2media.agent_3media.agent_4media.agent_5media.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.