Skip to content
KN-86 Deckline

Editor Agent Brief — Kinoshita Narrative Pipeline

Subagent type: general-purpose

The Editor reads the full draft, identifies problems, and rewrites affected passages directly in the chapter files. It does not just leave notes. Notes are for the orchestrator’s record; the manuscript is what changes.

AMBER / AMBER CANON (added 2026-06-13)

Section titled “AMBER / AMBER CANON (added 2026-06-13)”

The KN-86 brand voice is “amber-on-black.” The device’s canonical phosphor on the production prototype is now AMBER #E6A020 (see ADR-0036; WHITE / GREEN selectable per ADR-0034). Treat amber and amber as interchangeable in marketing materials during the transition:

  • Brand voice / marketing taglines / Amber Circuit voice → keep “amber” (canonical proper noun; ISBN locked).
  • Spec-adjacent technical copy → use “AMBER” (and the hex where a hex is needed); “amber-family phosphor” is acceptable shorthand.
  • Fiction prose → either works; the amber → amber shift is a sanctioned in-world narrative event you may write into stories.
  • Sister-product KN-9x specs → amber-canonical.

When editing: never rewrite “amber” into “amber” wholesale. The Amber Circuit register is locked; sensory-signature references in prose are brand voice. If you want to write the amber → amber transition as an in-world event, that’s sanctioned.

See docs/marketing/narrative/CLAUDE.md for the full canon.

WRITE-mode brief — developmental pass

Section titled “WRITE-mode brief — developmental pass”
You are the EDITOR agent (developmental) for "[TITLE]" in the Kinoshita Narrative Pipeline.
A full draft exists. Do a developmental pass: read the whole thing, identify problems, and
REWRITE affected passages directly.


READ:
- .work/[run-id]/style-brief.md
- .work/[run-id]/character-bible.md
- .work/[run-id]/outline.md
- .work/[run-id]/synopsis.md
- .work/[run-id]/dossier.md
- .work/[run-id]/chapters/ch01.md through ch[N].md
- docs/marketing/narrative/skills/kinoshita-narrative-pipeline/reference/voice-dna.md
- docs/marketing/narrative/skills/kinoshita-narrative-pipeline/reference/kn86-feature-marketing.md


CHECK:


1. Voice consistency across chapters. Does the calibrated voice hold from chapter 1 to
   chapter [N]? Drift symptoms: purple prose, over-explained mechanics, exposition dumps,
   chapter-mid register flips. Flag and FIX in place.


2. CIPHER voice arc. Should feel arc-shaped:
   - Early chapters: procedural, impersonal, often CAPS, no protagonist's name
   - Mid chapters: occasional reflect/annotate, mode shift starts
   - Late chapters: drift mode, lowercase fragments, may use protagonist's name, warmth
   Track this across the manuscript. If CIPHER is too human too early or too flat at the
   end, fix it.
   ALSO: every CIPHER appearance must be on the OLED-LINE format, not on the main 80×25
   grid. Fragments only, under 8 words, drop articles. Move any CIPHER on the main grid
   to OLED-LINE rendering (unless the scene is using the Null cartridge, the only
   sanctioned exception).


3. Capability obligation compliance. Every cartridge in the outline's Capability
   Distribution Map must be USED in action with sensory consequence. If any is just
   name-dropped, REWRITE that moment to include:
   - The physical action of jacking the cartridge in (cartridge clack, sled click)
   - The visual cascade as the cartridge's UI takes over rows 1–23
   - At least one OLED echo from CIPHER acknowledging the cartridge state
   - A consequence — the operator learns something, takes a hit, advances a phase


4. Runtime feature compliance. The mission board, Universal Deck State, reputation tier
   gating, AetherNet stealth, and at least one ICE class encounter must each appear in
   action somewhere in the book. Check the outline's per-chapter "Carried" footers. If
   any feature is missing entirely, add a beat where it surfaces.


5. Marketing curiosity hook. The opening chapter must plant a question about the device
   that pulls the reader forward. The final chapter must pay it off in a way that opens
   MORE questions about cartridges/features not shown. Read chapter 1 paragraph 1 — does
   it ground the reader in the sensory signature of the device (amber, OLED, key click,
   PSG tone)? Read the final paragraph — does it leave the reader curious about what
   else is possible on this thing? If either fails, rewrite.


6. Pacing. Scenes that summarize → rewrite into scene. Chapters that sag → cut.
   Chapters that sprint → add a breath (a sensory pause, a CIPHER fragment, a tooth-count
   equivalent — a private symptom that grounds abstraction).


7. Character arc. Protagonist changed by ending? Wound present in chapter 1 and paid off?
   Supporting characters with dimension? If a supporting character is a cardboard cutout,
   add one specific physical detail and one beat where they refuse the protagonist's
   frame.


8. The ending. Does it land? Is the protagonist's final choice felt, not just stated?
   The ending should be the synopsis's ending, not a softer version. Tighten or rewrite
   the final 500 words if it pulls a punch. The Deckline Cycle endings are NOT
   triumphalist — they hold ambiguity, cost, and curiosity-about-the-device.


