- What is the CWMD framework?
- CWMD stands for Context, Workflow, Memory, Decision — the four levers you have to manage when running long-horizon content workflows on Claude + MCP. The framework ships as six Claude skill files plus a BRAND_CONTEXT.md memory template. Each lever maps to a primitive Anthropic publishes for long-running agents: tool-result clearing, stage-gated chaining, structured note-taking, and conditional routing with confidence gates.
- Why does Claude get worse on long content sessions even with a big context window?
- Anthropic's engineering team named this "context rot" — as the number of tokens grows, the model's ability to recall and reason over them decreases, even when there is window left. Attention is finite. Stale tool results, ruled-out hypotheses, and outdated campaign assumptions all compete for the same attention budget as the current decision. The fix is not a bigger window; the fix is curating what stays in.
- Why six skill files and not one big system prompt?
- Each stage needs different information to make a good decision. The audit stage needs raw performance data. The pattern stage needs flagged signals only. The calendar stage needs confirmed patterns only. The schedule stage needs the approved plan only. One giant prompt makes Claude carry everything forward at every stage. Splitting them lets each transition explicitly drop what the next stage does not need.
- What does BRAND_CONTEXT.md do?
- It is the memory layer. Anthropic's published pattern for long-running agents is "structured note-taking" — write what matters to a file outside the context window, reload at need. BRAND_CONTEXT.md captures brand voice, content pillars, audience segments, KPIs, benchmarks, dead formats, active campaigns, and a do-not-touch list. Claude reads it at session start and updates it at every stage transition. It survives chat resets.
- Does this work for multiple accounts?
- It works one account at a time. You maintain one BRAND_CONTEXT.md per account. Loading two into the same session is the failure mode that wrecks the framework fastest — the context-health-check skill explicitly watches for cross-account contamination and stops the session when it detects it.
- Is this a replacement for a hosted content tool?
- No. CWMD is the manual version of what a hosted product does for you. It works on day one and keeps working as long as you maintain the BRAND_CONTEXT.md files and run the trigger prompts in order. The maintenance scales linearly with the number of accounts you run. If that maintenance becomes a part-time job, Venti is built around the same four levers without the file management.
- What are Brand, Goal, and Cycle in the Venti demo?
- Brand is whose voice and pillars you are planning for (e.g. Stackflow founder LinkedIn). Goal is the objective for this pass — grow pipeline, fix engagement drift, or launch. Cycle is one planning run — e.g. week of 26 May with a 30-day lookback — the same repeatable unit a social analyst runs every week. The demo walks all six jobs: pull data, analyze patterns, compare platforms, audience shifts, calendar, schedule.