01 · Stages 1–3
Build the evidence base
Pin an approved brand profile, confirm the campaign brief and review the entities and evidence the campaign may use.
The EntityStacks campaign workflow
Twelve controlled stages keep evidence, editorial decisions, generation and publication connected. Each approval advances one exact version; changing an earlier decision sends dependent work back for review.
01 · Stages 1–3
Pin an approved brand profile, confirm the campaign brief and review the entities and evidence the campaign may use.
02 · Stages 4–7
Shape keyword intent, topical coverage, planned assets and contextual links. Every link carries an editorial reason.
03 · Stages 8–9
Authorize a specific OpenRouter or Bedrock model, generate one planned article at a time and edit the exact output before approval.
04 · Stages 10–12
Approve a publishing plan, verify public content and optionally authorize one to thirty daily drift checks.
Twelve reviewable stages
Confirm the target, audience, topic and constraints.
Synthesize the approved brief and brand snapshot. This is not live web research.
Approve the brand facts and identity references for this campaign.
Review clusters, intent and sourced metrics. Leave unknown metrics unknown.
Define distinct topics and identify gaps in coverage.
Specify formats, page counts, destinations and organizational tier labels.
Define source → destination links with an editorial reason for each.
Generate scoped drafts using approved inputs and an authorized provider allowance.
Review exact asset versions, evidence and quality checks.
Approve a publication manifest before any external changes.
Verify reachability and links separately from index evidence.
Run checks within the authorized cadence, URL allowance and expiry.
Approval mechanics
Approvals are version-specific. Reopening research, entities or another upstream stage marks affected downstream work stale while retaining its history. Only one stage executes at a time for a campaign.
The review records the stage, version, reviewer and approved output.
A reasoned revision reopens the stage and marks later decisions for review.
BYOK jobs pin the selected OpenRouter or Bedrock connection, model and allowance.
Database functions and forced row-level security enforce workspace access.
An owner or admin chooses saved cloud accounts after content review is approved. EntityStacks shows planned public URLs and a signed-in preview before publication can be authorized. The first provider is included in the campaign credit cost; each extra provider costs five credits.
How to add each providerFetch every public article and compare its complete content hash with the approved upload. A human approves the verification results.
After verification, an owner or admin can authorize daily checks for one to thirty days. The schedule has an explicit allowance and expiry.
Reachability and content matching do not prove indexing or rankings. Live web research, managed campaign delivery and automatic backlink creation remain unavailable.
Create a brand profile, approve its source of truth, then open a campaign brief.
Create a workspace