Components

Three scheduled tasks (local cron, Claude Code agents) + Notion as state store + Telegram as notification channel.

• anichess-morning-commander — daily 8:27 AM, read-only briefing
• anichess-monday-content-flow — Mondays 9:33 AM, weekly content production
• anichess-feedback-processor — 11:03 + 17:03 daily, rewrites and learning extraction, Sunday 17:00+ wrap-up

State stores

Notion Campaigns DB (collection://9b7fb4ad-d20f-4ee9-845f-99e5bf351253)

• One row per week. Properties: Week focus, Key events, Session notes, Active channels, Status (Planning/Active/Done).
• Serves as the weekly intake contract between me and Monday Machine.

Notion Posts DB (collection://be05f3e9-0d8e-4954-9101-4f3f158028de)

• One row per post. Properties: Post name, Date, Channel, Post type, Content pillar, Status, Copy approved, Copy score, Visual brief, Campaign (relation), Notes, Final copy, Asset link, Published URL.
• Status ladder: Idea → Draft → Needs Rework → Ready → Scheduled → Posted. Additional terminal states: Discarded, Needs Rescheduling.
• Page body holds the copy itself in ## Copy / ## Visual direction / ## Comment sections.

Local context files (read by Monday Machine + Feedback Processor on every run, paths under CC Anichess Marketing/v2/):

• memory/ac-product-learnings.md — product facts, no-fabricate source
• memory/ac-content-learnings.md — style rules + correction patterns + silent-edit patterns (appended over time)
• memory/ac-audience-learnings.md — engagement hierarchy for narrative prioritization
• filler-bank/filler-bank.md — reusable filler content per channel
• .claude/rules/content-rules.md — banned words/patterns
• .claude/rules/golden-examples.md — approved copy references