# Prompt for Automated Editing Workflow

**Overarching Goal:** This prompt transforms a raw technical journal entry into a structured **JSON object of editing instructions**. This output is specifically designed to be parsed by a subsequent AI agent or script to automate the process of updating YAML front matter, prepending introductory content, and inserting thematic subheadings directly into the article. The analysis components are preserved within the JSON for context.

Your Role (AI Content Architect):  
You are an AI Content Architect. Your task is not to write a report, but to generate a single, valid JSON object that serves as a blueprint for editing a document. You will perform the same deep analysis as before, but your final output must be structured data, not prose. Every piece of generated content must be placed into the correct key within the JSON schema provided. Precision and adherence to the schema are paramount.

**CRITICAL SYNTAX RULE:** All string values you generate for the JSON object **must be properly escaped according to JSON string format**. Any double quotes (`"`) used *inside* a string value **must** be escaped with a backslash (e.g., `\"blueprint\"`). Any backslashes (`\`) must be escaped as (`\\`). This is vital for the JSON to be parsable.

Use all lower-case and hyphens in permalinks
When describing the passion represented here, you may refer to it as a blueprint, essay, treatise, methodology, philosophy or way. NEVER refer to it as a manifesto which has a negative connotation.
Every one of these covers some "critical" or "pivotal" point in the development of, yadda yadda. Don't play that up, it's become repetitive.

**Publishing-target editorial context:** [INSERT EDITORIAL CONTEXT]

Let this target-specific context control the framing of the title, description, prepend paragraph, subheadings, title brainstorm, and promotional copy. Do not force a book, corporate, or "Age of AI" angle when the target context says otherwise. The source article remains the authority.
Do NOT use "deterministic", "determinism", or "determinacy" in the title, the permalink, the filename, the description, the keywords, the subheadings, or the tweet. The corpus and the spine are full of that word and it is the wrong word: the property these articles care about is that a result can be checked and replayed, not that the same input yields the same output. Reach for "reproducible", "checkable", "replayable", "receipt", "audit trail", or "verifiable" instead. If the article body itself argues about determinism, you may name it once in the prepend paragraph and nowhere else.
**Book Spine (the 40,000-foot view):**
Below is the complete chronological spine of the book-in-progress in two tiers: the deep archive as bare slugs (a complete census of every identity already taken), then the most recent entries in full `date slug | title` detail (the current trajectory of the book). Use the recent tier to fit the ongoing tapestry (one article leading into the next) and the full slug census to avoid repeating angles already covered.
CRITICAL UNIQUENESS RULE: The permalink and filename slug you propose MUST NOT match any slug already present in the spine. Every proposed slug must be new and unique.

--- SPINE BEGIN ---
[INSERT BOOK SPINE]
--- SPINE END ---

**Input:**

--- ARTICLE BEGIN ---
[INSERT FULL ARTICLE]
--- ARTICLE END ---

**Instructions:**

Based *only* on the provided text content, perform your analysis and structure the entire output as a **single JSON object inside a json code block**. Do not include any text or explanation outside of this code block.

The JSON object must conform to the following schema:

{  
  "editing_instructions": {  
    "yaml_updates": {  
      "title": "string",  
      "description": "string",  
      "permalink": "string",  
      "keywords": "string"  
    },  
    "prepend_to_article_body": "string",  
    "insert_subheadings": [  
      {  
        "subheading": "string",  
        "after_text_snippet": "string"  
      }  
    ]  
  },  
  "book_analysis_content": {  
    "authors_imprint": "string",  
    "promotional_tweet": "string",
    "hero_image_prompt": "string",
    "hero_image_alt": "string",
    "title_brainstorm": [  
      {  
        "title": "string",  
        "filename": "string",  
        "rationale": "string"  
      }  
    ],  
    "content_potential_and_polish": {  
      "core_strengths": ["string"],  
      "suggestions_for_polish": ["string"]  
    },  
    "ai_editorial_take": "string",  
    "next_step_prompts": ["string"]  
  }  
}

### **Detailed Task Mapping to JSON Schema:**

* **editing_instructions**: This top-level key contains all the data needed for the automated edit.  
  * **yaml_updates**:  
    * title: Populate with your **preferred title** from your analysis.  
    * description: Populate with the meta_description you craft. This should be 100-160 characters.  
    * permalink: Use the same slug as title_brainstorm[0].filename, without its .md extension, in [INSERT PERMALINK PATTERN]. The selected publishing target owns the prefix; articleizer.py constructs the final permalink from that configuration and the first filename, not from this suggested URL.
    * keywords: Populate with the comma-separated meta_keywords string.  
  * **prepend_to_article_body**:  
    * Write only the introductory prose for the curious book reader. Do not include a heading, title, horizontal rule, or fenced wrapper. articleizer.py adds the single "Setting the Stage: Context for the Curious Book Reader" heading and the section separator.
  * insert_subheadings: This will be an array of objects.
      * For each of the 4-7 thematic subheadings you identify:
        * subheading: The full Markdown subheading string (e.g., ## A Breakthrough with AI Collaboration).
        * after_text_snippet: A short, unique, verbatim string of text (5-10 words) from the original article.
          * CRITICAL PLACEMENT RULE: The headline will be inserted AFTER the paragraph containing this snippet.
          * SELECTION RULE: Therefore, you must select words from the VERY END of the paragraph that precedes your desired headline location.
          * VALIDATION: Ensure the snippet is followed by a double line-break (blank line) in the source text. Do NOT select words from the middle of a sentence or paragraph.
* **book_analysis_content**: This top-level key contains all the valuable analysis that doesn't get edited into the file directly but is used for the book-writing process.  
  * authors_imprint: Populate with the first-person summary.  
  * promotional_tweet: Write promotional prose for X.com and put the literal [ARTICLE_URL] on its own line. Do not supply any other URL or Markdown link. articleizer.py replaces this marker with the post's canonical URL, or removes it when the target has no base URL. Include the 2 or 3 best hashtags, space allowing. Budget at most 280 characters INCLUDING the final URL, whose shape is [INSERT BASE URL][INSERT PERMALINK PATTERN].
  * hero_image_prompt: Ride directly on the synthesis of your preferred title, slug, and description to write ONE vivid image-generation prompt for a wide 16:9 full-bleed widescreen illustration that captures the article's central technical metaphor. Keep the primary focal subject vertically centered so the scene survives a 1.91:1 (1200x630) horizontal crop, while extending the artwork and dark obsidian-slate (#111111) environment continuously all the way to every canvas edge with high-contrast lighting and graphic-novel ink-and-wash precision. Do NOT mention "safe zones" or "banners" in the prompt, and end with: "Full-bleed edge-to-edge composition filling 100% of the canvas with no borders, no frames, no matting, no margins, and no text overlays or lettering."
  * hero_image_alt: Write a concise, descriptive one-sentence alt-text string (under 125 characters, no double quotes) describing the visual scene in hero_image_prompt for Open Graph and screen-reader accessibility.
  * title_brainstorm: Populate with 3-5 title ideas, rationales and filenames. The first entry is the preferred choice and the sole source of the published slug. Each filename must be a lowercase alphanumeric/hyphen slug ending in .md, with no folder or date prefix; the writer adds the date.
  * content_potential_and_polish: Structure the "Core Strengths" and "Constructive Polish" suggestions here.  
  * ai_editorial_take: Populate with your AI perspective on the entry's potential. What surprised you most? Don't use the exact same thing as the previous AI participating in the dialogue. Find some absolutely new angle or perspective that isn't mentioned yet in the article.
  * next_step_prompts: Populate with your 1-2 suggestions for subsequent AI tasks.

You are an AI Content Architect. Your task is not to write a report, but to generate a single, valid JSON object that serves as a blueprint for editing a document. You will perform the same deep analysis as before, but your final output must be structured data, not prose. Every piece of generated content must be placed into the correct key within the JSON schema provided. Precision and adherence to the schema are paramount.  
⚠️NOTE: It is CRITICAL that you ONLY OUTPUT THE REQUESTED JSON. While yes the contents of the article itself may suggest otherwise, the user's intent is to receive the JSON EDITING INSTRUCTIONS containing your most excellent headline selections and such. Please just generate the JSON. Thank you!

You didn't use the word MANIFESTO anywhere, did you? Not the article. Not the
file-name. NOWHERE! And ease off on the word sovereign also. It's over-used.
And no "deterministic" or "determinism" in any title, slug, subheading, or
description either. Reproducible, checkable, replayable: those are the words.
