KN-86 Deckline — PR-FAQ

Great Western Productions · Working-backwards document · April 2026

Document status: Internal draft for executive alignment. Written as if published on launch day, per the Amazon working-backwards method. Specific price points, date, and unit counts are illustrative anchors for planning — revise before any external use.

Launch target: Q4 2027 (placeholder date in this draft: November 11, 2027).

PRESS RELEASE

Kinoshita Arrives: Great Western Productions Ships the KN-86 Deckline, the 1988 Personal Cyberspace Terminal That Was Never Built — Until Now

The retro-cyberpunk handheld debuts with four cartridge capabilities and a Lisp-native operating grammar. First production run of 2,500 units opens for order today.

SAN ANTONIO, TEXAS — November 11, 2027 — Great Western Productions today launched the Kinoshita KN-86 Deckline, the first handheld Personal Cyberspace Terminal to ship with a Lisp-native input grammar and a cartridge-based capability model. Reconstructed from blueprints left behind by the defunct Kinoshita Electronics Consortium (KEC) of Osaka — a company that designed but never manufactured the device in 1988 — the KN-86 ships today as functional hardware running functional software.

The Deckline is a game console — dedicated handheld hardware, cartridge-based software, the works. What makes it different is that the fiction is load-bearing. The device presents itself as a Personal Cyberspace Terminal designed by Kinoshita Electronics in 1988; that framing is not marketing veneer over a generic handheld, it’s the design brief the hardware was built around. Every decision — the Lisp grammar, the amber 80-column display, the DMG-compatible cartridge slot, the in-universe publisher mark on every cartridge — is part of the story the operator lives inside. The device itself carries the story.

