KN-86 Deckline Marketing Plan

Great Western Productions Kinoshita Electronics Consortium (KEC) Recreation Project April 2026

Version 2.0 — April 10, 2026 Updated to reflect Capability Model commitment, OODA gameplay framework, Hot Swap mechanic, and Bare Deck Terminal HUD specification.

Part A: Marketing Context Document

Executive Summary

The KN-86 Deckline is a handheld console with a Lisp-based cartridge runtime. An 80-column amber terminal, a 31-key mechanical keyboard, a CIPHER-LINE auxiliary OLED, and a Pelican 1170 hardcase. It runs nOSh and loads KEC Lisp cartridges; the launch library is fourteen titles plus one. Set in the KEC / Edgeware universe. Hardware ships Q4 2027.

What it is. A focused, single-purpose handheld in the lineage of the Playdate — fixed display geometry, a fixed input grammar, and a curated cartridge library built around them. Hardware specifications live in CLAUDE.md (Canonical Hardware Specification); they are not restated here.

What it runs. The nOSh runtime owns the operator surface — mission board, phase chain, Universal Deck State, the CIPHER voice on the auxiliary OLED. Cartridges are authored in KEC Lisp and packaged as .kn86 capability modules (per ADR-0001, ADR-0004, ADR-0006). The launch library is fourteen capability modules plus one launch-adjacent title.

What you do with it. You type into a terminal. You run Lisp at the prompt. You stack capability modules across multiple cartridges and clear multi-phase missions, swapping cartridges mid-mission (Hot Swap) when a capability gap shows up.

When. Hardware ships Q4 2027 (per CLAUDE.md). The desktop SDL3 emulator is the development target today and the basis for community-facing pre-launch builds.

The world. The device sits inside a larger fiction — Kinoshita Electronics Consortium (KEC) and the Edgeware expanded universe. The fiction is the aesthetic and lore around the hardware. It is not a substitute for the product.

Core Positioning: “The KN-86 Deckline is a handheld console with a Lisp-based cartridge runtime. An 80-column amber terminal, a 31-key mechanical keyboard, a CIPHER-LINE auxiliary OLED, and a Pelican 1170 hardcase. It runs nOSh and loads KEC Lisp cartridges; the launch library is fourteen titles plus one. Set in the KEC / Edgeware universe. Q4 2027.”

The KN-86 differs from comparable handhelds by combining a Lisp-native input grammar, a hot-swappable capability-module cartridge model, and a fully realized fictional setting authored alongside the hardware. This document outlines how to reach the communities most likely to invest in something built this specifically.

Product Development Status

As of April 2026, the following project deliverables have been completed or specified:

Completed:

✅ Desktop emulator (SDL3) — fully functional with boot sequence, CIPHER voice, mission board framework
✅ Capability Model architecture — specified and implemented across all nOSh runtime systems
✅ ICE Breaker gameplay spec (10,000-word design document) — OODA Loop framework, Hot Swap mechanic, three living systems (Network, Toolkit, Threat) plus sound as fourth system
✅ Bare Deck Terminal HUD — specified with five nOSh runtime tabs (STATUS, CIPHER, LAMBDA, LINK, SYS); playable without cartridge
✅ Cartridge Runtime Framework (nosh_cart.h) — C-based handler-registration contract (cartridges authored in Lisp per ADR-0001, tree-walked by the Fe interpreter per ADR-0004 — no bytecode)
✅ All 4 launch titles designed as capability modules (per Capability Model Spec)
✅ 31-key Deckline layout finalized (14 function keys + 16 numpad keys + 1 TERM key; phone-layout numpad per ADR-0016; Kailh Choc v1 switches with MBK keycaps per ADR-0018; keycap legend manifest locked in ADR-0022)
✅ Product specification sheets (1-pager + 6-pager PDFs)

In Progress / Planned:

🔲 Prototype hardware build (Raspberry Pi Zero 2 W + Elecrow 7” IPS display, per CLAUDE.md Canonical Hardware Specification)
🔲 Physical cartridge slot mechanism and PCB integration
🔲 Enclosure, tooling, and assembly pipeline for a limited production run (qty. TBD; hardware ship target Q4 2027)

Product Positioning

What the KN-86 Is

The KN-86 Deckline is a handheld console with a Lisp-based cartridge runtime. It is:

A purpose-built handheld with fixed display geometry, a fixed input grammar, and a curated cartridge library — in the lineage of the Playdate
A Lisp-native interaction machine: CAR / CDR / CONS bound to physical keys in the operator’s input grammar (per ADR-0016)
A cyberdeck-format device: portable, custom-built, with a thematic design language drawn from the KEC / Edgeware universe
A collectible object: physical cartridge sleds carrying SD-based capability modules, an amber terminal aesthetic, deliberate design choices that reference 1988-era hardware without pretending to be period-accurate
A usable terminal even without a cartridge: the Bare Deck Terminal HUD features five nOSh runtime tabs (STATUS, CIPHER, LAMBDA, LINK, SYS) with small bounties and educational missions that teach the complete grammar

Key Designed Mechanics:

OODA Loop Framework (ICE Breaker): John Boyd’s Observe-Orient-Decide-Act cycle is the core gameplay framework. The operator’s skill is cycling the OODA loop faster than threats advance. This is tempo-based decision-making, not reflexive action.
Hot Swap Mechanic: The operator can physically pull a cartridge mid-mission and insert another when a capability gap is detected. The network advances at half-tempo during the swap. This is a signature mechanic that makes multi-phase capabilities tangible and strategic.
Bare Deck Terminal HUD: The device is a genuine operational terminal even empty. Every key except APPLY works on the bare nOSh runtime. Small runtime bounties (5–10 credits) teach the interface paradigm. The empty deck demonstrates that the KN-86’s value is in its grammar, not cartridge software.

What It Is NOT

Not a Nintendo Switch or Game Boy competitor — different scale, different audience, different runtime model
Not a general-purpose computer or replacement laptop
Not “a fictional console made real as a stunt” — the device is shipping hardware that runs a real Lisp runtime; the KEC / Edgeware fiction is the aesthetic and lore around it, not a substitute for the product

Language Matters

Lead with handheld console in product-marketing copy. The KN-86 is a handheld console — a focused one, in the lineage of the Playdate, with a Lisp-native input grammar instead of a d-pad. Cyberdeck and personal cyberspace terminal remain valid flavor descriptors and work as secondary framing once the reader knows what the device is.

Banned phrasings in product-marketing surfaces (this plan, executive summary, pitch decks, press kit, website copy, packaging copy, social):

“thought in lists” / “thinks in lists”
“shouldn’t have existed”
“never real — until now”
“never manufactured — until now”
“artifact we are resurrecting” / “reviving”
“blueprints left behind”
close paraphrases of the above

These concepts may continue to appear inside the in-universe fiction at marketing/narrative/; the ban applies to product marketing only. The KEC / Edgeware setting is not banned — the goal is to keep it as the closing beat of any positioning surface, not the opener.

Amber → amber (the canonical phosphor transition)

The brand voice has been “amber-on-black” since the brand was named, and the Amber Circuit ebook (released, ISBN locked) lives on that voice. The device’s canonical phosphor is now AMBER #E6A020 (decided on-glass against the deckline prototype 2026-06-13 — the prior #E6A020 read too yellow on the panel; amber is a warmer cousin in the same family). WHITE and GREEN are selectable phosphor schemes per ADR-0034.

Rules of thumb for marketing copy during the transition:

“Amber” remains the canonical brand-side proper noun. Existing marketing materials, the Amber Circuit voice, brand decks, and the website continue to use it. Do not retroactively scrub.
“Amber” is the canonical device-side specification noun. Spec sheets, technical descriptions, hardware mentions inside operator manuals use AMBER (and the hex where a hex is needed).
Treat amber and amber as interchangeable in marketing materials until a planned future pass migrates the brand to amber (timing TBD; not gating any current campaign). The phrase “amber-family phosphor” is acceptable shorthand when you want both at once.
The amber → amber shift is a sanctioned in-fiction narrative device. Within the KEC/KN-86 fictional universe, the phosphor refresh can be written into stories as a deliberate in-world event (a refresh by KEC, a generational shift between deck models). The Amber Circuit title and ISBN stay exactly as published; prose may be edited in later printings to incorporate the shift if useful — no rewrite required.
Sister-product specs (KN-9x: Statline, Toneline, Gridline, DM Sidearm) are amber-canonical — they ship with the current canon. Sister-product brand voice may still inherit “amber-family” framing where it serves continuity.

See docs/marketing/narrative/CLAUDE.md for the narrative-pipeline-specific canon.

Target Audiences

Research conducted April 2026 across five communities reveals distinct personas with overlapping interests.

Audience Prioritization

Not all five communities get equal weight. Prioritization — per Josh — is:

Tier	Community	% of content targeted	Why
Primary	Cyberdeck / DIY Electronics (§1)	40%	Native platform fit (Hackaday.io), highest conversion to waitlist/pre-order, strongest cultural match for “personal cyberspace terminal” framing
Secondary	Worldbuilding / Transmedia (§4)	20%	The KN-86 is a worldbuilding artifact; this community rewards narrative depth and sustains engagement between build milestones
Secondary	Retro Computing (§2)	15%	Aesthetic and historical resonance; slower-burn conversion but high content-reuse leverage
Tertiary	Indie Game / Interaction Design (§3)	15%	Activated at specific moments (emulator BETA in Week 14, cartridge game jam); not a sustained weekly audience
Tertiary	Mechanical Keyboard (§5)	10%	Activated at specific moments (switch/keycap content in Week 7 and Week 10); risk of over-indexing given the real switch is Choc v1 + MBK, not era-authentic Alps

The percentages apply to content volume, not to pillar emphasis. Every week’s publishing plan should roughly match these ratios when aggregated across the week’s pieces.

Content Pillar Weighting (by audience)

Pillar	Primary (Cyberdeck)	Secondary (Worldbuilding)	Secondary (Retro)	Tertiary (Indie Game)	Tertiary (Mechkeys)
Build Log	60%	10%	15%	5%	10%
Worldbuilding Lore	10%	70%	15%	5%	0%
OODA / Interaction Design	15%	10%	10%	60%	5%
Switch/Keycap/Sound	25%	0%	20%	15%	40%

Columns sum vertically across pillars; each row reads “what fraction of the pillar’s content is aimed at that audience.” Brand Reviewer sub-agent should spot-check weekly output against this grid.

Discord Strategy

A KN-86 Discord is part of the community infrastructure, but it is not the primary conversion surface — the mailing list is. Discord’s job is retention and signal, not acquisition.

