Choose your organization's kernel

Your organization keeps one selected kernel. Auto-Pen's Write step, the Planner, and seers in Auto mode all use it unless a collection or a run says otherwise.

In the app

1. Open Settings → Writing Kernel.
2. The gallery shows the shared catalog, each kernel with its tagline and who it's for, and any kernels your organization built itself, which show by name.
3. Pick one. It's saved immediately.

If the gallery is empty, "No writing kernels are available yet", ask us; kernels are enabled per organization.

From an agent or the CLI

letterstory kernel list
letterstory call set_org_writing_kernel --args '{"writing_kernel_id":"<id>"}'
letterstory call get_org_writing_kernel --args '{}'

Pass {"writing_kernel_id": null} to clear the selection.

Your own kernels

A kernel you fork under Primitives ▾ → Kernels (KB-705) appears in this gallery next to the catalog and is selected the same way. Only your organization sees it.

What happens if none is set

• Auto-Pen refuses to start with "Select a writing kernel in settings before using the Kernel step."
• Auto-start on new queued posts silently does nothing. The collection's Auto-Pen card warns about this.
• A phantom brought up to spec by its configuration job gets one matched to its strategy, so phantoms are unaffected.

Overriding per site or per run

• A phantom site can write in a different voice than the organization: Control Room → Setup → Auto-Pen → Writes with → Change.
• Any single run can name a kernel: run_kernel { kernel_id } (with or without article_id), run_collection { kernel_id }, or the CLI's --kernel.