Content Package
This is the standard preparation lane for researched content. It keeps evidence, writing, packaging, and external delivery distinct so an operator can inspect one concrete artifact and no local success is mistaken for publication.
Use it for articles, updates, newsletters, explainers, and other channel-bound content whose substantive claims need traceable support. The result should do something for the reader—clarify a decision, explain a change, establish trust, or enable a concrete next step—not merely prove that research happened.
Composes
ghostwrite#draftghostwrite#handoffghostwrite#packageresearch#investigateresearch#research
How the chain works
- The default
preparerunner takes the objective, audience and channel, with optionalpaths,urlsor completedsource_packets.research#investigatereads explicit sources directly and acquires only missing evidence. Nonempty supplied source packets skip acquisition. The explicitcontent-packagerunner retains its bounded-source-only contract for existing graphs. researchadmits the sources, binds citations, and decides whether the evidence supports a useful deliverable. For a completedresearch_packet, selectfrom-researchto skip both acquisition and research synthesis.ghostwritedrafts only from the admitted claims and digests, applying any supplied voice or operator context without treating it as factual evidence.- The validated draft is packaged deterministically for the declared channel.
- When a nonempty
publication_targetis supplied, a provider-neutral handoff records that target and the later approval requirement. Without a target, the prepared content remains available and no ready handoff is invented. Both paths stop before external delivery.
Local research, drafting, and packaging require no approval. A later provider skill owns the consequential gate, idempotency, send or publish request, acknowledgement, and readback.
Inputs and result
objectivestates what the content should change for its reader.pathsandurlsselect sources to read.source_packetsreuse completed governed reads;from-researchinstead accepts their completedresearch_packet.- Optional
brand_contextandtaste_contextretain their declared audience and channel scope through canonical writing admission. audience,channel, anddomainshape the artifact.operator_contextandtarget_entitiesnarrow interpretation but are not source evidence.publication_targetandboundary_kind(internalorexternal) prepare the next lane; they do not authorize it. An external delivery needs the delivering lane's own approval.
The result preserves the citation-validated research packet, the evidence-bound
draft, a deterministic channel package with not_sent state, and, when a target was supplied, a
provider-neutral handoff. needs_more_evidence, needs_review, and
not_worth_publishing are valid terminal states when the topic is unsupported,
stale, duplicative, or unhelpful.
Stop conditions
- Stop before drafting when the source packet is missing or invalid.
- Do not turn operator context, campaign intent, or a target URL into evidence.
- Withhold any draft whose material claim cannot be tied to an admitted digest.
- Do not add delivery or publication evidence to a local package.
- Route the exact accepted artifact into the relevant provider lane instead of rebuilding it there.
Example
An operator wants a blog post explaining a new governance boundary. The lane can validate official docs and receipt evidence, draft for engineering readers, package the accepted body for the blog, and prepare a CMS handoff. It cannot say the post is live until an approved CMS operation and provider readback prove it.