The hardware: a 31-key field terminal housed in a ruggedized black Pelican 1170 hardcase, with a phosphor-warm 7” IPS display set into a 3D-printed lid bezel (AMBER #E6A020 default, WHITE / GREEN selectable per ADR-0034/0036), an integrated YM2149 PSG synthesizer, and a cartridge slot housing a full-size SD card carried in a clamshell sled (per ADR-0019). Every operation — from booting the device to completing a contract — is expressed through a Lisp grammar built into the nOSh runtime. The operator’s identity, credits, and reputation persist across every cartridge in the library through a Universal Deck State held on the deck’s microSD per ADR-0011.

The problem we set out to solve

A generation of computing enthusiasts have watched handheld hardware become smartphones in costumes. Game Boy nostalgia machines, OLED retro handhelds, SBC cyberdecks — they all ask the operator to accept modern conveniences wrapped in vintage shells. None of them ask the operator to think differently. The people who grew up imagining what a cyberdeck would feel like under their hands have, for thirty years, been handed commodity hardware with a retro sticker on the front.

The solution

The KN-86 Deckline is a purpose-built piece of personal cyberspace hardware. It thinks in lists. It speaks in a single voice — Cipher, the deck’s resident Companion Intelligence. It carries its own scarcity: the switches are Kailh Choc v1 with custom MBK low-profile caps; the cartridges are dye-sublimated phosphor-on-black two-piece clamshell shells (~58 × 65 × 8 mm) carrying a full-size SD card the operator can swap with a screwdriver; the display is a single Elecrow 7-inch IPS panel rendered by the KN-86 native framebuffer renderer in AMBER #E6A020 (default), WHITE, or GREEN phosphor on black — selectable from the SYS tab (ADR-0034/0036). One phosphor at a time. One surface. One continuous operational career that survives every swap of the cartridge in the back.

“We didn’t want to build another retro handheld. Retro handhelds are museums. We wanted to build the device that would have existed if a specific Japanese company had survived 1992. The KN-86 is not nostalgia — it’s archaeology. Every decision, from the Lisp grammar to the cartridge pinout, is what KEC would have shipped if they’d lived.”

— Josh Schairbaum, Founder, Great Western Productions

How it works

The operator boots the deck into the Bare Deck Terminal — five nOSh runtime tabs (STATUS, CIPHER, LAMBDA, LINK, SYS) that teach the Lisp grammar through small runtime bounties before any cartridge is ever inserted. Once a cartridge is seated, the deck’s mission board unlocks contract templates for that capability domain.

Four cartridges ship in the launch library. Each is published by a different in-universe KEC-era studio, each has its own operational identity, and each extends the operator’s Universal Deck State — so the credits earned running one capability carry into the next.

#	Cartridge	Publisher	Capability	One-line pitch
01	ICE BREAKER	Zaibatsu Digital (Osaka)	Network intrusion	Pack-in. OODA-loop network penetration at tempo — extract the data before the ICE converges.
02	DEPTHCHARGE	Cascade Softworks (Seattle)	Maritime reconnaissance	Pilot an autonomous submersible through contested waters where sound is the interface.
03	NEONGRID	Edgeware Systems (Tokyo) — KEC first-party	Spatial navigation / operator training	The onboarding cartridge. District traversal, contact networks, dead-drop protocols.
04	BLACK LEDGER	Bureau 9 Technical Services	Forensic accounting	Trace transaction trees and shell-company topologies. Where ICE Breaker is tempo, Black Ledger is patience.

Multi-phase contracts span capability domains. An ICE Breaker SABOTAGE of a financial target triggers a Black Ledger audit phase. A Depthcharge dead-drop unlocks a SURVEILLANCE IMPLANT run. The more cartridges an operator owns, the more cross-domain contracts the mission board generates — and the highest-paying work in the Deckline’s economy is available only to operators carrying the full launch library.

What an operator said

“I have a 9-to-5, a commute, and two kids. I bought the Deckline because I wanted something that didn’t pretend to be a phone. Three weeks in, I can feel my brain reaching for CAR and CDR the way it used to reach for Ctrl-F. I don’t know if that’s healthy. I know I’m not putting it down.”

— “coyote_7,” operator, Seattle

Availability

The Kinoshita KN-86 Deckline is available starting today at gwpworkshop.com.

KN-86 Deckline (with ICE BREAKER pack-in cartridge): $499 USD
Individual launch cartridges (DEPTHCHARGE, NEONGRID, BLACK LEDGER): $39 USD each
Launch Library Bundle (Deckline + all four cartridges): $599 USD

First production run: 2,500 units. Waitlist for Production Run 2 (Q2 2028) opens the moment the first run ships.

EXTERNAL FAQ

Q: Is this a game console? Yes, honestly. It’s a dedicated handheld, it takes cartridges, and the software it runs includes gameplay. The distinction the KN-86 makes is not that it’s something other than a game console — it’s that the fiction is elaborate enough that the device itself carries the story. The hardware, the Lisp grammar, the amber display, the in-universe publisher mark on every cartridge — these aren’t branding on a generic console. They’re the artifact. When you pick up the Deckline you’re not using a console that has lore; you’re operating a 1988 Kinoshita terminal reconstructed from blueprints, and everything it asks you to do is what that terminal was designed to do.

Q: What do I actually do with it? You take contracts from the mission board. A contract is a structured piece of work that pays credits and accrues reputation. The domain depends on the cartridge you have loaded — network intrusion, forensic audit, maritime recon, or city navigation. You can complete single-cartridge contracts or chase multi-phase contracts that require physically swapping cartridges mid-mission. Operators who own all four launch cartridges unlock the full cross-domain mission board.

Q: I don’t have a numpad. Can I still play? Yes. The desktop SDL3 emulator (free, open-source) ships with full key remapping. The hardware deck has its own 31-key layout; the emulator lets any standard keyboard stand in. We publish the emulator alongside the hardware — the Deckline experience is not gated behind owning the device.

Q: Where does my save data live? Per-cartridge progress lives on the cartridge itself — a file on the cartridge’s own SD card, durable as long as the SD media. Your cross-cartridge identity — operator handle, credits, reputation, cartridge history, phase chain — lives on the deck. Swapping cartridges does not reset you. Inserting someone else’s cartridge in your deck loads their in-cart progress alongside your deck state. This was a deliberate design choice; it means cartridges can be traded, loaned, and gifted without losing the operator’s career.

Q: How long does it take to finish? The pack-in ICE Breaker cartridge has no “ending.” It has a career — procedurally generated contracts that scale with your reputation. A first-time operator will spend 15–25 hours reaching Rep 15 (Advanced Specialist tier). The full launch library, played across multi-phase campaigns, is an 80–120 hour experience before the mission board starts recycling templates.

Q: Will there be more cartridges? Yes. Ten additional cartridges are planned across the capability taxonomy (Operations, Commerce, Navigation, Strategy, Knowledge, System). Release cadence is one new cartridge per quarter through the end of 2029. The next cartridge after launch will be announced at Month 3.

Q: Can I write my own cartridge? Yes. Cartridges are authored in embedded Lisp on the Fe virtual machine and compiled to a .kn86 binary. The full FFI surface (54 primitives — text-puts, draw-sprite, spawn-cell, drill-into, advance-phase, and so on) is documented in ADR-0005. The compiler toolchain ships free alongside the emulator. Community-authored cartridges that meet our publishing bar will be featured in the official catalog.

Q: Is there multiplayer? Yes, via link cable (3.5mm TRRS, 4-pole). Two decks connected by link cable can run asymmetric cross-cartridge operations — one operator penetrates a network (ICE Breaker), the other defends it (Sysop Mode). Peer discovery is proximity-only. There is no internet multiplayer. This is deliberate.

Q: Why so expensive? Because it’s hand-assembled in a limited run, with a custom enclosure, a mechanical keyboard, a hardware cartridge slot, and premium components. Playdate launched at $199 and Analogue Pocket at $249; both had larger production runs and were assembled in East Asia at scale. The KN-86’s first production run is 2,500 units, manufactured and assembled in-region. We price it honestly.

Q: What’s the battery life? Roughly 4–5 hours with the 7-inch display lit, and 10–12 hours in display-off / electronics-only use, on three swappable 18650 cells driving an integrated UPS module — the deck runs while it charges. Standby is measured in weeks. The deck charges from a 12.6 V barrel-jack adapter, and the onboard battery monitor drives the on-screen fuel gauge.

Q: Is the nOSh runtime open? The emulator is open-source (MIT). The nOSh runtime is source-available under a non-commercial license. Every platform decision is documented in ADR-0001 through ADR-0014. We want operators to understand the system they are operating.

INTERNAL FAQ

Q: What is the size of the addressable market? The primary audience is the cyberdeck / DIY electronics community (active engagement ~50K–100K globally; strongest surfaces are Hackaday.io and r/cyberdeck). Secondary audiences — worldbuilding / transmedia, retro computing, indie game / interaction design, mechanical keyboard — total roughly 250K warm prospects across all five. To sell out Production Run 1 at 2,500 units, we need 1% conversion against that warm audience. Panic hit comparable conversion with Playdate. This is a realistic number for a niche-native launch, not a heroic one.

Q: Why launch in Q4 2027, and why November 11? Q4 2027 is the hardware ship target per the canonical spec. November specifically because: (a) holiday gifting tailwind; (b) the November indie-hardware cycle is where Analogue, Teenage Engineering, and Panic have competed since 2020 — we want the press oxygen of that cycle, not April’s; (c) it gives us 18 months of runway from current emulator-BETA milestone to final hardware. November 11 is illustrative; the actual launch date will be fixed at BOM-lock in Q2 2027.

Q: What happens if the hardware slips? The emulator is the hedge. If the Pi Zero 2 W + Elecrow hardware slips past Q4 2027, we ship the emulator at zero cost and the cartridges as standalone .kn86 binary downloads, then move hardware to Q2 2028. The fiction layer and capability model hold regardless. The transmedia story does not slip — because the story was never gated on the hardware being in hand.

Q: Why ICE Breaker as the pack-in, and not one of the others? ICE Breaker is the strongest possible first impression. The OODA loop, the Hot Swap mid-mission cartridge mechanic, and the parallel Network/Threat/Toolkit/Sound systems are the Deckline’s signature design choices — and ICE Breaker is the cartridge where they land hardest. Every operator who boots the deck plays ICE Breaker first. If the operator does not feel the Deckline’s identity in their first ICE Breaker session, we have failed the launch. The ICE Breaker onboarding sequence is the most-tested, most-reviewed, and most-revised piece of software in the launch package.

Q: Why four cartridges at launch and not six? Six was our original plan. We stopped at four after paper-prototype sessions showed that operators presented with six cartridges at first boot experienced a paradox-of-choice failure mode: insert one, play fifteen minutes, suspect they were missing something, swap, repeat, never settle. Four cartridges is the smallest library that covers the cross-domain phase chain (intrusion + accounting + navigation + reconnaissance) and demonstrates the capability-model value proposition without overwhelming the first-day operator.

Q: What is the single biggest risk? The Lisp grammar being skin-deep. The April 2026 Paradigm Audit found that 12 of the original 14 module designs treated keys as renamed generic controls rather than as a transferable Lisp grammar. The Paradigm Revisions have been implemented across all four launch cartridges, but transferability is still the critical pre-launch QA test: an operator who internalizes CAR / CDR / CONS / LAMBDA semantics in ICE Breaker must be able to carry that intuition to NeonGrid without re-learning. If the QA agent cannot validate this, we do not ship.

Q: What is the second-biggest risk? Cartridge manufacturing economics. Custom two-piece clamshell shells (carrying a commodity SD card per ADR-0019) at 2,500-unit volume are the single largest line item in the cartridge BOM. If per-cartridge COGS — shell + SD card + label + assembly — cannot come in under $12, the $39 SRP breaks and the library-bundle pricing becomes loss-making. The SD card and the bridge IC are commodity (the bridge IC is a one-time device-side line item from the ADR-0018 hub topology, not per-cartridge); the per-cartridge variable is dominated by the injection-mold tooling amortization against the Run 1 unit count and the per-shell SD provisioning cost.

Q: What is the third risk? Cipher’s voice drifting. The worldbuilding depends on Cipher — the deck’s resident Companion Intelligence — speaking in a single voice across every cartridge, every firmware patch, and every community-authored module we endorse. If Cipher’s voice drifts between cartridges, the deck feels composite instead of singular. Cipher voice style and vocabulary are locked in the Cipher Voice Style Guide, and every cartridge PR runs a grammar-compliance check before merge.

Q: What does Day 1 success look like?

Production Run 1 sells out in under 30 days
Waitlist for Run 2 reaches 5,000+ by Day 30
Zero firmware-critical bugs in the first 72 hours
At least one front-page Hackaday feature and one Ars Technica retrocomputing-desk write-up
Operator sentiment on r/cyberdeck, Hackaday comments, and the Discord #operators-lounge channel skews toward “I get it” rather than “I don’t get it”

Q: What does Year 1 success look like?

7,500 decks in operator hands (Runs 1 + 2 + 3)
4+ community-authored cartridges published under the official imprint
1+ sustained press relationship established with the craft-hardware press (Hackaday, Ars Technica, Make:)
First two-deck link-cable tournament run at Hackaday Supercon or DEF CON
Cartridge #5 shipped on schedule at Month 3, #6 at Month 6

Q: What happens after Launch Day 1?

Week 1: Emergency response. QA monitors Discord, return queues, mechanical-failure reports.
Weeks 2–4: Firmware 1.01 patch; first community-authored cartridge spotlight.
Month 2: Production Run 2 ordering opens (target: 5,000 units, ships Q2 2028).
Month 3: Cartridge #5 announced and dated.
Month 6: First KEC Universe anniversary event — Null dispatch, lore drop, community cartridge-jam winners promoted to official releases.
Year 2: Sustained release cadence; organized link-cable tournament circuit; production run 4.

Q: What kills the project? Three scenarios, in order of likelihood: (1) The Lisp grammar fails transferability QA and the launch slips into Q2 2028 while we rework the affected cartridges. (2) Cartridge COGS comes in above $12 and either SRP goes up or margin goes underwater. (3) A sustained PR incident around the fiction layer — someone credibly argues that the KEC archaeological frame is misleading or culturally insensitive — forces us to either restructure the narrative or withdraw it. All three are mitigable with current planning; none are zero-probability.

Document owner: Josh Schairbaum, Great Western Productions Status: Draft for internal alignment. Revise before external distribution.