Skip to main content

Workflow & Statuses

State machine​

Status meanings​

StatusMeaningGate to enter
DiscoveredImported; no research—
ResearchedResearch folder and SERP evidence existscs research --check
SelectedHuman decision=godecision fields set
BriefedBrief approvedscs brief --check + --approve
WritingDraft in progressapproved brief
EditingHuman editarticle half written
QADraft in WordPress, review pendingscs publish
ScheduledReview approvedscs qa check --advance
PublishedLivepublish transition
TrackingGSC data flowingperformance rows
RefreshRefresh in progressreview signal
Consolidated / Pruned / RejectedTerminal actionshuman decision

The three hard gates​

GateRequires
Researchresearch/<pid>/README.md + serp.md, 3 competitor URLs, no placeholders
Briefdecision=go, required sections non-empty, 3 competitor URLs, 2 source URLs, 4 - H2: outline lines, internal links row or none
QAwpw_review_status=approved, reviewer, date, checklist items; ymyl scope when required

scs check enforces status gates; a typo in status is a validation error.

Decision model​

gos_tier is a triage band, not a verdict.

TierGOSUse
P170+High triage signal
P250–69Worth reviewing
P330–49Cluster or supporting candidate
P4below 30Low triage signal
n_sv = sv / max(sv for the site across all workspaces) * 100
n_kd = kd
gos = (n_sv * (100 - n_kd)) / 100
FieldValues
decisiongo, hold, no
decision_factorscompetition, knowledge, experience, eeat, business_value, cluster_gap, existing_page, effort
decided_by / decided_onPerson / ISO date
important

A low-GOS keyword can be go for cluster coverage or business value. A high-GOS keyword can be no for competition, knowledge, or E-E-A-T reasons.

Manual by design​

  • The keyword decision.
  • The brief prose and differentiation angle.
  • The article draft.
  • The WordPress visual review.
  • The publishing-state decision.

SCS automates state, paths, front matter, validation, draft creation, and QA read-back. It does not automate judgement.