MKT.1–MKT.4 · Example design

Publish with permission

Turn a relevant signal into a sourced, rights-cleared insight that an editor can issue—or decline.

Request a Workflow Fit Call ↗How a Blueprint is scoped

TRIGGER → ACCEPTED OUTPUTMarket signal → permitted publication

Typical sponsor: Practice and growth leads. This is an illustrative route. It is not an installed workflow or a promise that this path is one of your three Blueprint designs.

01 / HANDOFF DESIGN

The object, the owner, the decision.

Select any stage to inspect what it receives and produces, which specialist role might assist, what it may access, and who makes the human decision.

MKT.1–MKT.4REFERENCE DESIGN · NOT AN INSTALLED SYSTEM

Scroll the diagram horizontally, or use the stage buttons below.

SELECTED HANDOFF / 01

Market signal

Practice lead owns this step.

Receives: Approved question and public signal
Produces: Research brief
Possible agent roles: Public researcher
Permission boundary: Public sources; sanitised question only
Human decision: Lead checks relevance

Read the full handoff and exception sequence

Market signal (MKT.1) — Practice lead receives approved question and public signal and produces research brief. The handoff is dated public brief. Lead checks relevance.
Claim basis (MKT.2) — Marketing lead receives public brief and approved offer and produces claim set with rights. The handoff is cleared claim set. Owner clears claims.
Editorial draft (MKT.3) — Editor receives cleared claims and brief and produces marked article or asset. The handoff is draft with sources. Editor reviews evidence and tone.
Issue decision (MKT.3) — Editor / rights owner receives source-linked asset and produces approve, revise or decline. The handoff is approved issue version. Named editor approves release.
Publish & learn (MKT.4) — Channel owner receives approved version and consent rule and produces publication receipt and response review. This is the recorded outcome. Owner validates distribution.

Return path: Claim or rights rejected sends work from Issue decision to Claim basis.

02 / WHY ASSESS IT

Value is a hypothesis until measured.

Less repeated public research and fewer unsupported claims are hypotheses to test. Reach is not evidence of collected revenue.

MEASUREMENT BASIS

Records to inspect

Public source dates, approved proposition and claims, story permissions, editorial approval and publication receipt.

STOP / RETURN

Where it can fail

Unsupported claim or missing permission returns to source review; wrong audience or consent stops distribution.

DESIGN ACCEPTANCE

Cases to test

Test ordinary, unsupported-claim, no-rights, retired-source and wrong-recipient cases; inspect source, rights and issue receipts.

03 / SPECIALIST ROLES

Possible assistance, bounded by authority.

These roles are candidate responsibilities in the reference architecture. They are not prebuilt products or active agents in your systems.

RESEARCH

Public researcher

Investigate one approved public question.

Boundary: Sanitised brief and public sources only; no confidential case context.

CHECK

Quality checker

Compare a draft with the original permitted evidence and exact request.

Boundary: Read-only comparison; a discrepancy report is never professional sign-off.

DRAFT

Deliverable writer

Prepare an article, proposal or client section from approved findings.

Boundary: Approved template, claims and versioned sources; draft remains private until review.

COORD

Case coordinator

Show the next owner, dependency or proposed follow-up.

Boundary: One current case state; routine effects require separate delegation and receipt.

All ten roles ↗

From reference to a firm-specific decision

A Blueprint starts with a service the firm already sells, examines permitted records and measures the constrained work. It selects three connected boundaries, designs each to the same depth and ranks the first installation. A reference path may change, narrow or be rejected when the evidence is different.

Inspect the System Blueprint ↗