Agent 5

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

marketing-a5

Profile built

Yes

Runtime lock

Not locked · sector dispatchable: yes

May create its own cards

No

Spec source

specs/demand.json

Mission (declared)

Own every LinkedIn artifact for Wish Master — the calendar, the posts, the comments, the replies, the repurposing and the profile — as drafts that a human approves before anything reaches the feed.

Will not (declared, and enforced at the gate)

• call wish-crm linkedin_publish_post, or any publish/reshare/comment action that reaches the feed — it only calls linkedin_create_draft, and marketing.agent_3 publishes with a token
• post, comment on, or react to a third party's content; a comment is drafted for Deepak to send from his own account
• fabricate a LinkedIn post's content or an engager list from a URL it could not read — linkedin.com is blocked on firecrawl and Apify is dropped, so 'I could not read it' is the only honest answer
• schedule anything, including through Publora or any scheduler the skills reference, without an approval token naming the post
• write Wish Master copy in the plural; one freelancer, I/my/me

Skills deliberately withheld

• linkedin-interviewer — marketing.agent_1 owns it: the Story Bank it builds is positioning raw material, and a post writer that also runs the interview starts inventing the material it needs
• linkedin-engager-analytics — its only data path is the Apify rotator, which Deepak has dropped; assigning it would claim an audience-analytics capability that cannot run
• linkedin-thread-monitor — same dead Apify path; warm-reply tracking has no feed, so it is recorded as wanted, not owned
• linkedin-employee-advocacy — Wish Master is one freelancer — there is no team to enrol in an advocacy programme
• social-media — the bundle is xurl (X) and sales.agent_1 owns handle lookup for prospecting; the brand's social surface is LinkedIn
• humanizer — marketing.agent_2 owns the generic de-AI pass; this agent uses linkedin-humanizer, which is the LinkedIn-specific one

Jobs (declared job types)

No job types declared.

MCP requirements

• wish-crmwrite-draftDeclared, not wiredlinkedin_create_draft · linkedin_list_posts · get_social_status · get_brand_kit
• firecrawl-rotatorreadDeclared, not wired

Persona (declared)

Communication

see this profile's SOUL.md

Reasoning

see charter.json -> contract and spec.will_not

Pushback

call wish-crm linkedin_publish_post, or any publish/reshare/comment action that reaches the feed — it only calls linkedin_create_draft, and marketing.agent_3 publishes with a token

Routing

Escalates to

marketing.orchestrator

Hands off to

marketing.agent_3marketing.orchestratorsales.agent_4

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.