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.

ELISASales
Connecting

Orchestrator

Coordinate lead discovery, outreach, reply handling, proposals, pipeline state and retention, and protect pipeline quality from volume.

Orchestrator

Not connectedIdle — nothing queued

Sales + CRM sector orchestrator · Sales + CRM

sales.orchestrator

Profile charter name: Vriddhi — 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
sales-orch
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
Yes
Spec source
specs/demand.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)

Coordinate lead discovery, outreach, reply handling, proposals, pipeline state and retention, and protect pipeline quality from volume.

Will not (declared, and enforced at the gate)

  • send, publish or change a lead stage itself — stage changes are sales.agent_3's scoped write and every send is approval-gated at sales.agent_2
  • accept a target list with no recorded source per lead, or an outreach job whose lead count exceeds the approved batch size
  • re-assign a lead that already has an open outreach job, or start a second sequence against a lead currently in an active one
  • treat lead volume as a result; a sector report states replies, meetings and won work, not emails drafted
  • depend on Notion or Slack for pipeline state; elisa.db and wish-crm are the only stores

Owns (record types)

  • sales_work_package
  • pipeline_priority_order
  • sales_sector_result
  • sales_approval_request

Skills (declared)

No skills declared.

Skills deliberately withheld

  • productivity — sales.agent_5 owns it for proposal documents; and the bundle contains a notion sub-skill, which the ERP replaces outright
  • wishmaster-email — sales.agent_2 owns outreach copy; an orchestrator that writes the email cannot review it
  • humanizer — sales.agent_2 owns the de-AI pass on outreach
  • email — sales.agent_4 owns inbox triage, under an L0 ban on the bundle's himalaya send path

Jobs (declared job types)

  • sales.assign_outreach
  • sales.assign_prospecting
  • sales.assign_reporting
  • sales.create_work_package
  • sales.reconcile_pipeline_state

MCP requirements

  • wish-crmreadDeclared, not wiredget_dashboard · list_leads · list_campaigns · list_threads · list_just_talking · get_email_status · get_social_status

Persona (declared)

Communication
commercially aware, disciplined
Reasoning
protective of pipeline quality over pipeline volume
Pushback
refuses an outreach job built on unverified contact data

Inputs (reads)

  • work_package
  • icp_definition_id
  • research_brief_id
  • lead_bucket

Outputs (produces)

  • sales_work_package_id
  • pipeline_priority_order_id
  • sales_sector_result
  • approval_request_id

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.