Content Generation (Phase 3)

Goal: produce an accurate, useful draft that fulfils the approved brief and helps the intended reader complete their task. Metadata supports publishing; it does not substitute for editorial quality.

Where the article lives

The brief and the article are one file:

data/<workspace>/md/<pid>--<slug>.md

Example:

data/fundamentalstock/md/FS-9001--what-is-a-balance-sheet-a-beginner-s-guide.md

The file has three parts:

1. YAML front matter (regenerated from the CSVs by scs brief / scs sync);
2. the brief half between <!-- scs:brief --> and <!-- scs:article -->;
3. the article half after <!-- scs:article -->.

---
title: "What Is a Balance Sheet? A Beginner's Guide"
description: null
category: "Investing"
tags:
  - "balance sheet"
  - "financial statements"
content_type: "reference"
status: "Draft"
date: null
slug: null

scs:
  schema: scs-content/v3
  identity:
    pid: "FS-9001"
    site_id: "fundamentalstock"
  writing:
    audience: "Beginner investors"
    intent: "Informational"
    primary_keyword: "what is a balance sheet"
    supporting_keywords: []
    angle: "Explain the statement as a snapshot"
    differentiation: "Explain it as a connected snapshot"
    target_words: 2200
    tone: "Educational"
    author_role: "Practitioner"
    entities_to_cover:
      - "assets"
      - "liabilities"
      - "equity"
    questions_to_answer: []
  links:
    internal: []
  editorial:
    reviewer: "Sample reviewer"
    review_due: "2026-10-30"
    disclosure: null
  research:
    path: "data/fundamentalstock/research/FS-9001/"
    status: "needs_review"
---

<!-- scs:brief -->
## 1. Decision
...

<!-- scs:article -->
# What Is a Balance Sheet? A Beginner's Guide

...

note

content_type in front matter is the article format (reference, checklist, comparison, …). The WordPress ACF content_type (hub / pillar / cluster / supporting) comes from clusters.kc_type and is never read from front matter. See WordPress Contract.

Marker contract

Marker	Meaning
<!-- scs:brief -->	Start of the brief half
<!-- scs:article -->	Start of the article half

• scs brief --check validates the brief half only.
• scs publish sends the article half only.
• Files without markers keep working: the whole body is treated as the article for publishing, and as the brief for checks.

Model selection

Model	Best for	Notes
deepseek-v4.1-flash	Standard posts, supporting content	Fast, cost-effective
deepseek-v4-pro	Pillar pages, flagship guides	Deeper reasoning

Generation runs through opencode: pass the structured prompt to the selected model and save the result into the article half.

Generation modes

Mode	When	Method
Single prompt	A focused article the model can handle coherently	One prompt with the brief, evidence, and constraints
Section-by-section	A long or complex article that benefits from staged review	Generate sections with the full brief and context; check consistency across sections

Prompt shape

Help {audience} accomplish {reader_task} by writing a {content_type} about
"{keyword}". Use the approved angle: {hook_angle}.

READER AND SCOPE
- Answer the main question or task directly.
- Follow the approved outline where it serves the reader; do not add headings
  merely to hit a count.
- Cover {scope}; do not cover {excluded_scope}.
- Include questions only when their answers add value not already present.

EVIDENCE AND DISTINCTIVE VALUE
- Use the supplied research and sources; do not invent facts or citations.
- Include this site-specific evidence or experience: {distinctive_contribution}.
- If evidence is missing or a claim is uncertain, flag it for the editor instead
  of guessing.

REFERENCE TERMS — optional; use only when accurate and natural:
{reference_terms_with_ranges}

EDITORIAL CONSTRAINTS
- Do not invent statistics, sources, quotes, credentials, or first-hand experience.
- Use clear language appropriate for {audience_experience}.
- Use the supplied entities only where relevant: {entities_to_cover}.
- Length is guided by scope and evidence, not a quota{optional_word_guidance}.
- Include the intended next step where appropriate: {cta}.

Quality control

warning

AI-generated content must be reviewed by a person before publishing. Check that it answers the reader's task, follows the evidence, distinguishes facts from recommendations, and delivers the brief's stated contribution. Verify important claims against sources; assess citations, scope, and risk; remove unsupported claims and generic filler. Natural keyword use is a clarity check, not a target to maximize. See Quality & E-E-A-T.

After generation

scs sync --workspace bs        # refresh front matter, keep the body
scs check --workspace bs       # gates and references
scs publish --workspace bs --pid FS-0001 --dry-run
scs publish --workspace bs --pid FS-0001

Next: Quality & E-E-A-T or Publishing Workflow.