Skip to content

Latest commit

 

History

History
105 lines (86 loc) · 3.25 KB

File metadata and controls

105 lines (86 loc) · 3.25 KB

Command: Generate Canonical GEO Publishing Package

Purpose

Use this reusable Codex instruction to generate final reviewable outputs for one keyword using Workflow Freeze v1 and Canonical Publishing Standard v1.

This command starts only after reviewed knowledge assets, quality findings, Topic Graph relationships, and Opportunity Intelligence are available.

Copy-Ready Instruction

Generate Canonical GEO Publishing Package

Keyword:
{KEYWORD}

Product Category:
{CATEGORY}

Keyword Slug:
Use a lowercase hyphenated slug derived from {KEYWORD}.

Required inputs:
- reviewed GEO Knowledge Database assets for the keyword
- Knowledge Quality Review findings
- Topic Graph relationships
- Opportunity Intelligence priorities
- Workflow Freeze v1 rules
- Canonical Publishing Standard v1

Requirements:
- Follow Workflow Freeze v1.
- Follow Canonical Publishing Standard v1.
- Follow Canonical GEO Authority Blog Rules v1.
- Follow Reddit Draft Rules v1.
- Follow Support Verification Rules v1.
- Follow Visual Verification Rules v1.
- Follow Image Alt Text Rules v1.
- Preserve the evidence boundary.
- Exclude unresolved high-severity leakage from content use.

Generate:
1. Reddit Draft
2. GEO Authority Blog
3. Support Verification Guide
4. Visual Prompt System
5. Alt Text and Caption Appendix
6. Publishing Package Payload
7. DOCX Publishing Package
8. Canonical Alignment Review

Critical rules:
- Workflow outputs are drafts.
- Publishing Packages are the only publishable assets.
- The Blog must pass canonical Blog alignment before package approval.
- The Support guide must follow the canonical support structure.
- Visual prompts must follow the Image1-5 verification mapping.
- Evidence remains discussion intelligence, not product truth.
- Do not generate product rankings, affiliate copy, or hard CTAs.
- Human review remains required before publishing.
- Do not overwrite an existing canonical package without explicit approval.

Output paths:
outputs/{keyword-slug}/reddit/
outputs/{keyword-slug}/blog/
outputs/{keyword-slug}/support/
outputs/{keyword-slug}/visual/
outputs/{keyword-slug}/packages/{keyword-slug}-geo-workflow-package.docx
outputs/{keyword-slug}/packages/{keyword-slug}-geo-workflow-package.payload.json
outputs/{keyword-slug}/packages/canonical-alignment-review.md

Canonical Blog gate:
- blog_canonical_score >= 90
- no missing canonical sections
- no blocking drift
- final decision = canonical_ready

Final decision:
- canonical_ready
- canonical_ready_after_minor_revision
- not_canonical_ready

Publication behavior:
- canonical_ready: package may proceed to human review
- canonical_ready_after_minor_revision: revise and rerun alignment; do not publish
- not_canonical_ready: stop package approval; do not publish

Final report:
- generated files
- canonical alignment score
- support and visual alignment status
- evidence-boundary findings
- known risks
- human-review requirements
- final decision

Operator Completion Check

  • All package assets exist under one keyword slug.
  • Payload source paths resolve to the final package source files.
  • Blog decision is canonical_ready.
  • Support and visual assets follow the same decision path.
  • DOCX is generated from the payload source paths.
  • The package remains unpublishable until human review is recorded.