Structure: Single server, channels by audience tier (e.g., #build-log, #lore, #cartridge-dev, #operators-lounge). Keep it small and legible. No “memes” channel — protects signal-to-noise.
Posture: GWP voice only (§Channel tone matrix). No KEC in-character roleplay in Discord — confuses newcomers.
Cadence: One weekly GWP post summarizing the week’s publishing (Friday). AMA once per month. No daily posting pressure.
Moderation: Small trusted mod team. Strict on hype-cycled language and nostalgia traps (§Forbidden words). Generous with newcomers (§Voice Attribute 4).
Success metric: Discord active members +5% WoW (announce-and-hook); active-to-waitlist ratio ≥50% after one month on server.

Where We Won’t Play

Stating explicitly where we won’t invest helps the team and sub-agents stay focused:

TikTok: Wrong audience and wrong format for a considered-not-clever voice. Revisit only if a specific campaign clearly fits.
Mainstream gaming press (IGN, Kotaku, Polygon): We are not a game console. Pitching as one erodes positioning.
Crypto / web3 adjacent spaces: Off-brand. Hard no.
General tech influencer tier (MKBHD, LTT, etc.): Too broad for a niche artifact. Prestige press targets are craft-press (Hackaday, Ars Technica retrocomputing desk, specific YouTube retrocomputing channels).
Paid social spend: Zero through Week 16. Consider only once waitlist-to-pre-order conversion data exists (runway Phase 2 at earliest).
Hot-take threads on X/Twitter: Not our voice. If we post there, we post threads of the build, not culture commentary.

1. Cyberdeck / DIY Electronics Community

Platform: r/cyberdeck, Hackaday.io, cyberdeck.cafe, Discord servers Community Size: r/cyberdeck is an active niche community; Hackaday.io is “the world’s largest collaborative hardware development community” (as of 2025) Engagement: High-quality documentation, process transparency, and novel technical approaches drive engagement

Why They’ll Care:

The KN-86 is a completed, documented cyberdeck design with custom PCBs, nOSh runtime, and enclosure
It uses period-authentic components (YM2149 PSG sound chip) and modern premium switches (Kailh Choc v1 with custom MBK keycaps) in a coherent aesthetic — per CLAUDE.md Canonical Hardware Specification
The build log bridges DIY electronics (breadboard proof-of-concept, component sourcing, assembly) and artistic vision
Hackaday.io compatibility: this project is native to their platform

Messaging Angle: “We reverse-engineered a fictional device. Here’s how we sourced the components, designed the logic, and brought it to physical form.”

Content Opportunity: Weekly Hackaday.io logs with schematics, CAD files, nOSh runtime iterations, and component testing. Cross-post to r/cyberdeck with community engagement.

2. Retro Computing Enthusiasts

Platforms: r/RetroComputing, Deskthority, vintage computing forums, YouTube retro channels Community Size: r/RetroComputing is a substantial subreddit; vintage hardware collecting remains popular post-2024 Engagement: Technical spec discussions, preservation and restoration culture, aesthetic appreciation of pre-1995 design language

Why They’ll Care:

The KN-86 is an intentional homage to 1988 computing: Lisp-based interface, monochrome amber IPS display, cartridge-based media
It respects historical constraints (no modern web browsing, no smartphone replacement narrative) while being fully functional
The Rosetta Stone cartridge labels are a cunning nod to both Lisp’s S-expressions and archaeological artifacts
The fiction layer adds depth: this isn’t nostalgia kitsch, it’s a comment on how we memorialize lost technologies

Messaging Angle: “A device designed in 1988 that was never built. Now archaeologists from GWP have completed the reconstruction from original blueprints.”

Content Opportunity: Blog posts on why 1988 was the mythological peak of personal computing, comparisons to real devices from that era (Osborne, Grid Compass, Casio Cassiopeia), and essays on interface philosophy.

3. Indie Game / Interaction Design Community

Platforms: r/gamedesign, itch.io, GDC experimental gameplay workshop discourse, IndieGames subreddit Community Size: Growing; itch.io hosts 800k+ games; GDC experimental gameplay is a prestigious venue Engagement: Novel input paradigms, anti-mainstream design choices, games that comment on their own medium

Why They’ll Care:

The CAR/CDR/CONS interface is a playable commentary on how we interact with data structures
ICE Breaker (the flagship title) is not a “game” in the traditional sense; it’s an exploratory interaction design
The mechanical cartridge insertion is a deliberate design choice that makes the act of loading software into tangible ritual
This community built Playdate’s cult following; they understand how form and philosophy shape experience

Messaging Angle: “Lisp is a language of lists. We made a device that thinks in lists. What does it mean to play with data this way?”

Content Opportunity: GDC talk proposal on Lisp-as-interface-paradigm; itch.io community posts showing ICE Breaker desktop emulator with build-in-progress footage; interaction design essays on the blog.

4. Worldbuilding / Transmedia Fiction Audience

Platforms: r/worldbuilding (1.9M members as of 2025), SCP Foundation community, ARG enthusiast forums (ARGNet), Discord worldbuilding servers, Tumblr lore tags Community Size: r/worldbuilding is one of Reddit’s largest creative communities; SCP Foundation has millions of readers Engagement: Deep lore appreciation, artifact analysis, “how did they design this system?” breakdowns, transmedia narrative construction

Why They’ll Care:

The KN-86 is a fictional product made real — a direct precedent for how transmedia worldbuilding can materialize
KEC’s history (founded 1978, mysterious closure 1992, Edgeware connection) is scaffolded across blog posts, cartridge labels, build logs, and design specs
Each cartridge label is both a technical spec and a lore artifact — the Rosetta Stone concept
This is “fictional product archaeology” — exactly what ARG communities and SCP enthusiasts engage with

Messaging Angle: “We found fragments of a fictional company’s work. We’re rebuilding it piece by piece, and the story unfolds as we go.”

Content Opportunity: Lore drops timed to build milestones; KEC origin story essays; the “why did KEC close in 1992?” mystery; Edgeware connection deep-dives; Notion worldbook entries or wiki-style documentation of the KEC universe.

5. Mechanical Keyboard Community

Platforms: r/MechanicalKeyboards (1M members as of 2025), Geekhack, Deskthority, keyboard forums Community Size: One of the largest hobbyist communities on Reddit; mechanical keyboard market projected to see robust expansion Engagement: Switch feel comparisons, sound design appreciation, historical component research, nostalgia for older switch technologies

Why They’ll Care:

The KN-86 uses Kailh Choc v1 low-profile switches with a custom MBK keycap set — a modern premium tactile experience designed specifically around the device’s Lisp input grammar (fictional 1988 KEC lore references “Alps SKFL” as the original 1988 design switch; see Worldbuilding Canon)
The build includes a deliberate sound design section exploring the YM2149F chip (Tangerine Dream-adjacent, not chiptune)
The switch choice is philosophically defensible: low-profile, tactile, impossible to source new — the device carries its own scarcity
Choc v1 keys (the newer cartridge insert version) represent a continuity line from the Alps era

Messaging Angle: “We designed a switch-and-keycap combination around a Lisp input grammar — Kailh Choc v1 low-profile switches with a custom MBK keycap set dye-subbed in the KN-86 Code Page. Here’s why that combination matters.”

Content Opportunity: Switch feel video (YouTube) using the real prototype; deep-dive blog post on why Choc v1 + MBK fits a Lisp input model better than QWERTY-era switches; Geekhack thread engagement on custom keycap design; sound design demo contrasting typing tempo on the KN-86 vs. Cherry MX boards.

Competitive Landscape: What Differentiates the KN-86

1. Playdate (Panic) — The Closest Precedent

Product: A handheld with a crank controller, designed by Teenage Engineering, with seasonal game releases via subscription Price: $199 at launch; sold out in 20 minutes; secondary market: $750+ Why It Succeeded:

Stunning industrial design (instantly recognizable)
Novel input paradigm (the crank is unique and satisfying)
Narrative-first marketing (Panic built anticipation through storytelling, not specs)
Scarcity and exclusivity (artificial scarcity, queued orders, slow delivery)

How the KN-86 Differs:

Playdate is about whimsy and charm; KN-86 is about archaeology and philosophy
Playdate delivers short, polished games; KN-86 is a single coherent experience (ICE Breaker) built into a conceptual framework
Playdate targets mainstream indie gamers; KN-86 targets worldbuilders, DIY hardware makers, and philosophical explorers
Playdate is a consumer product; KN-86 is a transmedia artifact with deep lore that unfolds across build logs, essays, and fiction

Competitive Advantage: Fiction-as-product. No other handheld is built from fictional blueprints with a full worldbuilding layer.

Where They’re Stronger:

Industrial design muscle (Teenage Engineering partnership) we cannot match on aesthetics-per-dollar
Existing mainstream indie-game press relationships and launch distribution
Proven subscription model for recurring revenue; a one-shot artifact has no equivalent monetization loop
Polished seasonal software cadence backed by a studio; we ship one pack-in + cartridges from a solo operator

2. Analogue Pocket — Premium Retro Handheld

Product: FPGA-based handheld for Game Boy/Game Gear/Atari emulation Price: $239.99 (as of March 2025, up from $220 due to tariffs) Target: Retro game collectors with $200+ budgets

How the KN-86 Differs:

Pocket is about perfect emulation of existing hardware; KN-86 is about a new (fictional) paradigm
Pocket is backward-compatible; KN-86 is forward-looking but rooted in 1988 aesthetics
Pocket targets preservation; KN-86 targets creation and narrative exploration

Competitive Advantage: Not a competitor — different audiences. Pocket buyers are game archivists; KN-86 buyers are worldbuilders and interface philosophers.

Where They’re Stronger:

Manufacturing execution and global distribution at scale
FPGA-grade technical credibility in the retro-hardware press
Vast pre-existing software library (the Game Boy corpus) vs. our single launch title
Clear “why you buy it” story (preservation) is immediately legible; ours takes explanation

3. Clockwork Pi DevTerm and uConsole

Products:

DevTerm: $239–$339; modular, with thermal printer; 6.8-inch screen; Rockchip RK3399 CPU
uConsole: $139–$209; compact; 5-inch IPS screen; modular CPU options (Raspberry Pi CM4, A-04, A-06, R-01)

Target: Developers, fantasy console makers, Linux enthusiasts

How the KN-86 Differs:

DevTerm/uConsole are general-purpose portable computers; KN-86 is a single-purpose philosophical tool
DevTerm/uConsole are modular and upgradeable; KN-86 is intentionally fixed and constrained
DevTerm/uConsole target developers; KN-86 targets explorers and artists
KN-86 has a narrative layer; DevTerm/uConsole are pure hardware

Competitive Advantage: Coherence and story. We’re not building a platform; we’re building an artifact.

Where They’re Stronger:

General-purpose utility — a DevTerm runs any Linux workload; KN-86 runs one worldview
Active modular ecosystem (swappable CPU boards, thermal printer) appeals to makers who want optionality
Established Crowd Supply crowdfunding track record; we have not yet proven we can close a pre-order round
Broader developer appeal (Python, Rust, anything); our audience must opt into a Lisp paradigm

4. Budge Retro Handhelds: Miyoo Mini / Anbernic RG35XX

Products:

Miyoo Mini Plus: ~$50–$80; excellent emulation; active OnionOS community; cult following
Anbernic RG35XX SP: ~$80–$100; larger screen; more comfortable; GarlicOS support

Target: Budget gamers, emulation enthusiasts

How the KN-86 Differs:

Price: KN-86 will be a premium artifact (estimated $300–$500 range for limited production)
Purpose: Not an emulation box; a singular creative tool with deep narrative context
Community: Different subreddits, different values

Competitive Advantage: None — different price tier and purpose. These are gateway drugs to cyberdeck culture; KN-86 is the museum artifact that takes the philosophy seriously.

Where They’re Stronger:

Price accessibility — a $50 device finds ten times the buyers of a $399 one
Mature open-source firmware ecosystems (OnionOS, GarlicOS) with active contributor communities
Instant-gratification value — plug in, play 10,000 ROMs tonight; KN-86 asks you to learn a paradigm
Established subreddits with high traffic; top-of-funnel discovery is largely solved for them

5. Back7 CO Cyberdecks

Product: DIY Pelican case builds with Raspberry Pi, custom 3D-printed enclosures Price: Custom builds; $100–$500 depending on components Target: DIY cyberdeck builders

How the KN-86 Differs:

Back7 is a starting point for custom builds; KN-86 is a finished philosophical object
Back7 empowers customization; KN-86 enforces aesthetic and narrative coherence
Back7 is about the building process; KN-86 is about the artifact and its fiction

Competitive Advantage: We’re not selling DIY; we’re selling the complete vision. Builders inspired by KN-86 might then build their own cyberdecks with Back7 techniques.

Where They’re Stronger:

Deep credibility inside the r/cyberdeck community — Back7 is a reference point and tastemaker
Personalized, one-of-a-kind builds command premium prices and word-of-mouth in ways a finished product cannot
No inventory risk: custom-commission model vs. our production-scale commitment
Years of accumulated build posts serve as a permanent content flywheel

6. Penkesu Computer

Product: 3D-printed clamshell cyberdeck with 7.9-inch display, Raspberry Pi Zero 2W, custom mechanical keyboard Target: Handheld computer enthusiasts, makers, hackers

How the KN-86 Differs:

Penkesu is open-source and hackable; KN-86 is a fixed artifact with intentional constraints
Penkesu celebrates DIY customization; KN-86 celebrates aesthetic and philosophical coherence
Penkesu is a Raspberry Pi container; KN-86 is a conceptual tool

Competitive Advantage: Narrative and purpose. Penkesu is a clever engineering challenge; KN-86 is a philosophical statement dressed as hardware.

Where They’re Stronger:

Fully open-source hardware — remix-friendly culture compounds reach via forks and derivatives
Lower barrier to entry for the maker audience (3D-print + off-the-shelf Pi)
Zero manufacturing risk — Penkesu is a reference design, not a product we have to ship
Clean, legible “here’s how I built it” documentation is native to the project’s identity

7. GameTank — Open-Source 8-Bit Console

Product: New 8-bit console launching July 2026 with twin 6502 CPUs, open-source hardware design, crowdfunded on Crowd Supply Price: $349 Status: Crowdfunding success (smashed $30K goal); launching Q3 2026 Target: Homebrew developers, hobbyists, hardware modders, retro gaming enthusiasts

How the KN-86 Differs:

GameTank is a gaming platform; KN-86 is an operational terminal with a philosophical framework
GameTank targets retro recreation (1980s arcade/console nostalgia); KN-86 targets fictional archaeology (1988 cyberpunk fiction made tangible)
GameTank is open-source and moddable; KN-86 is a fixed, coherent artifact with intentional constraints
GameTank is about gameplay; KN-86 is about interaction paradigm, decision-making speed (OODA loops), and how interface shapes thought
GameTank celebrates technical mastery of retro hardware; KN-86 celebrates the philosophy embedded in constraints

Competitive Advantage: Different audiences, different goals. GameTank buyers want to build retro games. KN-86 buyers want to explore decision-making under pressure via a Lisp-based operational terminal. The two communities may overlap, but they’re pursuing different values.

Where They’re Stronger:

Proven Crowd Supply close — they cleared their funding goal; we have not yet demonstrated pre-order conversion
Fully open-source hardware design attracts a larger hobbyist contributor base
Lower pedagogical overhead — “8-bit console for homebrew” is a one-sentence pitch; ours is not
Established crowdfunding muscle memory for a product in the same $349 price tier

8. Flipper Zero — The “Weird Gadget” Benchmark

Product: Multi-tool for wireless protocol exploration (sub-GHz radio, NFC, RFID, IR, BadUSB, GPIO) wrapped around a Tamagotchi-style dolphin character and a monochrome screen Price: $169; perpetually backordered; gray-market premiums up to $400 Target: Pentesters, hardware-curious teenagers, TikTok-driven weird-gadget audience Why It Succeeded:

Cohesive character-led narrative (the dolphin) turns a pentesting tool into a companion object
Monochrome screen + deliberate retro UI made a modern tool feel like an artifact
Relentless short-form video (TikTok, Instagram Reels, YouTube Shorts) created a discovery loop we cannot match
Strong Discord community functions as both tech support and social layer
Community-authored app catalog (Flipper Apps) provides a content flywheel without Flipper needing to build every app

How the KN-86 Differs:

Flipper is a pentesting multi-tool with charm; KN-86 is a single-paradigm philosophical terminal
Flipper is broad-surface (dozens of unrelated radio protocols); KN-86 is deep-surface (one Lisp paradigm, explored richly)
Flipper’s fiction is vestigial (the dolphin personality); KN-86’s fiction is load-bearing (the 1988 KEC corporate universe is the reason the device exists)
Flipper is aimed at doing things to the world (read a badge, spoof a remote); KN-86 is aimed at doing things in a world (ICE Breaker, capability modules)

Competitive Advantage: Depth of worldbuilding and paradigm coherence. Flipper sells a toolkit; KN-86 sells a way of thinking.

Where They’re Stronger:

TikTok-native virality and mainstream gadget-press coverage — neither is on our channel list
Hardware-hacking communities (HackerNews, Hackaday) already consider Flipper a reference point
Character-led branding plays in short-form video; our Cipher voice is built for long-form reading
Established app-store-style third-party developer ecosystem; we have not yet opened cartridge authoring to outsiders

9. MNT Reform — The Premium Artisanal Computer

Product: Open-source, user-serviceable laptop with mechanical keyboard, trackball, replaceable modules, and a deliberate aesthetic position against disposable consumer hardware Price: ~$1,700+ (kit); ~$2,200 (assembled) Target: Designers, hardware rights activists, privacy-conscious professionals, “computing should be humane” adherents Why It Succeeded:

Articulate manifesto-level positioning — MNT wrote itself into a philosophical lineage (Alan Kay, right-to-repair, post-Intel computing)
Unapologetic premium pricing signals the seriousness of the project
Hardware, nOSh runtime, schematics, and PCB files fully open — creates long-tail trust no marketing budget can buy
Sustained, literate long-form blog cadence builds authority over years

How the KN-86 Differs:

Reform is a general-purpose daily-driver laptop; KN-86 is a single-purpose narrative terminal
Reform’s fiction is absent — it is real hardware positioned against real competitors; KN-86’s fiction is central — the device is evidence of a company that never existed
Reform is ~$2,000 tooling for professionals; KN-86 is a ~$399 artifact for worldbuilders
Reform’s openness is the product; KN-86’s worldview is the product

Competitive Advantage: We’re not competing on openness or professional utility. KN-86 is a narrative artifact; Reform is a working laptop for people who need a working laptop.

Where They’re Stronger:

Long-form literate brand voice executed over years — a depth of archive we are five years away from matching
Trust earned through radical openness (schematics, nOSh runtime, BOM) at a level we will not match because the KN-86 is not intended as a general-purpose platform
Legitimate professional-tier use case (a person can actually use a Reform as their daily driver); we are explicitly not pitching daily-driver utility
Serves a higher-LTV customer willing to spend $2K+ on a coherent worldview; our price ceiling is lower

2x2 Positioning Map

The competitive field maps cleanly onto two axes we care about: narrative density (how much fiction, worldbuilding, and philosophical framing the product carries) on the vertical, and interaction specificity (how narrow vs. general-purpose the device is) on the horizontal.

                       HIGH NARRATIVE DENSITY
                              ▲
                              │
                              │   ◆ KN-86 (fictional company,
                              │     capability model,
                              │     Lisp paradigm)
                              │
              ◆ Playdate       │   ◆ MNT Reform
                (crank, seasons,│     (manifesto,
                 Panic voice)   │      right-to-repair)
                              │
                              │   ◆ Flipper Zero
                              │     (dolphin character)
  ◆ Back7 ───────────────────┼─────────────────────────
    (DIY)                     │
                              │        ◆ GameTank
  ◆ Miyoo Mini / RG35XX       │          (retro console)
    (budget)                  │
                              │   ◆ DevTerm / uConsole
                              │     (modular laptop)
                              │
  ◆ Analogue Pocket           │
    (perfect emulation)       │
                              │
  GENERAL PURPOSE ◀───────────┼───────────▶ NARROW / SPECIFIC
                              │
                              ▼
                       LOW NARRATIVE DENSITY

Quadrant reading:

High narrative × narrow purpose (upper-right): KN-86 is alone in this quadrant. Playdate, MNT Reform, and Flipper are the closest neighbors but each lives elsewhere — Playdate skews more general (it’s a game platform), Reform skews much more general (a laptop), Flipper is narrower in purpose but lower in narrative density.
High narrative × general purpose (upper-left): Playdate and Reform. These products carry a strong point of view but serve many use cases.
Low narrative × narrow (lower-right): GameTank, DevTerm, uConsole. Sharp focus, minimal fiction.
Low narrative × general (lower-left): Pocket, budget handhelds, DIY cyberdecks. Hardware first, story optional.

Implication: The strategic moat is the upper-right quadrant. Our marketing job is to make that position legible — not to drag the device toward the general-purpose axis (where Reform and Playdate have capital and execution advantages) or toward the low-narrative axis (where price and throughput win).

If They Copy Us — Defensibility

The closest plausible “someone ships a KN-86 lookalike” scenarios, and why the moat holds:

“Panic makes a Lisp handheld.” The closest existential risk. Panic has the industrial-design talent, press relationships, and audience trust to ship something adjacent. What they cannot buy is the KEC corporate universe — the multi-year accumulated fictional archive (GWA, Sandgrain, Edgeware) that predates the device. They would ship a clever Lisp toy; we ship the artifact of a company that has been “real” in our worldbuilding for years before the hardware existed.

“A clone ships from Shenzhen.” Budget clones commodify hardware, not worldview. A clone can replicate the single-phosphor display, the 31-key layout, even the cartridge slot. It cannot replicate the Cipher voice, the capability-model cartridge grammar, the NoshAPI FFI surface, or the integrated Lisp paradigm that makes the hardware comprehensible. A clone would be a dead terminal without the nOSh runtime’s orchestration layer — and the nOSh runtime is the product.

“A well-funded cyberdeck startup copies the positioning.” Positioning is the easiest thing to imitate and the hardest thing to inhabit. The four-attribute voice (considered, fictional-with-a-straight-face, philosophically serious, generous to newcomers) is defensible because it requires years of long-form writing to earn. A competitor would have to out-read us, out-think us, and out-write us over a multi-year cadence. That is a bet we are happy to compete on.

“An AI/LLM-native handheld claims the philosophical territory.” The likeliest next wave of competition is a voice-agent handheld marketed as “a thinking device.” KN-86’s defense is that our philosophical claim is embedded in the constraints, not the compute. We are more defensible the more constrained we look: single-phosphor, fixed-pixel framebuffer, no network, no LLM, no voice agent. The moat is that the constraints are the argument.

What we cannot defend on: Price (anyone can undercut), manufacturing speed (anyone at scale beats us), open-source credibility (Reform and Penkesu own that axis), mainstream distribution (Analogue and Flipper own retail). We do not fight on those axes.

What Makes the KN-86 Unique

Fiction-as-Product: No competitor integrates fictional worldbuilding into the hardware itself. The KN-86 is evidence of a fictional company. This is transmedia narrative materialized.
Capability Model Architecture: The KN-86 uses a unified nOSh-runtime/cartridge model where nOSh is the orchestrator (owns mission board, economy, phase chain, Cipher voice) and cartridges are capability modules. This enables multi-phase missions spanning multiple capability domains with physical cartridge swaps mid-run. The Capability Model is the definitive software architecture.
OODA Loop as Core Gameplay Framework: ICE Breaker, the pack-in title, is built on John Boyd’s Observe-Orient-Decide-Act cycle. The operator’s skill is tempo—cycling OODA faster than threats advance. This is decision-making under pressure, not reflex-based action. No other handheld makes this the explicit design center.
Hot Swap Mechanic: The operator can physically pull a cartridge mid-mission and insert another when a capability gap is detected. The network advances at half-tempo during the swap. This transforms multi-phase gameplay from abstract mechanics into tangible, strategic physical action.
Bare Deck Terminal HUD: The device is a genuine operational terminal even without a cartridge. Five nOSh runtime tabs (STATUS, CIPHER, LAMBDA, LINK, SYS) teach the complete grammar through small bounties and educational missions. The empty deck demonstrates that the KN-86’s value is in its philosophy, not cartridge software.
Lisp Interaction Paradigm: CAR/CDR/CONS as physical grammar. The device teaches you how to think by virtue of how it forces you to interact. No competitor has this.
Cartridge-as-Rosetta-Stone: Labels on cartridges are both technical specs and lore artifacts. Loading software becomes an archaeological act.
Philosophical Coherence: Every design choice serves the narrative: Kailh Choc v1 low-profile switches with MBK keycaps (tactile feedback on list operations), YM2149 PSG (Tangerine Dream, not chiptune), monochrome amber IPS display (constrains cognitive load, focuses on structure not visuals), no QWERTY keyboard (breaks expectations, enforces different thinking). (Hardware values per CLAUDE.md Canonical Hardware Specification.)
Build Log as Narrative: The 18-week build is documented as both technical process and fictional excavation. GWP is an “archaeologist,” KEC a “lost company.” The narrative unfolds as we build.

Price Positioning

The KN-86 is not a budget device. It is a limited-production, artifact-grade terminal designed for people who understand what they’re buying.

Estimated Pricing (Limited Production Run):

Assembled Unit: $349–$449 (comparable to GameTank at $349, Playdate at $199+ secondary market, Analogue Pocket at $240)
Kit Version (DIY Assembly): $249–$299 (for builders who want to engage with the construction narrative)

Pricing Rationale:

Component Cost: Kailh Choc v1 switches + custom MBK keycap set (per-unit), YM2149 PSG ($15–20), Elecrow 7” IPS display assembly, Raspberry Pi Zero 2 W, custom PCBs, enclosure, cartridge mechanics — detailed BOM in docs/device/hardware/sourcing-guide.md
Limited Production: Not mass-manufactured. Each unit is built as part of the GWP archaeology narrative. Scarcity + story = premium positioning
Market Comparables: GameTank ($349) targets homebrew developers; KN-86 ($349–449) targets worldbuilders and operational philosophers. Same price tier, different value proposition
Precedent: Playdate ($199) sold out in 20 minutes; secondary market reached $750+. KN-86’s premium positioning aligns with artifact-grade collectibles (high demand, limited supply)

Not Competing on Price: The document emphasizes that KN-86 buyers are not choosing between this and Miyoo Mini ($50–80). They are choosing between this and a high-end vinyl record, art book, or limited-edition board game. Price signals that this is a serious artifact, not a casual consumer device.

Brand Voice

The Dual Narrative

Two voices speak about the KN-86:

KEC Voice (1988):

Formal, slightly mysterious, product-focused
Writes like a company that existed in the Edgeware universe
Technical, precise, unapologetic about constraints
Example: “The Kinoshita KN-86 Deckline. A Personal Cyberspace Terminal for operators who think in lists. Designed for exploration. Built for constraint.”

GWP Voice (2026):

Archaeologist, scholar, curious explorer
Writes like someone reconstructing a lost artifact
Transparent about the process, generous with newcomers
Example: “We found fragments of KEC’s work. Blueprints, part numbers, design philosophy. We’re rebuilding what was lost. Here’s how we’re doing it.”

Never Break Character Unnecessarily — but don’t gatekeep the audience. Make the real project accessible. Bridge the fiction and the hardware honestly.

Voice Attributes (four-part structure)

A copywriter sub-agent should be able to read any one of these and draft on-voice without further direction. Each attribute follows the same shape: We are / We are not / This sounds like / This does NOT sound like.

1. Considered, not clever

We are: patient. We explain our choices. We show our work. We earn the reader’s attention one sentence at a time.
We are not: hype-cycled. We do not use engagement tricks. We do not write “You won’t believe…” or “The one thing…” or stack rhetorical questions.
Sounds like: “We considered four switch families before landing on Kailh Choc v1. Here’s the decision matrix.”
Does NOT sound like: “We tried EVERY switch — and the winner will surprise you.”

2. Fictional with a straight face

We are: committed to the bit. When we speak in KEC voice, we speak as if KEC existed. When we speak in GWP voice, we speak as the people who know it didn’t.
We are not: winking. We do not say “(just kidding, this is fake!)” in KEC copy. We do not treat the fiction as a gimmick in GWP copy.
Sounds like (KEC): “The KN-86 Deckline. Personal cyberspace terminal. Kinoshita Electronics Consortium, 1988.”
Sounds like (GWP): “KEC never shipped the KN-86. We’re shipping it instead. Here’s what that means for the design choices.”
Does NOT sound like: “LOL imagine if KEC was real, right? This fictional company we made up…”

3. Philosophically serious

We are: people who believe interface design shapes thought. We take Lisp seriously. We take constraint seriously. We take the 1988 aesthetic seriously.
We are not: nostalgic, reverential, or precious. We do not say “back when computers were real computers.” We do not shame modern tools.
Sounds like: “A terminal that thinks in lists is not a novelty — it is a bet that structure shapes cognition.”
Does NOT sound like: “Modern tech has lost its soul. The KN-86 brings back what we’ve forgotten.”

4. Generous with newcomers

We are: welcoming to people who have never heard the words “cyberdeck” or “CAR/CDR/CONS.” We define terms inline the first time they appear in a piece. We link to primers rather than requiring them.
We are not: jargon-heavy. We do not assume the reader already lives in r/cyberdeck.
Sounds like: “A cyberdeck is a custom-built portable terminal — the DIY cousin of a laptop, with personality.”
Does NOT sound like: “As every cyberdecker knows, the mods scene has been debating Pi vs. Framework since 2022.”

Forbidden words & phrases

Do not use in public copy (KEC or GWP voice). Brand Reviewer sub-agent should flag these as hard fails.

Hype-cycled: “revolutionary,” “game-changing,” “disrupting,” “unprecedented,” “paradigm shift,” “insanely good,” “literally the best”
Overclaim language: “complete,” “finished,” “final,” “launched” (for hardware that has not shipped); “production-ready” (until production is locked); “fastest,” “only,” “first-ever” (without a specific scoped claim that can be verified)
Nostalgia traps: “real computers,” “back when things were simple,” “what we’ve lost,” “kids today” (or any variant)
AI slop signifiers: “in today’s fast-paced world,” “at the intersection of,” “journey,” “delve,” “tapestry,” “landscape” (as in “the cyberdeck landscape”)
Demo-waving: “just wait until you see,” “you won’t believe,” “mind-blowing,” “you have to try it”
Emoji in body copy: Never in blog, newsletter, or Hackaday posts. Single emoji is fine in social posts if it’s the only way to hit a beat.

Channel tone matrix

The same voice flexes by channel. All variants still pass the four Voice Attributes above.

Channel	KEC/GWP balance	Register	Length shape	What’s emphasized
Blog (gwpdispatch.com)	70% GWP / 30% KEC	Essayistic, patient	1,200–2,000 words	Reasoning, evidence, philosophical grounding
Hackaday.io build log	90% GWP / 10% KEC	Technical, documentary	600–1,200 words	Specifics, photos, component choices, decision matrices
Newsletter	60% GWP / 40% KEC	Warm, direct	400–700 words	One story, one CTA (usually: share the list)
Reddit self-post	100% GWP	Conversational, honest	300–600 words	Question that invites reply; no hard-sell
YouTube script	60% GWP / 40% KEC	Spoken, deliberate	6–10 min runtime	Hook → story → payoff; minimal cuts
Mastodon / Bluesky	50% / 50%	Light, allusive	1–3 short posts	Images; enigmatic KEC one-liners work well
X/Twitter (if used)	70% GWP / 30% KEC	Punchy	Thread format	Threading the build — one beat per post
Discord	100% GWP	Casual, helpful	Variable	Conversation, troubleshooting, welcome posture
Press / pitch	80% GWP / 20% KEC	Professional, plain	300–500 words	Facts, ship date (Q4 2027), what’s real vs. fictional

Tone Guidelines

Respectful of the craft: This is not a novelty. We take interface design, worldbuilding, and hardware seriously.
Playful with the premise: The fiction is real, but we’re not pretending it fooled anyone. The joke is in the commitment.
Transparent about process: Show failures, iterations, component sourcing challenges. Authenticity builds trust with DIY communities.
Inviting to newcomers: Someone seeing “cyberdeck” for the first time should be able to understand what’s happening without the jargon.
Philosophical: We’re not just building hardware. We’re commenting on how interfaces shape thought, how constraints focus creativity, how fiction can materialize.

Content Pillars

The marketing strategy rests on seven interlocking content streams:

1. Build Log (Process Documentation + Fictional Excavation)

What: Weekly updates documenting hardware assembly, nOSh runtime development, component selection, and testing.

Tone: Technical but narrative. “Here’s the BOM decision matrix that got us from Raspberry Pi Pico to Pi Zero 2 W” is build log. “The switch feel of 1988 is a fiction we’re translating, not a myth we’re pretending to recover” is the narrative layer.

Formats:

Hackaday.io project logs (primary home)
Blog posts on gwpdispatch.com (longer-form)
YouTube videos (assembly time-lapses, proof-of-concept demos)
Reddit posts in r/cyberdeck, r/MechanicalKeyboards, r/RetroComputing
Short video clips for Mastodon/Bluesky

Cadence: Weekly updates, 18 weeks, with alternating technical/lore focus each week.

2. Worldbuilding Lore Drops

What: The KEC universe unfolds through blog essays, cartridge labels, design spec documents, and narrative fragments.

Content Types:

“The Kinoshita Electronics Consortium: A Company That Never Was” (origin story)
“The Edgeware Connection: Why KEC Shut Down in 1992” (mystery)
“Thinking in Lists: The Philosophy of Lisp-Based Interface Design” (philosophical defense)
Cartridge label designs that encode both lore and functionality (e.g., “ICE BREAKER v3.2 // Emergency Exploration Utility // KEC Internal Use Only // Serial XX-XXXX”)
“Personal Cyberspace” definition essays (what is cyberspace in 1988? what is personal computing in a post-individual world?)

Audience: r/worldbuilding, ARG communities, SCP Foundation enthusiasts, transmedia fans.

Cadence: Biweekly essays timed to major build milestones.

3. The OODA Loop—Decision Instrument Design

What: ICE Breaker is built on John Boyd’s OODA Loop (Observe-Orient-Decide-Act). This pillar explores tempo-based decision-making, how the interface enables rapid re-cycling, and why this is a playable philosophy, not just a game mechanic.

Content Types:

“The OODA Loop: From Fighter Jet Tactics to Handheld Terminal Design” (why Boyd, why now)
“Tempo as Skill: How Fast Can You Think?” (ICE Breaker gameplay philosophy)
“Sound as the Fourth System: Audio Cues in Decision-Making” (sound design bridges to gameplay)
“Hot Swap as Strategy: Why Cartridge Swaps Are Turns, Not Loading Screens” (game design post-mortem)
Video essays showing ICE Breaker’s three living systems (Network, Toolkit, Threat) and how they feed the OODA cycle

Audience: Game designers, strategy game enthusiasts, decision-science communities, OODA researchers.

Cadence: Biweekly deep-dive posts timed to ICE Breaker reveal and post-launch.

4. The Bare Deck—Terminal First, Cartridge Platform Second

What: The KN-86 without a cartridge is a complete, usable operational terminal. This pillar shows how the device teaches the grammar through nOSh runtime tabs, small bounties, and educational missions.

Content Types:

“No Cartridge? No Problem: The Bare Deck Terminal HUD” (what you can do empty)
“Five Tabs, One Philosophy: STATUS, CIPHER, LAMBDA, LINK, SYS” (nOSh runtime deep-dive)
“Micro-Bounties and the Empty Deck: Learning Lisp Without Software” (educational model)
“The Terminal Is the Device: Why Constraints Are the Feature” (design philosophy)
Video walkthrough: “Starting with Nothing, Learning Everything” (bare deck tutorial)

Audience: Cyberdeck enthusiasts, minimalist computing advocates, educational technologists, philosophy of interfaces.

Cadence: Ongoing after hardware launch; released alongside bare deck / emulator availability.

5. Interaction Design Essays

What: Deep dives into the philosophy of how the KN-86 works and why those choices matter.

Content Types:

“Why CAR/CDR/CONS? A Lisp Grammar for Physical Input” (justification of interface paradigm)
“The Cartridge Label as Rosetta Stone” (on artifact design and meaning)
“No QWERTY: Why Constraints Enable Exploration” (counter-mainstream UX thinking)
“The Sound of Thinking: YM2149F and the Tangerine Dream Aesthetic” (audio philosophy)
“What Does a 1988 Handheld Know That Modern Devices Forgot?” (design archaeology)

Audience: r/gamedesign, GDC submissions, interaction designers, indie game developers.

Cadence: Biweekly, timed to content pillar releases.

6. Sound Design Deep Dives

What: The YM2149F Yamaha chip is the voice of the KN-86. Its sound is not chiptune nostalgia but a deliberate aesthetic choice connected to Tangerine Dream, modular synthesis, and 1980s electronic minimalism.

Content Types:

“Not Chiptune: The YM2149F and Electronic Minimalism” (historical context)
Audio demos comparing the KN-86’s sound to period-accurate devices
Production notes on emu2149 implementation
Essays on how sound design informs the interaction experience
Video series: “16 Seconds of Pure YM2149F” (short aesthetic studies)

Platforms: YouTube, SoundCloud, blog, Mastodon (audio clips).

Audience: Sound designers, synth enthusiasts, people interested in audio-as-interface.

7. Fiction-as-Product Philosophy

What: Essays exploring the meta-layer of this project: why build a fictional device? What does it mean to materialize fiction? How does this relate to transmedia worldbuilding, ARGs, and the SCP Foundation model?

Content Types:

“Building from Blueprints That Don’t Exist: The KN-86 as Fictional Archaeology”
“Transmedia Worldbuilding and Hardware: A Case Study in Materialized Fiction”
“The KEC Model: Fictional Companies as Design Constraints”
“Why We’re Not Making a Sequel: On Authenticity and Singular Artifacts”
Comparison essays with Playdate, SCP Foundation, and other “fiction made material” projects

Audience: Media scholars, worldbuilders, art and technology communities, r/worldbuilding.

Cadence: Monthly essay, posted to blog and cross-posted to relevant subreddits.

Marketing Channels

1. YouTube (Build Log Video Series)

Best Practices (2025 Research):

87% of successful channels use series content (uniting videos in logical sequences)
Creative process content resonates: showing how an idea becomes real demystifies craft
First 15 seconds and thumbnail quality are critical: 93% of successful channels prioritize these
Series format (concept → build → result) improves watch time and recommendation algorithm

KN-86 Strategy:

Video Series Structure:

“Kinoshita Archaeology” (4-6 episodes) — the discovery narrative, lore background
“Component Hunt” (4 episodes) — sourcing Kailh Choc v1 switches, the Elecrow IPS display, YM2149 PSG chips
“Proof of Concept” (3 episodes) — breadboard build, first pixels, first sounds
“Enclosure Design” (3 episodes) — 3D printing, tolerances, assembly
“First Boot” (2 episodes) — nOSh runtime on real hardware, ICE Breaker launch
“Retrospective” (1 episode) — what we learned, the philosophy, what’s next

Cadence: One video per week, 18 weeks.

Thumbnail/Title Strategy:

Descriptive titles: “We Found the Lost Kinoshita KN-86 Blueprints” (hooks premise)
Thumbnails: High contrast, show the hardware, use KEC branding colors
First 15 seconds: Hook with the artifact or a satisfying build moment (switch click, LED flicker)

Target Audience: r/cyberdeck, r/RetroComputing, indie game devs, maker community, algorithm-friendly DIY + worldbuilding crossover.

2. Blog/Newsletter (gwpdispatch.com)

Content Strategy:

Long-form essays (1500–3000 words) on interaction design, worldbuilding, and hardware philosophy
Weekly build log summaries linking to Hackaday.io
Monthly lore deep-dives
Guest posts from component historians (Alps switch experts, YM2149F audio engineers, etc.)
Email newsletter: biweekly digest of all KN-86 content + broader worldbuilding news

Cadence:

2–3 blog posts per week (mix of original essays, build log summaries, lore drops)
Newsletter: every other Friday
Long-form essays: once per week (750–1500 words minimum)

SEO Strategy:

Target keywords: “cyberdeck build guide,” “Lisp interface design,” “YM2149 PSG synthesizer,” “Kailh Choc v1 custom keycaps,” “transmedia worldbuilding,” “fictional product design”
Internal linking between build logs, essays, lore drops, and product spec pages

3. Reddit Community Engagement

Target Subreddits and Strategy:

r/cyberdeck

Introduce the project in week 1 with a concept post and lore hook
Weekly build log cross-posts (self-post, not spam)
Engage in community discussions about design philosophy
Post proof-of-concept videos and assembly updates
Tone: “We’re building something weird, here’s how we’re doing it”

r/MechanicalKeyboards

Walk through the Kailh Choc v1 switch + custom MBK keycap design choice (and why KEC’s fictional Alps SKFL became our design constraint)
Deep-dive post on why we chose these switches
Sound design demo posts
Engage in switch comparison threads
Tone: “Respecting the craft of tactile feedback since 1988”

r/RetroComputing

Lore post: “We’re Rebuilding a Fictional 1988 Device”
Design philosophy posts on 1988 as a design era
Component sourcing discussions
Comparison posts (KN-86 vs. Osborne, Grid Compass, etc.)
Tone: “Archaeology meets hardware”

r/worldbuilding

Lore announcement: “The Kinoshita Electronics Consortium Universe”
Cartridge label design posts
“How do you materialize fictional products?” discussion threads
Philosophy essays on transmedia worldbuilding
Tone: “Here’s a complete fictional company. Build with us.”

r/gamedesign

Interaction design essays on Lisp-as-interface
“Novel input paradigm” showcases
ICE Breaker gameplay mechanics breakdown
Tone: “What if your interface was philosophy?”

Cadence:

Presence in all five subreddits from week 1
Weekly build log posts in primary subreddits (r/cyberdeck, r/MechanicalKeyboards)
Lore drops in secondary subreddits (r/worldbuilding, r/gamedesign) on biweekly basis
Genuine community participation, not just self-promotion

4. Hackaday.io Project Page

Best Practices (2025 Research):

Tell us what, why, and how. Explain your project thoroughly and post excellent images.
Use the WYSIWYG editor for stress-free documentation
Embed YouTube videos directly (paste the URL)
Link to external resources (GitHub for nOSh runtime, CAD files on Thingiverse, etc.)
Keep regular logs of ongoing progress

KN-86 Strategy:

Project Page Structure:

Project Overview — The fiction hook + technical summary
Details Section — Full bill of materials, component sourcing, CAD files, nOSh runtime repos
Logs Section — Weekly technical build logs (primary documentation home)
Gallery — High-quality assembly photos, schematics, PCB designs
Files — Downloadable assets (CAD, nOSh runtime, design specifications, cartridge label templates)
Links — GitHub (nOSh runtime), blog (essays), YouTube (videos), related projects

Weekly Log Structure:

Title: Descriptive, keyword-rich (e.g., “Week 3: Designing the Keycap Set — Why Choc v1 + MBK Fits a Lisp Grammar”)
Summary paragraph (lore + technical)
Process documentation (photos, CAD renders, breadboard screenshots)
Challenges and solutions
Next week preview

Cadence: One detailed log per week, 18 weeks.

5. Mastodon / Bluesky (Short-Form Updates)

2025 Landscape:

Bluesky: 33M users, primarily Gen Z/Millennial, 62% under age 34. Thriving developer and creator ecosystem.
Mastodon: 8700+ instances, decentralized, strong maker and open-source community.

KN-86 Strategy:

Content Mix:

Work-in-progress photos (switch mounting, PCB testing, 3D prints)
Short lore snippets (KEC timeline fragments, cartridge label previews)
Links to full blog posts and Hackaday logs
Sound design clips (YM2149F audio)
Behind-the-scenes: component sourcing, soldering closeups, problem-solving moments
Engagement: reply to related projects, boost other cyberdeck/worldbuilding posts

Tone: Playful, transparent, building in public. “Look at this beautiful switch” and “Why we chose Lisp” in equal measure.

Cadence:

3–4 posts per week (mix of photos, text, links)
High-quality images (component close-ups, build progress, final products)
Hashtags: #KN86, #cyberdeck, #worldbuilding, #Lisp, #hardwaredev, #AlpsSKFL, #YM2149F

Cross-Platform: Identical posts across both networks, but leverage each community (Bluesky for algorithm feeds and custom feeds around #cyberdeck; Mastodon for open-source and maker instances).

6. Itch.io (Desktop Emulator + Game Files)

Strategy:

Host a free desktop emulator of the KN-86 (browser or downloadable)
Upload ICE Breaker game files for exploration
Link to all documentation and lore
Community game jam: encourage developers to write Lisp games for the KN-86 environment

Purpose:

Lower barrier to entry: people can explore the device before commitment
Accessible to game designers and interaction artists
Bridges the fictional hardware to a real (virtual) experience
Centralizes game and documentation in maker space

Cadence: Emulator beta in week 8, full release in week 12, community game jam announcement in week 14.

Marketing Timeline & Key Milestones

The 12-week plan spans weeks 5–16 of the 2026 announce-and-hook campaign. Hardware ships Q4 2027 (per CLAUDE.md Canonical Hardware Specification). Week 16 is not a product launch — it is the end of the first-wave reveal arc, when a working prototype is shown publicly and the pre-order waitlist opens. Weeks 17+ begin the pre-order runway arc that runs through hardware ship.

Why start in week 5?

Weeks 1–4: Internal documentation and lore foundation (not public)
Week 5: First public announcement (concept + lore hook)
Weeks 5–13: Build in public — emulator as the 2026 demo vehicle, growing community momentum
Weeks 14–16: Prototype reveal arc — working Pi Zero 2 W prototype shown publicly; pre-order waitlist opens
Weeks 17+ (through Q4 2027): Pre-order runway — sustained content cadence, production readiness, community beta program, final-unit reveal

This gives media time to build and allows the community to witness the full arc from fiction to artifact to shipping hardware.

Part B: 12-Week Marketing Plan

KPI Framework (Weeks 5–16)

Every week’s metrics section tracks the same primary KPI plus week-specific secondary KPIs with numeric targets.

Primary KPI (every week):

Mailing list growth: +10% week-over-week. This is the one number that matters. If mailing list growth hits 10% WoW, the week is a pass — regardless of what any other metric did. If it misses, the weekly retro has to explain why and what the correction is.

Secondary KPIs (numeric targets by content category):

Category	Weekly target (announce-and-hook phase)
Reddit top-post score (best of week, across all our posts)	≥100 upvotes
Hackaday.io followers	+10% WoW (early weeks), trending down to +3% WoW by Week 13
YouTube video views (that week’s hero video)	≥1,000 views in 7 days
Blog read-through (median scroll depth on hero essay)	≥60%
Newsletter open rate	≥45% (healthy hobbyist-list benchmark)
Newsletter click-through rate	≥8%
Social media reach (combined Mastodon + Bluesky impressions)	≥10,000/week
Discord active members (if Discord live)	+5% WoW

How this rolls up:

Weekly scorecard: One number at the top — mailing-list WoW %. Secondary KPIs appear below as a table with green/yellow/red status vs. target. See marketing:performance-report skill for the expected report shape.
Why +10% weekly: An audience of engaged hobbyists grows through word-of-mouth and referral more than paid reach. 10% WoW is ambitious but achievable with a working announce-and-hook — and it compounds hard. Starting from 500, Week 5, it puts us at ≈1,100 by Week 13 and ≈1,450 by Week 16, a credible launching pad for the waitlist.
When the target shifts: Once Week 16 opens the waitlist, the primary KPI tightens to waitlist-specific signups and moves to month-over-month growth tracking through the Runway phase (see §Weeks 17+).

Week 5: Announce & Hook (The Discovery)

Week 5 Content Pieces

Content	Channel	Format	Description
”In 1988, a Company Built a Device That Thought in Lists”	Blog	Essay (1500 words) + video	The KEC origin story. What is the Edgeware universe? Why did this company vanish? Why are we rebuilding it? Sets the narrative frame.
Project Page Launch	Hackaday.io	Full page setup	Overview, bill of materials, design philosophy, GitHub links. First Hackaday log: “Week 5: The Discovery.”
Introductory YouTube Video	YouTube	8-minute concept video	Voiceover narrative of finding KEC blueprints. Show the lore artifacts (vintage ads, design specs, cartridge labels). Tease the device. No build footage yet.
Reddit Announcement Posts	r/cyberdeck, r/RetroComputing, r/worldbuilding	Self-posts (3 variations)	Introduce the project with appropriate context for each community. Cyberdeck: “We’re rebuilding a fictional 1988 handheld from blueprints.” Retro: “A device that never existed.” Worldbuilding: “Meet the Kinoshita Electronics Consortium.”
Announcement Toot/Post	Mastodon, Bluesky	Short posts + images	”We found blueprints for a fictional device from 1988. We’re rebuilding it. Here’s why.” Link to blog and Hackaday.
Newsletter Launch	gwpdispatch.com	Email (weekly digest)	Announce the series. Subscribers get early access to lore.

Week 5 Goals

Awareness: Introduce KN-86 to five core subreddits
Narrative Hook: Establish the “fictional archaeology” premise
Community Seeding: Get early engagement in r/cyberdeck, r/RetroComputing
Platform Presence: Establish on Hackaday.io, blog, YouTube, Reddit, social media

Week 5 Metrics to Track

Blog post views
Reddit post upvotes + comments (depth of engagement)
Hackaday followers
Email subscribers
YouTube video views
Social media impressions

Week 6: Lore Deep-Dive

Week 6 Content Pieces

Content	Channel	Format	Description
”The Kinoshita Electronics Consortium: 1978–1992”	Blog	Essay (2000 words)	Full corporate history. Fictional but internally consistent. Financial timelines, product lines, the Edgeware connection, the mysterious closure.
Hackaday Log: “Week 6: Components Have Stories”	Hackaday.io	Build log	No assembly yet, but component sourcing begins. Show the YM2149 PSG, the Elecrow 7” IPS panel, Kailh Choc v1 switch samples. Each component is a character in the story.
”Why We’re Not Building a Modern Device”	Blog	Essay (1200 words)	Defend the design choices. Why Lisp? Why no QWERTY? Why 1988? Why constraints? Subtle polemic against “progress” narratives in hardware.
Cartridge Label Design (Concept)	Mastodon, Bluesky, Blog	Images + process notes	Show cartridge label prototypes. Each label encodes lore (KEC serial numbers, mysterious stamps, Edgeware insignia). Explain the Rosetta Stone concept.
Reddit: “Why Kinoshita Electronics Makes Sense in 1988”	r/RetroComputing, r/worldbuilding	Self-post	History of 1988 as a design era. Osborne, Grid Compass, Psion. Why would KEC have designed the KN-86 then?
Weekly Dispatch Newsletter	gwpdispatch.com	Email	Recap of week 5 announcements, teaser for week 6 lore, call-to-action to join Hackaday followers.

Week 6 Goals

Narrative Deepening: Flesh out the KEC universe with historical depth
Community Building: Move from announcement to sustained engagement
Design Philosophy: Explain the “why” behind every choice
Visual Identity: Establish the cartridge label aesthetic

Week 6 Metrics

Blog readership growth
Hackaday log views
Reddit post engagement (especially r/worldbuilding)
Social media reach on cartridge label posts

Week 7: Component Sourcing Begins

Week 7 Content Pieces

Content	Channel	Format	Description
”Designing the Keys: Why Choc v1 + MBK Fits a Lisp Grammar”	Blog + YouTube	Dual format (essay + video)	The decision path from fictional “Alps SKFL” lore to the real Kailh Choc v1 switch + custom MBK keycap design. Keycap-set layout reasoning, legend conventions, tactile feedback for list operations.
Hackaday Log: “Week 7: BOM Walkthrough — Pi Zero 2 W, YM2149, Elecrow 7” IPS, Choc v1”	Hackaday.io	Build log	Unboxing photos of the actual prototype BOM. Write about the tradeoffs between era-authentic and available-today, and why each component earned its spot.
Reddit: “A Custom MBK Keycap Set for a Lisp Machine”	r/MechanicalKeyboards	Self-post	Share the keycap-set design and legend conventions. Invite feedback on legend clarity, layout, and switch/keycap pairing for a non-QWERTY board.
Sound Design Preview	YouTube + Mastodon	90-second video clip	Early emu2149 audio, showing the YM2149F aesthetic. No gameplay context yet, just pure sound. “This is what 1988 sounds like."
"Thinking in Lists: Why Lisp?”	Blog	Essay (1500 words)	Philosophical justification for the CAR/CDR/CONS interface. Not a programming language tutorial—a meditation on how structure shapes thought.
Weekly Newsletter	gwpdispatch.com	Email	Recap, subscriber-exclusive cartridge label preview, link to all week 7 content.

Week 7 Goals

Technical Credibility: Show that component sourcing is thorough and thoughtful
Community Expertise: Position as thoughtful stewards of retro tech
Interaction Design Philosophy: Begin explaining the interface paradigm
Audio Aesthetics: Introduce the sound design as a central element

Week 7 Metrics

YouTube video views (sound preview)
Reddit engagement in r/MechanicalKeyboards (comments on switch discussion)
Blog traffic (component sourcing story)
Hackaday followers growth

Week 8: Proof of Concept — First Pixels

Week 8 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 8: Breadboard Magic — First Pixels”	Hackaday.io	Build log	Breadboard proof-of-concept showing LED matrix lighting up. Show the circuit design. Photos of jumper wires and the first amber glow.
YouTube: “Week 8 — Breadboard to Reality”	YouTube	5-minute video	Time-lapse of breadboard assembly, first boot sequence, the moment the display lights. Include the YM2149F playing the first audio. Narrative voiceover about “bringing the ghost to life.”
Blog: “The Moment We Brought Kinoshita Electronics Back to Life”	Blog	Reflection essay (1000 words)	Emotional/philosophical reflection on the breadboard working. What does it mean when a fictional device starts to respond? What are we actually building?
Reddit: “Proof of Concept — The First Boot”	r/cyberdeck, r/RetroComputing	Self-post + video link	Show the breadboard working. Invite cyberdeck community to weigh in on design choices, next steps.
Mastodon/Bluesky Teaser Clips	Social media	15-second video loops	The moment the display lights. The first audio. “It’s alive.” Simple, satisfying, viral-friendly.
Newsletter: “The Moment We Brought a Fictional Device to Life”	Email	Recap + reflection	Recap all week 8 content. Subscriber-exclusive sneak peek at week 9 (cartridge design).

Week 8 Goals

Momentum: The project is no longer abstract—it’s real hardware producing light and sound
Emotional Connection: This is the moment the fiction becomes tangible
Proof of Feasibility: Show that the design actually works
Community Excitement: Build anticipation for the next phase

Week 8 Metrics

YouTube video views (breadboard demo)
Reddit upvotes/comments (proof-of-concept post)
Blog engagement (reflection essay)
Social media reach (video clips on Mastodon/Bluesky)
Hackaday followers

Week 9: Display & Audio Integration

Week 9 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 9: Amber Glow — Display Calibration”	Hackaday.io	Build log	Photos of the Elecrow 7” IPS panel at different brightness levels with the amber-on-black color lookup applied. Aesthetic decision-making. Why amber? (Readability, aesthetics, ‘88 authenticity.)
Blog: “The Color of Code: Why Amber?”	Blog	Essay (1200 words)	Deep dive into monochrome displays, readability research, the aesthetics of constraint. Tangential history of green screens, amber screens, CRT technology. Why color would dilute the experience.
YouTube: “The Sound of Code: YM2149F in Action”	YouTube	4-minute video	Screen captures of nOSh booting, with the YM2149F providing the soundtrack. Show the connection between code execution and audio output. No chiptune nostalgia—pure Tangerine Dream aesthetic.
Blog: “Not Chiptune: The YM2149F and Minimalist Electronic Music”	Blog	Essay (1500 words)	Audio philosophy. Tangerine Dream references. Why we chose this specific chip. How sound design is interface design.
Reddit: “Display Color & Readability: Why Amber?“	r/RetroComputing	Self-post	Discuss the choice with retro computing community. Invite discussion on color, contrast, historical accuracy vs. aesthetics.
Mastodon: 16-Second Sound Design Loop	Social media	Audio-focused post	Just the YM2149F, beautifully captured. No explanation. Let people discover it. #YM2149F #KN86
Newsletter	Email	Weekly recap	All week 9 content, plus subscriber-exclusive: early draft of the first cartridge label (ICE BREAKER v3.2).

Week 9 Goals

Aesthetic Coherence: Show that display and audio are unified by design philosophy
Sound as Interface: Establish audio as a first-class design element
Historical Depth: Justify each choice through research and philosophy
Community Discussion: Engage r/RetroComputing on color and readability trade-offs

Week 9 Metrics

Blog traffic (amber and YM2149F essays)
YouTube views (sound design video)
Social media engagement (16-second audio clip)
Reddit comments (display discussion)

Week 10: Switch Feel Testing

Week 10 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 10: The Tactile Grammar of Choc v1”	Hackaday.io	Build log	Photos and descriptions of switch mounting on the prototype PCB. Close-ups of Choc v1 actuation. Tactile-feel comparison of the candidate switches we tested.
YouTube: “Why Choc v1? A Switch Feel Comparison for a Lisp Deck”	YouTube	6-minute video	Audio closeups of the switch actuation sound. Slow-motion footage of the keystroke. Comparison with Cherry MX, Alps-like, and other low-profile switches. Why tactile feedback matters for Lisp operations.
Blog: “Touching Code: Why Switch Feel Matters in List Thinking”	Blog	Essay (1400 words)	Phenomenological meditation on tactile feedback and interaction design. How the physical click of a switch informs cognition. Why mechanical keyboards are not nostalgia—they’re interface philosophy.
Reddit: “Designing For Switch Feel, Not Nostalgia”	r/MechanicalKeyboards	Discussion thread	Post the YouTube video. Ask: “If you were designing a board around Lisp — CAR/CDR/CONS instead of QWERTY — which switch profile and keycap family would you pick, and why?” High engagement potential without any vintage-sourcing claims.
Mastodon/Bluesky: Close-Up Switch Photos	Social media	High-quality images	Extreme macro photography of switch actuation. Beautiful, tactile, satisfying to look at.
Newsletter	Email	Recap	All week 10 content, plus exclusive: the mechanical keyboard manifesto (why we didn’t choose modern switches).

Week 10 Goals

Technical Depth: Show expertise in switch selection and mounting
Community Engagement: Tap into the mechanical keyboard community’s passion
Philosophy: Connect tactile feedback to interface design
Aesthetics: Publish beautiful close-up photography

Week 10 Metrics

YouTube views (switch feel comparison)
r/MechanicalKeyboards engagement (high expected)
Blog traffic (phenomenology essay)
Social media reach (macro photography)

Week 11: Enclosure Design & 3D Printing

Week 11 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 11: Iterating on Form — CAD to Reality”	Hackaday.io	Build log	CAD renderings of enclosure design. Photos of 3D print iterations, failed prints, refinements. Show the design intent: compact, holdable, with a satisfying cartridge slot.
YouTube: “From CAD to Physical: The Enclosure Design Story”	YouTube	7-minute video	Time-lapse of 3D printing. Multiple iterations. The moment the first successful print emerges. Beauty in the imperfection.
Blog: “Designing for Constraint: The KN-86 Form Factor”	Blog	Essay (1200 words)	Explain the design philosophy. Why this size? Why this grip? Why the cartridge slot is a central design element. How physical form shapes interaction.
Reddit: “Thoughts on Our Enclosure Design? Help Us Refine”	r/cyberdeck	Self-post with CAD images	Solicit feedback from the community. Make it collaborative. “We’re refining the design. What would you change?”
Mastodon/Bluesky: 3D Printing Time-Lapses	Social media	Video loops	Satisfying footage of print layer-by-layer. No dialogue needed. Just the process.
Newsletter	Email	Recap	All week 11 content, plus subscriber-exclusive: CAD files available for download (for non-commercial use).

Week 11 Goals

Design Iteration: Show the messy reality of hardware design (failed prints, refinements)
Community Collaboration: Invite feedback before final design
Form as Philosophy: Explain that enclosure design is not aesthetic—it’s functional and philosophical
Accessibility: Share CAD files with community

Week 11 Metrics

YouTube views (3D print time-lapse)
Reddit engagement (design feedback thread)
Blog traffic (form factor essay)
CAD file downloads (if metrics available)
Social media reach (satisfying time-lapse videos)

Week 12: Cartridge Design & Label Artwork

Week 12 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 12: The Cartridge as Artifact”	Hackaday.io	Build log	Design and manufacture of the physical cartridges. Label artwork. Printing samples. Show the Rosetta Stone concept: labels encode both technical specs and lore.
Blog: “The Cartridge Label as Rosetta Stone: A Design Philosophy”	Blog	Essay (1500 words)	Deep dive into why cartridge labels matter. How they’re both functional (ROM chip reference, load specifications) and narrative (KEC serial numbers, Edgeware stamps, mysterious metadata). The label is where fiction and hardware collide.
YouTube: “The First Cartridge: ICE BREAKER v3.2”	YouTube	3-minute video	Show the cartridge design, label printing, the moment a cartridge slides into the slot for the first time. Slow-motion. Satisfying click.
Itch.io Announcement	Itch.io	Project page launch	Announce the desktop emulator coming in week 14. Preview the cartridge label designs. Community game jam announcement: “Create Lisp games for the KN-86.”
Reddit: “Cartridge Label Design — Where Fiction Meets Function”	r/worldbuilding, r/cyberdeck	Dual self-posts	For r/worldbuilding: “The label is lore.” For r/cyberdeck: “The label is specification.” Show how the same artifact serves both purposes.
Mastodon/Bluesky: Label Artwork	Social media	Beautiful images	Close-ups of the cartridge labels. Typography, color, mysterious iconography. “This is what 1988 looks like.”
Newsletter	Email	Recap	All week 12 content, plus subscriber-exclusive: early access to ICE BREAKER cartridge label full-res files. Call-to-action: “Join the game jam.”

Week 12 Goals

Narrative Materialization: The label is where the fiction becomes tangible
Design Coherence: Show that every element—from the silicon to the label—serves the same philosophy
Community Creativity: Launch the itch.io game jam to invite developers
Aesthetics: Publish beautiful label artwork

Week 12 Metrics

Blog traffic (Rosetta Stone essay)
YouTube views (cartridge insertion video)
Itch.io project followers
Reddit engagement (dual posts on lore + function)
Social media reach (label artwork)
Game jam signups (if tracked)

Week 13: nOSh Boot Sequence & Runtime

Week 13 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 13: The First Real Boot — nOSh Lives”	Hackaday.io	Build log	Screen captures of the nOSh boot sequence on the KN-86 hardware. Show the nOSh runtime working. Lisp REPL. Command structure. The moment the device becomes fully functional.
YouTube: “The nOSh Boot Sequence: A Lisp REPL in Your Hand”	YouTube	5-minute video	Screencast of the boot. Show the progression: system startup, Lisp initialization, first REPL prompt. Commentary on what’s happening at each step. Why Lisp? Why this interface?
Blog: “nOSh: The Minimal Lisp Operating System at the Heart of the KN-86”	Blog	Essay (1500 words)	Technical explanation of the custom OS. Show how the interface paradigm (CAR/CDR/CONS) is baked into the system. What does it mean to have an OS that thinks in lists?
Reddit: “We Just Booted a Lisp OS on Real Hardware”	r/gamedesign, r/cyberdeck	Self-post with video link	This is the moment the device becomes real. Community excitement.
Mastodon/Bluesky: Lisp REPL Cursor	Social media	Animated GIF	The prompt blinking. Simple, meditative, hypnotic. “The heart of the KN-86.”
Newsletter	Email	Recap	All week 13 content, plus subscriber-exclusive: nOSh source code early access (for interested developers).

Week 13 Goals

Functionality Demonstration: Show the device working as an integrated system
Technical Credibility: Explain the nOSh runtime layer with depth
Interface Philosophy: Highlight how the OS embodies the design intent
Community Hype: This is a pivotal moment—the device is fully functional

Week 13 Metrics

YouTube views (boot sequence screencast)
Blog traffic (nOSh essay)
Reddit engagement (first boot post)
Social media impressions (blinking cursor animation)
Source code interest (if tracked)

Week 14: ICE Breaker Gameplay Preview

Dependency flag. Week 14 assumes ICE BREAKER is playable end-to-end on the desktop emulator. Per docs/marketing/product-evaluation.md, this is not yet true as of 2026-04-22. Josh is pursuing the engineering path in parallel. If ICE BREAKER is not playable by Week 13, Week 14 pivots to “OODA, made playable in the Bare Deck” — using the nOSh runtime only OODA demo as the public artifact, with ICE BREAKER previewed via design-doc walkthrough rather than live gameplay footage. Do not publish gameplay footage that has not been captured from a running build.

Week 14 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 14: ICE BREAKER — The OODA Loop Made Playable”	Hackaday.io	Build log	Gameplay screenshots captured from the desktop emulator (not mock-ups). Mechanics explanation (OODA Loop, three living systems: Network/Toolkit/Threat, Hot Swap cartridge mechanic). Show how the Lisp interface paradigm shapes tempo-based decision-making. Sound as the fourth system.
YouTube: “ICE BREAKER: Tempo as Skill”	YouTube	8-minute video	Gameplay footage showing OODA cycling. Voice-over explaining John Boyd’s decision cycle and how it translates to interaction design. Show Hot Swap mechanic in action (mid-mission cartridge swap). Three systems in concert. Sound design demo.
Blog: “ICE BREAKER Design: The OODA Loop Framework & Hot Swap Mechanic”	Blog	Essay (2000 words)	Deep design philosophy. Why OODA? How does tempo become playable? What are the three living systems and how do they feed the decision cycle? Why is Hot Swap a signature mechanic? Why is sound the fourth system?
Itch.io Desktop Emulator BETA	Itch.io	Game page	Release the desktop emulator (browser or downloadable). Host ICE BREAKER (playable for free). Include Bare Deck Terminal demo showing five nOSh runtime tabs. Let people experience the device without hardware.
Reddit: “We Built a Game Around John Boyd’s OODA Loop — Here It Is”	r/gamedesign, r/cyberdeck, r/indiegames	Self-post with itch.io link	Explain OODA framework. Why does a handheld terminal teach decision-making under pressure? How does Hot Swap change multi-phase game design? Why is Bare Deck relevant? Invite designers to think about tempo and constraint.
Mastodon/Bluesky: Gameplay Clips	Social media	15-30 second video loops	OODA cycling. Sound cues triggering decisions. Hot Swap in action. Satisfying list operations. “Tempo is skill.” “Threat advances. You decide. Network responds. That’s the loop.”
Newsletter	Email	Recap	All week 14 content, plus subscriber-exclusive: deep-dive into the three systems (Network threat model, Toolkit capability pool, Threat escalation). “How we designed a game around decision pressure.”

Week 14 Goals

Decision Framework Clarity: Explain OODA as the core gameplay pillar
Mechanic Showcase: Highlight Hot Swap as a signature design that makes multi-capability play tangible
System Architecture: Show the three living systems (Network, Toolkit, Threat) + sound as integrated gameplay engine
Community Access: Release emulator (with Bare Deck Terminal) so anyone can experience both the game and the empty-deck philosophy
Designer Engagement: Inspire game designers to think about tempo, constraint, and decision-making as primary mechanics

Week 14 Metrics

YouTube views (gameplay video)
Itch.io downloads (desktop emulator)
Itch.io plays (ICE BREAKER)
Reddit engagement (game design discussion)
Social media reach (gameplay clips)
Game jam submissions (if tracked)

Week 15: Prototype Assembly — First Working Unit

Scope note. Week 15 is the first working prototype milestone — a functioning Pi Zero 2 W + Elecrow 7” IPS LCD + Kailh Choc v1 input rig running nOSh end-to-end. This is not a production-ready unit. The enclosure may still be 3D-printed, the switch layout may still be a rev. Production-ready hardware targets Q4 2027.

Week 15 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 15: First Working Prototype”	Hackaday.io	Build log	Photos of the first functioning prototype. PCB soldering, Pi Zero 2 W wiring, Elecrow panel integration, 3D-printed enclosure, cartridge slot mock-up. Call out what is prototype-grade and what is production-grade.
YouTube: “From Emulator to Prototype — 15 Weeks Compressed”	YouTube	Time-lapse video	Montage of the emulator-first development arc followed by prototype assembly. Breadboard → PCB → components → enclosure → working unit. Be explicit: this is the first prototype, not the production device.
Blog: “Fiction Becomes Prototype: Reflections on the First Working Unit”	Blog	Reflective essay (1500 words)	Philosophical reflection on the arc so far. What have we learned moving from emulator to hardware? What’s still ahead on the runway to Q4 2027?
Reddit: “First Working KN-86 Prototype — The Fiction Boots”	r/cyberdeck, r/worldbuilding, r/RetroComputing	Comprehensive self-post	Summary of the project to date. Link to all 15 weeks of content. Thank the community for engagement. Preview Week 16’s prototype reveal + pre-order waitlist.
Newsletter: “15 Weeks In — The Prototype Boots”	Email	Recap + prototype news	Entire project summary. Subscriber-exclusive: behind-the-scenes photos of the first boot and reflections that didn’t make the public posts. Prime the list for Week 16 waitlist open.
Mastodon/Bluesky: Prototype Boot Clips	Social media	Video + carousel posts	Power-on sequence on real hardware. Close-ups of the amber display. Cartridge load. Short boot-sequence loops.

Week 15 Goals

Prototype Milestone: Publicly mark the first working Pi Zero 2 W unit running nOSh
Narrative Resolution: Reflect on what it means that the fiction now boots on real hardware
Community Gratitude: Thank the communities that made this possible
Momentum Building: Set up Week 16’s prototype reveal and pre-order waitlist open

Week 15 Metrics

Mailing list growth: +10% week-over-week (primary KPI)
YouTube views (prototype time-lapse)
Blog traffic (reflection essay)
Reddit engagement (comprehensive project post)
Social media reach (prototype boot clips)
Email engagement (full recap)

Week 16: Prototype Reveal & Pre-Order Waitlist Open

Scope note. Week 16 is not a product launch. It is the public reveal of the first working prototype and the opening of the pre-order waitlist. Hardware ships Q4 2027. All copy and goals in this week must be consistent with that timeline; do not use “complete,” “finished,” or “launched” language for the hardware.

Week 16 Content Pieces

Content	Channel	Format	Description
Hackaday Log: “Week 16: Prototype Reveal — Fiction Boots Hardware”	Hackaday.io	Build log	Photos of the first working prototype unit. All prototype systems functional. Show the device running the Bare Deck Terminal (and ICE BREAKER if playable — see Week 14 dependency flag). Be explicit about what is prototype-grade and what still needs production work.
YouTube: “KN-86 Prototype Reveal — A Fiction That Now Boots”	YouTube	8-minute reveal video	Showcase the working prototype. Walkthrough of the form factor, the interface, the sound design, the cartridge slot. Set expectations: this is the first prototype, production hardware ships Q4 2027, pre-order waitlist is open today.
Blog: “Prototype Reveal + Pre-Order Waitlist Open”	Blog	Announcement essay (1500 words)	The fictional device now boots on real hardware. What’s done, what’s left on the runway to Q4 2027, and what joining the waitlist means (exclusive build-log access, beta program lottery, pre-order priority). Clear primary CTA: waitlist signup.
Pre-Order Waitlist Landing Page	kn86-deckline.com	Web page	Dedicated page on kn86-deckline.com with the prototype reveal hero, waitlist signup form, FAQ (ship date, price band, what a waitlist slot entitles you to, what it does not). Email capture is the primary conversion.
Itch.io Community Game Jam Announcement	Itch.io	Page update	Announce the winning games from the community game jam. Celebrate the developers who created Lisp cartridges for the KN-86 emulator.
Reddit: “KN-86 Prototype Reveal + Waitlist Open”	r/cyberdeck, r/worldbuilding, r/RetroComputing, r/MechanicalKeyboards, r/gamedesign	Multi-subreddit announcement	Share the prototype reveal and waitlist link across all five key subreddits. Thank each community. Invite continued engagement through the Weeks 17+ pre-order runway arc.
Mastodon/Bluesky: Prototype Beauty Shots	Social media	High-quality product photography	Product photography of the prototype unit. In different contexts. In different lighting. Drive to the waitlist landing page. #KN86Prototype #KinoshitaElectronics
Newsletter: “The Waitlist Is Open”	Email	Reveal + waitlist CTA	Project recap. Waitlist announcement. Clear expectations: ship date, waitlist-holder perks, pre-order timing. Thank subscribers for 12 weeks of engagement and invite them to forward to one person.

Week 16 Goals

Prototype Reveal: Publicly mark the end of the announce-and-hook arc with a working prototype in hand
Waitlist Open: Establish the pre-order waitlist as the primary conversion surface going forward
Narrative Pivot: Move from “will this be real?” to “when does it ship?” — without claiming it has shipped
Community Recognition: Celebrate the developers who participated in the community cartridge jam
Runway Kickoff: Set up Weeks 17+ as the pre-order runway arc through Q4 2027

Week 16 Metrics

Mailing list / waitlist growth: +10% week-over-week (primary KPI)
Waitlist signups (absolute count; establishes baseline for pre-order conversion rate)
YouTube views (prototype reveal video)
Blog traffic (waitlist announcement)
Reddit engagement across all five subreddits
Social media reach (prototype photography)
Email engagement (waitlist reveal)
Itch.io game jam celebration

Weeks 17+ (through Q4 2027): Pre-Order Runway

The campaign does not end at Week 16. Hardware ships Q4 2027 — roughly 18 months of pre-order runway remain. This section defines the sustained cadence and the narrative arc that carries the audience from waitlist to shipping unit.

Narrative Arc (Phased)

Runway Phase 1 — “Prototype Hardening” (≈Weeks 17–30): Sustained build-in-public content as the prototype is refined. Focus: PCB revisions, enclosure iterations, keycap set finalization, cartridge slot design, nOSh runtime hardening. Emulator remains the public demo vehicle; prototype footage rolls out as milestones are hit.
Runway Phase 2 — “Beta Program” (≈Weeks 31–52): Invite a small beta cohort (waitlist lottery; limited seats) to test later-revision prototypes and early cartridges. Beta content (AAR posts, community interviews, unboxing clips) becomes the primary social proof engine. Pre-order window opens at a defined waitlist volume (target: TBD).
Runway Phase 3 — “Pre-Order & Production” (remaining months): Pre-orders live. Focus shifts to production content: tooling, assembly pipeline, QA, final-unit reveal, shipping readiness. Final content beats: unboxing-of-the-first-production-unit reveal, full ICE BREAKER + launch cartridge lineup showcase, ship-day announcement.

Sustained Cadence (per month during runway)

1× build-log post (Hackaday.io + cross-post) on a prototype milestone
1× community highlight (waitlist member interview, cartridge jam winner profile, or beta tester AAR)
1× design essay (Lisp paradigm, fiction-as-product, retrocomputing context)
1× newsletter issue (tight, focused — primary CTA is waitlist share)
Social cadence: 2–3 posts/week on Mastodon + Bluesky; 1 post/week on X/Twitter if still relevant at the time

The cadence tightens approaching pre-order open and loosens during production-tooling months. See Part C.

Primary Runway KPIs

Mailing-list / waitlist growth: +10% month-over-month (primary KPI — per-week growth is the announce-and-hook target; runway cadence moves to monthly tracking)
Waitlist-to-pre-order conversion rate (once pre-order window opens)
Beta-program retention (beta testers active at end of each month)
Content consumption (video watch-time, blog read-through, newsletter open rate)
Community health (Discord active users, cartridge jam submissions, unsolicited fan content)

Risk Guardrails (things we will not do on the runway)

No unverifiable ship-date commitments. Ship window = “Q4 2027” until a specific month is locked with production.
No gameplay footage from mock-ups. Every piece of gameplay content comes from a running emulator or a running prototype build.
No hardware spec claims outside CLAUDE.md. Every copy reference to hardware values points back to CLAUDE.md Canonical Hardware Specification.
No price commitments until production tooling and BOM cost are locked.

Part C: Ongoing Marketing Cadence

Operating Posture: Solo + Sub-Agents

This cadence is designed for one human operator (Josh) plus a rotating set of specialized sub-agents handling drafting, scheduling, and review. It optimizes for sustainability over the full Q4 2027 runway, not the first 16-week push. Every item on this calendar must be defensible on week 40, not just week 5.

Guiding principles:

One anchor post per week, not three. Anchor = Hackaday.io build log. Everything else rebroadcasts or extends the anchor.
Bi-weekly long-form, not weekly. Essays and lore posts alternate — a deep piece every two weeks, not one every week.
Every-other-week video. One YouTube publish every two weeks. Quality beats cadence; a missed week signals trouble. Eight videos across Weeks 5–20 is the target envelope.
Newsletter is weekly because it’s the primary KPI surface. A Friday dispatch is non-negotiable — that’s where the +10% weekly mailing-list growth metric lives.
Reddit is opportunistic, not scheduled. Anchor only r/cyberdeck at weekly cadence. Other subreddits get posted to when we have a specific artifact that fits their culture, not on a calendar.
Skip weeks are expected. A missed anchor post is recoverable; a broken cadence commitment is not. The calendar below describes a maximum sustained rate, not a minimum floor.

Weekly Content Calendar (Sustained Cadence, Weeks 5–16 and beyond)

Pillar	Monday	Wednesday	Friday
Build Log (anchor)	Hackaday.io log published	Reddit r/cyberdeck cross-post	—
Long-form essay	—	(biweekly) Lore, design philosophy, or interaction essay — one per fortnight, not per week	—
Social Media	Mastodon/Bluesky: WIP photo tied to Monday’s log	—	Mastodon/Bluesky: week-in-review post
YouTube	—	—	(biweekly) Video publish — one per fortnight
Newsletter	—	—	Weekly email dispatch (Friday evening) — primary KPI surface

Cadence summary:

Channel	Sustained rate	Notes
Hackaday.io	1 log / week	Anchor. If one slips, skip the week rather than shipping thin content.
Blog (long-form)	1 post every 2 weeks	Alternates between lore, design philosophy, and interaction essays.
Reddit (r/cyberdeck)	1 cross-post / week	Auto-linked to Monday’s Hackaday log — no separate copywriting.
Reddit (other subs)	Opportunistic	See “Opportunistic Reddit Posts” table below.
Mastodon / Bluesky	2 posts / week	One Monday WIP, one Friday recap. Combined across both networks.
YouTube	1 video every 2 weeks	~8 videos across Weeks 5–20. Quality ≥ cadence.
Newsletter	1 dispatch / week	Friday evening. Non-negotiable because of the primary KPI.
Discord	1 pinned summary / week	Friday summary post referencing the week’s outputs. No daily presence expected.

Opportunistic Reddit Posts (not scheduled):

Subreddit	Trigger	Target frequency
r/MechanicalKeyboards	A post is only scheduled when we have a keyboard-specific artifact (a switch teardown, a keycap closeup, a sound test).	~2 across the 12-week window.
r/RetroComputing	When a CP437 / 80×25 / fictional-1988-hardware angle can lead the post.	~2 across the 12-week window.
r/worldbuilding	When a lore essay or KEC fiction artifact is the subject.	~2 across the 12-week window.
r/gamedesign	When ICE Breaker gameplay video or OODA-loop writeup is ready.	~1 across the 12-week window.

Anti-pattern to avoid: Publishing to all four side-subreddits on a calendar. That produces thin, calendar-driven posts that damage reputation in each community. Post only when the artifact genuinely fits the sub.

Capacity Model

A rough weekly time budget for the sustained cadence, assuming sub-agents draft and Josh reviews:

Activity	Josh hours / week	Sub-agent load
Build log draft + photos	2	Copywriter agent drafts from raw notes
Reddit anchor cross-post	0.25	Auto-rebroadcast
Social (Monday + Friday)	0.5	Social agent drafts; Josh approves
Long-form essay (when biweekly cycle hits)	3 (averaged 1.5/wk)	Copywriter agent drafts; Brand reviewer agent lints
YouTube (when biweekly cycle hits)	4 (averaged 2/wk)	Video script agent drafts; Josh records & edits
Newsletter	1.5	Email agent drafts; Josh finalizes
Discord Friday summary	0.25	Auto-generated from week’s artifacts
Total (steady-state)	~7.5 hours/week	Sub-agents do the first draft on everything.

If the weekly budget exceeds ~10 hours, cut a channel — don’t ship thinner content. The sustained cadence only works if it’s protectable.

Escalation & Skip Protocol

One missed anchor post (Hackaday): Note it in the Friday newsletter; resume next week. No makeup post.
Two consecutive missed anchors: Marketing lead (Josh) flags in the Notion marketing task; assess whether cadence needs to be cut further.
Newsletter skip: Not acceptable without an agent-level incident. Primary KPI depends on this touchpoint.
YouTube skip: Expected and fine. A missed biweekly video is recoverable; a shipped-thin video is not.
Long-form essay skip: Reschedule to the next biweekly slot. Don’t “make up” by publishing two in one week.

Conclusion: The Philosophy of This Marketing Plan

This plan is not about selling hardware. It is about inviting people into a world.

The KN-86 Deckline succeeds if, at the end of week 16:

The cyberdeck community sees a fully documented, reproducible design that advances the state of the art
The retro computing community appreciates a thoughtful historical homage that respects constraints as creative tools
The game design community understands that novel input paradigms can teach philosophy
The worldbuilding community recognizes that fiction can materialize into functional artifacts
The mechanical keyboard community celebrates the resurrection of a legendary switch technology
New audiences understand that hardware, narrative, and design philosophy can be unified in a single object

The device is the narrative. The narrative is the device.

Research Sources & References

Community Research (April 2026)

Competitive Product Research (April 2026)

Marketing & Platform Research (April 2026)

Document prepared: April 1, 2026 Project timeline: 18 weeks (total) / 12 weeks (marketing focus) Status: Ready for implementation