Last updated: 2026-07-07 07:39 EDT

Status: official live workspace skill. Proposal kron-evolution-20260707-19221a7e9d was applied through Skill Workshop, and skills/kron-evolution/SKILL.md now contains the revised artifact-evaluation workflow.

---
name: "kron-evolution"
description: "Create Kron iterations with isolated artifacts and evaluation."
---

# Kron Evolution

Use this skill to create the next Kron Evolution Workshop iteration. The skill turns the loop forward by evaluating the previous iteration's isolated public-facing artifact, choosing one lesson, generating one new artifact, updating the public ledger, and maintaining the concise lesson archive without touching live cron jobs unless Christopher explicitly asks.

## Core Rule

Each iteration evaluates the previous iteration, not itself. Do not include a `Next Evaluation Target`, self-evaluation, or forward-looking target section inside the current iteration. The current turn should evaluate the prior turn, implement one change or sidestep, record the output, and stop.

Human input is part of the loop. When Christopher gives a correction, preference, or critique since the prior iteration, treat that as the primary evaluation signal and preserve it in the next evaluation and change record.

## Artifact Boundary

The public-facing artifact is a self-contained bundle:

- Intended idea: the idea the iteration tried to represent;
- Image: the visual attempt to communicate the idea;
- Accompanying text: the saying, quote, caption, parable, or post-length text paired with the image.

The artifact should be able to stand on its own for an outside person. The image should present the intended idea without needing the ledger for context. The text should resonate with the image and clarify or deepen the same idea, not explain the workflow that produced it.

Keep evaluation, metadata, audit notes, lesson archives, and output records outside the artifact.

## Evaluation Stance

Do not assume every iteration must identify a failure. Evaluate whether the previous artifact coherently conveyed its intended idea.

An evaluation may conclude:

- the artifact failed or drifted, so the next iteration corrects course;
- the artifact mostly worked, so the next iteration preserves the lesson and sidesteps toward a new idea;
- the image and text aligned, but the next iteration should aim for more depth, emotional resonance, legibility, or engagement.

## Page Structure

On the public iteration ledger page:

- Keep the lesson archive self-contained in a collapsed dropdown by default.
- Keep iteration entries newest-first.
- Inside each new iteration entry, include an isolated Artifact Under Evaluation or New Artifact block containing intended idea, accompanying text, image, and image path.
- Keep evaluation, rubric, explanation, metadata, and output record outside that artifact block.

## Safety Boundaries

- Do not modify legacy-active Bluesky or YouTube cron jobs.
- Do not create, edit, enable, or schedule cron jobs unless Christopher explicitly requests that step.
- Do not post publicly unless Christopher explicitly approves publication.
- Keep the first output path inside the Workshop unless told otherwise.
- Make every run visible: record what was evaluated, what changed, what was created, and what safety boundaries stayed closed.