Workflow & Statuses
State machine
Status meanings
| Status | Meaning | Gate to enter |
|---|---|---|
Discovered | Imported; no research | — |
Researched | Research folder and SERP evidence exist | scs research --check |
Selected | Human decision=go | decision fields set |
Briefed | Brief approved | scs brief --check + --approve |
Writing | Draft in progress | approved brief |
Editing | Human edit | article half written |
QA | Draft in WordPress, review pending | scs publish |
Scheduled | Review approved | scs qa check --advance |
Published | Live | publish transition |
Tracking | GSC data flowing | performance rows |
Refresh | Refresh in progress | review signal |
Consolidated / Pruned / Rejected | Terminal actions | human decision |
The three hard gates
| Gate | Requires |
|---|---|
| Research | research/<pid>/README.md + serp.md, 3 competitor URLs, no placeholders |
| Brief | decision=go, required sections non-empty, 3 competitor URLs, 2 source URLs, 4 - H2: outline lines, internal links row or none |
| QA | wpw_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.
| Tier | GOS | Use |
|---|---|---|
P1 | 70+ | High triage signal |
P2 | 50–69 | Worth reviewing |
P3 | 30–49 | Cluster or supporting candidate |
P4 | below 30 | Low triage signal |
n_sv = sv / max(sv for the site across all workspaces) * 100
n_kd = kd
gos = (n_sv * (100 - n_kd)) / 100
| Field | Values |
|---|---|
decision | go, hold, no |
decision_factors | competition, knowledge, experience, eeat, business_value, cluster_gap, existing_page, effort |
decided_by / decided_on | Person / 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.