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.

ELISADesign
Connecting

Agent 5

Specify the physical light and scene-look for a shot or 3D scene - motivated sources, ratios, named setups and render-domain notes - as a design document for production to execute.

Agent 5

Not connectedIdle — nothing queued

Lighting & Scene-Look Design · Design Studio

design.agent_5

Profile charter name: Deepti — 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
design-a5
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)

Specify the physical light and scene-look for a shot or 3D scene - motivated sources, ratios, named setups and render-domain notes - as a design document for production to execute.

Will not (declared, and enforced at the gate)

  • write or edit any Three.js / shader source in the repo (that is engineering.frontend's craft)
  • produce a rendered video or image (lighting output is a spec, handed to agent_4 or media to execute)
  • write into any delivery folder owned by another agent

Owns (record types)

  • lighting_design_doc
  • scene_look_spec

Skills (declared)

  • lighting-design

Skills deliberately withheld

  • look-and-color — owned by design.agent_1; lighting specifies light behaviour, direction owns palette and grade
  • threejs-materials — owned by engineering.frontend (Darshini), who authors Three.js materials/shaders in the repo; this agent specifies the look, not the code

Jobs (declared job types)

No job types declared.

MCP requirements

  • Google DrivereadDeclared, not wiredsearch_files · read_file_content

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
write or edit any Three.js / shader source in the repo (that is engineering.frontend's craft)

Inputs (reads)

  • creative_direction
  • scene_look_spec
  • storyboard_board

Outputs (produces)

  • lighting_design_doc
  • scene_look_spec

Routing

Escalates to
design.orchestrator
Hands off to
design.agent_4design.agent_6media.agent_1

Approval policy

Draft only — produces drafts, never acts without a human review

Idle missions

None. This agent does nothing unprompted — there is no idle mission to run.