Citizen Analyst — Content Authoring
Editorial & Assessment

Citizen Analyst — Content Authoring

Skip to main content
Table of Contents
< All Topics
Print

Citizen Analyst — Content Authoring

Last updated: November 20, 2026

The codified loop for Phase 5 of CONTENT-WORKFLOW-REENGINEERING-PLAN.md. Local Markdown under agent-base/knowledgebase/ is the single source of truth; ca-publish (scripts/ca_publish.py) syncs it to WordPress. Never edit content on WordPress.

Run all commands from the citizen-analyst/ project root.

The loop

  1. Take the request — a new document, or an update to an existing one.
  2. Gather context — read the relevant existing KB docs and Skills; use

WebSearch / Tavily for current information. Cite sources with exact publication dates (see Publication Date Rule below).

  1. Write / update the .md:
  • New doc: make new-doc SLUG= for a schema-valid stub, then write.
  • Frontmatter: title, category (a leaf in docs/category-taxonomy.yaml),

meta_description (80–160 chars), tags; bump last_updated.

  • In-body cross-references use [[slug]] / [[slug|text]]

(docs/linking-convention.md) — never relative .md links.

  1. Backlink pass (new docs) — make backlinks SLUG=; propose

[[slug]] insertions into the surfaced documents; let Peter approve.

  1. Reciprocate + validate — python3 scripts/sync_related.py --apply,

then make validate and python3 scripts/lib/linkgraph.py --report.

  1. Guardrail checks — apply the Cursor Rules: patriot-accountability-profile-standards.mdc

(evidence tiers, prohibited words, citations, factcheck notice) for accountability profiles; patriot-zero-pii.mdc; patriot-investigative.mdc (provenance tags, cross-reference discipline) for investigative content.

  1. Propagate — make sync-derived (counts/indexes); if a skill changed,

python3 scripts/sync_skills.py.

  1. Commit — git commit; keep knowledge-sync commits separate from code.
  2. Stage — make publish-staging → the article appears as a WordPress draft.

9b. (Optional) Embed timeline or infographic — If the document benefits from a visual timeline or infographic, use the Pipeline Editor sidebar panels to generate them. Place ` or ` markers in the body to control position. If no marker is present, assets append at the end. See docs/EDITORS-MANUAL.md §8 for the full workflow. 9c. Update the master timeline repository — For any document that contains dated events (accountability profiles, voting guides, legal analyses, etc.), update the local timeline repository:


    make timeline-extract SLUG=<slug>

This extracts events with Claude and writes them to agent-base/timeline-repository/events/{slug}.json. The extractor skips documents whose content hash has not changed, so this is safe to run after any edit. Use make timeline-extract-changed at the end of batch sessions to process all modified documents at once. See .claude/skills/master-timeline/SKILL.md for the full workflow.

  1. Publish — Peter reviews the draft on citizenanalyst.ai; on approval,

set status: published and make publish. The cascade pass resolves inbound links automatically.

Publication Date Rule

Every web source cited in a KB document — whether inline Source link:, Fact-check source:, or in a Sources section — must include the exact publication date of the cited article or document (e.g., “March 14, 2025”).

When using WebSearch or Tavily, capture the published_date from each result. Vague references like “2025” or “recent report” are insufficient. If the publication date cannot be determined, note [publication date not available] rather than omitting it silently.

This is required for downstream timeline generation (Cool Timelines Pro), staleness audits, and establishing the temporal sequence of events.

Rules

  • Slugs are stable. Never change a published doc’s slug without a 301

(redirects.py).

  • Protected files — CLAUDE.md, .cursor/rules/*.mdc — are never auto-edited;

propose a [CONTEXT-UPDATE] instead.

  • A document with no live counterpart stays status: draft until reviewed

(see docs/draft-docs-review.md).

  • Oversized documents (>~8000 tokens) must be segmented before publishing —

ca-publish blocks them (embedding pre-flight).

Reference

docs/content-workflow.md — the human-facing workflow and full command list.

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?