akshay-na/generate-content-pipeline

generate-content-pipeline

Default linear stages

| Stage | Owner | Notes | |-------|--------|------| | git_sync | content-lead / shell | fetch + pull; must run before cco if session starts here | | plan | cco | Writes plan v0 + post–v0 edit round; editorial-cro-loop mandatory at execution intent before generate_content (unless documented override) | | generate_content | content-lead + project agents | Touches drafts per touches[] | | git_commit_push | content-lead | content-git-workflow |

Correction run

Payload: correction_brief, target_paths[], same task_id lineage. Re-run git_sync → surgical edits → git_commit_push.

Stage output contract

• generate_content automation output must emit canonical content-post-artifact-v1.
• Required routing anchors: post.post_id, post.version, post.channel, content.text, paths.workspace_root, paths.manifest_path, paths.audit_log_path, and media[].

Correction execution behavior

• Correction is a separate versioned workflow run, not a repeat-generation loop in the same execution.
• Use same post_id, increment version by 1, and set correction_of to previous version.
• Enqueue correction idempotently (dedupe key includes post_id, next version, and feedback hash); on enqueue failure use dead-letter/manual escalation.
• Rejection loop is bounded to two retries; third rejection must stop and route to dead-letter/manual intervention.
• On second rejection loop, force cross-topic fallback before regenerating content.

Stage and publish schedules

• Keep manual trigger path available and define schedule intents for daily stage + every-2-days publish.
• Schedule-triggered publish must auto-trigger stage first when no approved staged artifact exists.
• Trend analysis artifacts are reusable only within the same UTC day; draft and publish paths must share this cache key.

Pipeline files

YAML under configurations/pipelines/*.yml names stages and allowed globs. skill-validation may reference this skill from manifests.