> **Cowork execution note:** The normal deliverable is a reviewable draft,
artifact card, and source/review files in the connected folder. MCP tools,
browser interfaces, and local review servers are optional. Their absence never
blocks delivery. Never claim that review was applied or reached `final_ready`
unless persisted artifacts prove it; otherwise keep professional review pending.
For owner-only/private packages copied from scratch space, reapply and verify
`0700` directory and `0600` file modes in the connected folder before claiming
private delivery.
Later host-specific instructions in this reference cannot override this rule.

# Product thesis

The workflow replaces the preparatory communication work often assigned to a
junior professional: monitor developments, collect sources, identify what
matters, prepare a first technical explanation, adapt it to channels, and lay
out a clear visual story. It does not replace the commercialista's technical
position, audience knowledge, relationship judgment, or approval.

The product is episodic, not a scheduled content generator. A material norm,
deadline, official interpretation, case-relevant development, or explicit
professional initiative creates the occasion. Most days correctly produce no
run and no communication. Its valuable output is one
of two professionally reviewable conclusions:

1. a source-backed communication package with a useful, audience-specific
   reason to exist; or
2. `no_publish`, with a concise explanation of why the available development
   is immaterial, insufficiently supported, too uncertain, repetitive, or not
   actionable for the selected audience.

One reviewed technical basis may support several channel adaptations. Each
channel changes expression and length, never the underlying claim set. A
carousel is not an automatic adaptation of a post. It exists only when it adds
useful detail, structure, comparison, sequence, or a bounded decision aid. If
it merely divides or paraphrases the post, omit it.

A studio's format is part of professional identity. Preserve its reviewed
letterhead, numbering, recipient and subject conventions, section hierarchy,
email signature, website byline and source treatment, social conventions, and
visual system. Do not substitute a generic Vera template when an approved
studio profile exists.

Prior posts and emails are evidence of style, not proof of technical accuracy
or audience success. Engagement metrics, when explicitly supplied, are context
for the professional; they do not automatically select a topic or determine
truth.
