Model LinkedIn conversations and professional context without hiding the gate

LinkedIn account access is decision-gated

The catalog describes a non-official account-session target, not an open LinkedIn developer product or a live DewEngine connector. No implementation or sale proceeds before the policy gate is approved.

• Catalog status and access: LinkedIn account products — decision gated, non official session
• Authentication: The intended account boundary is a session owned and explicitly connected by the user. Credential/session custody, reconnect behavior, and authorization are design targets only and require approval before implementation.
• Resources: chats, messages, profiles, companies, relations, invitations, posts, search, jobs
• Target actions: message.send, profile.get, company.get, relation.list, invitation.send, search.perform, post.create, job.manage
• Target events: message.received, message.sent, relation.accepted, account.status
• Limitations and failures: No connector or provider traffic exists; Reactions, read receipts, profile viewers, comments, and engagement events are not declared capabilities; Provider limits and authorization must be established before method design is final
• Release gates: LinkedIn account products — Qualified legal review and provider/product authorization are required before implementation or sale

Keep message history attached to the correct account

The target chat and message resources preserve provider conversation identifiers, participants, sender account, timestamps, and raw context. Sending remains a separate command whose acknowledgement and later event state are recorded independently.

Link profiles and companies without manufacturing identity

Profile, company, and relationship resources can give a CRM or ATS useful context. The application still owns contact matching and must retain provider IDs rather than treating a name, headline, or email inference as a guaranteed person match.

Make every state-changing action explicit

Search, invitations, messages, posts, and job actions have different inputs, limits, and consequences. Each target method needs an account-scoped permission, an idempotent command where applicable, and provider feedback that remains visible to the calling product.

Surface pacing, reconnect, and authorization state

A long-running account connector must stop safely when a session expires, the provider restricts an action, or the account requires user intervention. DewEngine should not turn those outcomes into a generic retry or a false success.

Keep workflow policy outside the connector

A CRM, ATS, or outreach product decides who may act, whether a human must approve, and when a sequence must stop. DewEngine's target role is to execute an authorized provider action and return evidence, not to invent outreach intent.