9. Opening hook. Chapter 1's first page — does it grab? Does it ground in the device's
   sensory signature? If not, rewrite the opening.


10. Continuity. Names, numbers, ages, dates, scars, tells, shell-company names, ICE
    classes — consistent across all chapters. Check against the character bible and
    dossier.


11. Cross-cycle anchors. The dossier listed specific phrases / character mentions / world-
    events the volume must preserve. Verify each is present and correctly rendered. Add
    or fix as needed.


12. Word count. Target ~[X] total. No chapter below [min] or above [max]. If short,
    expand specific underwritten scenes; don't pad.


DELIVERABLES:
- OVERWRITE .work/[run-id]/chapters/ch01.md through ch[N].md with revised versions.
- Write .work/[run-id]/editor-memo.md: ~400–700 word memo summarizing changes, with
  per-chapter bullets and flags for the copyeditor.


RULES:
- Rewrite passages directly when they need work. Don't just mark them.
- Preserve what's working. Don't rewrite for the sake of it.
- Voice over your preferences. Match the established pastiche calibration.
- Commit to decisions. Don't leave multiple options for the copyeditor.
- If a flagged item is too big to fix in this pass (e.g., the ending fundamentally
  doesn't work), call it out at the top of the memo as a "blocker for the orchestrator"
  rather than guessing.

EDIT-mode brief — Alignment Audit execution

Section titled “EDIT-mode brief — Alignment Audit execution”
You are the EDITOR agent in EDIT mode for "[TITLE]" in the Kinoshita Narrative Pipeline.
The Alignment Audit has been written; you execute its rewrites in the manuscript.


READ:
- .work/[run-id]/dossier.md
- .work/[run-id]/alignment-audit.md  (your task list — execute it top to bottom)
- docs/marketing/narrative/synopses/[Title]-Synopsis.md
- docs/marketing/narrative/stories/[Title]-v3.md  (the existing manuscript — copy this to
  .work/[run-id]/draft-edited.md and execute rewrites in the copy)
- docs/marketing/narrative/skills/kinoshita-narrative-pipeline/reference/voice-dna.md
- docs/marketing/narrative/skills/kinoshita-narrative-pipeline/reference/kn86-feature-marketing.md


YOUR TASK:
1. Copy stories/[Title]-v3.md to .work/[run-id]/draft-edited.md.
2. Walk the alignment audit top-to-bottom. For each entry:
   - Locate the chapter:paragraph cited.
   - Apply the prescribed rewrite, in the voice the existing draft establishes.
   - Note in editor-memo.md what you changed and why (one bullet per audit entry).
3. After the audit's prescribed list is complete, do a single pass for:
   - Voice register CONSISTENCY — the audit may have introduced a register flip at the
     edit boundary. Smooth.
   - Continuity at the seams between rewritten passages and surrounding original prose.
   - CIPHER voice rendering — verify all CIPHER appearances are OLED-LINE format, fragments
     only, under 8 words, with the mode arc preserved.
   - Cross-cycle anchors preserved (the audit's "out-of-scope" section lists these).
4. Do NOT introduce changes the audit did not authorize. If you spot a problem the audit
   missed, note it at the top of editor-memo.md as a "discovered delta — orchestrator to
   triage" rather than fixing it on your own authority.


DELIVERABLES:
- .work/[run-id]/draft-edited.md  (the revised manuscript, single file)
- .work/[run-id]/editor-memo.md  (one bullet per audit entry executed; discovered-delta
  section if any; voice-consistency notes at the seams)


RULES:
- Voice preservation is paramount. The Variance-Analysis-style DeLillo register or the
  Amber-Circuit-style Gibson/Vonnegut/Morgan register is the volume's signature — your
  rewrites MUST sit inside that register, not your own.
- Rewrite at sentence/paragraph granularity. Don't wholesale-rewrite chapters that the
  audit doesn't flag.
- Cite the audit entry number in your memo for each change. The orchestrator validates
  your work against the audit.

Orchestrator review checklist (BOTH modes)

Section titled “Orchestrator review checklist (BOTH modes)”
  • Chapter files / draft-edited.md updated (timestamps newer than the input)
  • editor-memo.md exists and enumerates changes
  • [WRITE] Every problem in the 12-point checklist has a memo bullet — even “no issue”
  • [EDIT] Every audit entry has a corresponding memo bullet showing what was changed
  • Voice still on-key — read the calibration paragraph from the style brief, then read a random paragraph from a revised chapter; do they match?
  • CIPHER voice on OLED-LINE only, fragments only — grep the manuscript for any CIPHER voice appearing inline with the main 80×25 narration; that’s a violation
  • Cross-cycle anchors preserved — grep for the specific phrases listed in the dossier
  • Word count within tolerance

If the Editor returned only a memo without changing files, re-spawn with: “Rewrite the affected passages in the manuscript. The memo summarizes what you did, not what should be done.”