KN-86 Deckline: Working-Backwards PRFAQ

Great Western Productions · Working-backwards document · 2026-07-11

Launch target: Late April 2027, my 50th birthday, one year to the day from when the build started.

What launches that day: one finished KN-86 Deckline, built and working. The full hardware design and the desktop emulator go public. Selling units is a separate, later decision. The eventual goal is a profitable production run and a small line of related devices.

Hero order (what leads the doc): 1) what you do, the missions and the capability model; 2) the device you hold; 3) the world it is set in.

Fiction: the Amber Circuit, a cyberpunk sprawl of identity-less operators who run contracts for scratch. The name is a double meaning: the amber phosphor, and the circuit operators run like a touring route. Kinoshita Electronics Consortium is the name on the deck; Edgeware is the company watching from behind it. The story follows the operators.

Voice contract (stop-slop): state what a thing is and does, and let the reader judge the significance. No em dashes. No “X, not Y” comparisons. No treating the device as a person. No claim the product does not actually make. Review the ADRs before describing any functionality.

PRESS RELEASE

Great Western Productions unveils the KN-86 Deckline, a handheld terminal for running contracts as an operator in the world of The Amber Circuit

The deck generates the missions. Swappable capability cartridges and a set of built-in Lisp programs are how you solve them. The first unit is built and running, and the hardware design plus a free emulator are public today.

SAN ANTONIO, TEXAS. April 2027. Great Western Productions today released the Kinoshita KN-86 Deckline, a handheld terminal you operate under an alias in a cyberpunk sprawl. In this world you have lost your legitimate identity, and the deckline is the one economy that will still hire you. The deck listens for contracts over a stealth mesh network and assembles each one on the spot. You solve them with capability cartridges you slot into the back and a set of Lisp programs built into the device. Every job you clear pays credits, raises your reputation, and goes into the deck’s permanent record of the operator you are becoming.

The complete build is public as of today: schematics, bill of materials, enclosure files, and the nOSh runtime source, alongside a free desktop emulator that runs the same software on any computer. One finished hardware unit exists, assembled, flashed, and in daily use as the reference build.

What you do. You work as an operator. The deck runs a mission board, and it does not ship a fixed list of missions. It generates them. It takes the capabilities you own, your reputation, your history, and a random seed, and it composes a contract to fit. Clear the contract and you earn credits and reputation. Reputation raises the ceiling on how hard the next jobs can be. Credits buy upgrades to the programs you work in. You cannot buy standing; you earn reputation only by doing the work.

Two kinds of software decide what a contract can ask of you.

Capability cartridges are the domains of work. Slot one in and the board can generate missions in that domain, and a running mission can call the cartridge mid-job. Four ship at launch:

ICE BREAKER. Network intrusion. Break the ICE and get into a target.
DEPTHCHARGE. Sonar and submersible piloting. Run a drone through contested water to reach a jack you cannot walk to.
BLACK LEDGER. Forensic audit. Trace money through shell companies and reconstruct what happened.
NEONGRID. Grid navigation and operator training. This is the cartridge that teaches the Lisp key grammar.

Built-in programs are the tools you always have, cartridge or no cartridge. Thirteen ship inside the deck. Among them: CONDUIT, the network client you drive once you are through the ICE; Kinoshita Kommander, a two-panel file browser where exfiltrated data lands; and AmberCalc, a terminal spreadsheet in the VisiCalc line. A cartridge can feed a program but never locks you out of one. BLACK LEDGER drops its findings into AmberCalc. ICE BREAKER drives a CONDUIT session.

The paying jobs cross domains. One contract might have you pilot a DEPTHCHARGE drone to an undersea data jack, break the ICE there with ICE BREAKER, open a session in CONDUIT, work through the mount in Kinoshita Kommander, find the fraudulent rows in AmberCalc, and carry the evidence out to the buyer who commissioned it. When a job needs a cartridge that is not in the slot, the deck stops and asks you to swap it in, and the clock keeps running while you do.

All of it lands in Universal Deck State: your handle, your credits, your reputation, the cartridges you have run, the jobs in flight. It lives on the deck. There is no cloud account. It is the record of the operator you have made.

With no cartridge in the slot the deck still works. A Bare Deck Terminal gives you seven tabs, every built-in program one keypress away, and a Lisp prompt, with small paid tasks that teach the grammar.

The device is built from seven parts:

A split, 34-key mechanical keyboard. Kailh Choc v1 switches, MBK keycaps, and a trackpoint set between the keys on each half. The left half carries the fourteen-key Lisp function block, one legend to a key: CAR, CDR, CONS, FN, APPLY, QUOTE, EVAL, and the rest, plus the deck’s four navigation verbs. You build expressions by pressing them. The right half carries the digits and punctuation. There is no QWERTY block.
A 7-inch primary display. An amber grid on black. Body text, tables, and gameplay render at 8x8 cells, scaled up for headlines and numbers. Amber is the default; white and green are selectable.
A second amber display. A narrow strip above the keyboard, on its own driver. It carries the deck’s status line and CIPHER, the deck’s synthetic voice. CIPHER speaks only here.
Cartridges. Each one is a two-piece clamshell sled about the size of a matchbook, holding a full-size SD card that the deck reads as storage. You can open the shell with a screwdriver and re-flash the card. Every cartridge carries the label of the studio that published it.
Sound. A YM2149 PSG synthesizer, emulated in software and run through a stereo audio codec. It plays in mono through a 2-inch built-in speaker and in stereo through a 3.5 mm headphone jack.
The case. A stock Pelican 1170 hardcase. 3D-printed panels hold the displays, the key plate, the cartridge slot, and the ports. The shell itself is never machined, so it still closes, latches, and travels.
The processor and power. A Raspberry Pi Zero 2 W, with a Pico 2 coprocessor running the audio and the second display. Three 18650 cells power it, charged over a barrel jack, for roughly four to five hours with the screen lit.

The world you operate in. The KN-86 is set in the Amber Circuit, the operators’ name for the work: a touring route of contracts you run for scratch and standing, across a cyberpunk sprawl a generation into the deckline’s revival. Here, a government ID is the key to everything legitimate: banking, work, housing, care. Operators are the people who have lost that ID and cannot get it back. The deckline is the one economy that still takes an identity-less worker, so they carry the device, run contracts under an alias, and keep their standing on the deck itself. Most are climbing toward a single purchase: a synthetic identity that buys them back into the legitimate economy.

They work over the AetherNet, a stealth mesh with no central server and no registered identities. The deck is a node on it, and it listens for contracts without logging into anything. That anonymity is the draw, and it is also the trap. Edgeware, the software house behind the deckline, designed the AetherNet and can see the whole mesh. To the public, the hardware is a Kinoshita Electronics Consortium product, and that lawful name is the front. Behind it, Edgeware runs the platform, watches the operators, and skims their pay.

The deck has a voice. CIPHER speaks in short amber fragments on the second display and warms as your reputation climbs. Whether it is a tool or something starting to notice you is the question the fiction turns on. The worst network defenses, the Black ICE, reach past the job to the operator at the deck and can do real physical harm. The first novelette set here, The Amber Circuit, follows an operator named Wreck up sixty-three days of contracts toward an offer they never knew was the prize.

Availability. As of today:

The desktop emulator is free and open-source. It runs the full nOSh runtime and all four launch cartridges on macOS and Linux, with key remapping for a standard keyboard.
The hardware design is public. Schematics, BOM, enclosure files, and the runtime source are all released, so anyone can build their own.
The reference unit is built. One Deckline exists, assembled and in daily use.

Selling units comes later. A small production run is planned, and its timing and price depend on demand over the coming year. The waitlist opens today at gwpworkshop.com.

Why I built this
Section titled “Why I built this”

I build this to explore game interfaces. I have never enjoyed games more than I did at the start of them, on Atari BASIC, an early Apple IIe, and the monochrome software I grew up typing into. That is the feeling the Deckline goes after: a machine you operate directly, in text, where the interface itself is the thing you play.

The last console I loved without reservation was the original Game Boy. Most of what came after copied its shape and kept adding resolution. Today’s consoles lean on visual spectacle, and much of the time the spectacle is covering for thin story and thin play. I wanted to work the other way: strip the screen down to amber text and find out whether the interface and the writing can carry the whole thing.

It is also the project of my fiftieth year. I started it in April 2026, when I turned forty-nine, and set out to have a working deck in my hands one year later, on my fiftieth birthday. The date on this release is that birthday.

I would like to sell these. The honest reason it exists is that I wanted one, and the only way to find out whether the idea holds up was to build the real thing and use it. If it holds up, a production run follows, and maybe the other two devices I have in mind. Today it is built, it works, and it shipped when I said it would.

EXTERNAL FAQ

Q: Can I buy one today? No. The design and the emulator are public and one reference unit is built. A production run is planned but not scheduled. The waitlist opens today, and pricing follows demand.

Q: Is this a game console? Yes. It is dedicated hardware, it takes cartridges, and it runs games. What makes it its own thing is how much of the product is the world it is set in and the software stack that world runs on.

Q: What do I actually do with it? You play an operator taking contracts. The deck generates each contract from the capabilities you own, your reputation, and your history. You solve them with capability cartridges (network intrusion, forensic audit, sonar, navigation) and the programs built into the deck. Clearing jobs earns credits and reputation, and reputation opens harder work.

Q: I don’t own the hardware. Can I still play? Yes. The desktop emulator is free and runs the complete experience with a remappable keyboard.

Q: Why is the keyboard split, with no QWERTY? Because the input is a Lisp grammar. The left half is the fourteen-key Lisp function block, one legend per key; the right half is digits and punctuation. You build expressions by pressing operators. When a job needs you to type words, the right-hand digit keys work like an old Nokia phone: T9-style multi-tap with word completion, so text entry never needs a full keyboard.

Q: Where does my progress live? Per-cartridge save data lives on that cartridge’s own SD card. Your operator identity (handle, credits, reputation, history) lives on the deck as Universal Deck State. Swapping cartridges never resets you.

Q: Can I write my own cartridge? Yes. Cartridges are written in KEC Lisp and packaged into a .kn86 file. The toolchain ships free with the emulator, and the runtime primitives are documented.

Q: Is there multiplayer? Two decks can link by cable for asymmetric play, one operator running a target and the other defending it. Discovery is proximity-only. There is no internet multiplayer.

Q: What’s the sound? A YM2149 PSG synthesizer, emulated in software. Mono through the built-in speaker, stereo through the headphone jack.

Q: Is the software open? The emulator is open-source. The nOSh runtime is source-available. The hardware design is public.

INTERNAL FAQ

Q: Why launch on the birthday, ahead of the Q4 2027 hardware ship target? This launch marks a personal milestone: a working device, one year to the day from the start. The canonical hardware ship target (Q4 2027) is for a production run of many sellable units. Those are two different events. Late April 2027 is the capstone: design public, emulator public, one reference unit built. Q4 2027 stays the target for units you can buy.

Q: What is actually done by April 2027, and what isn’t? Done: the emulator, the runtime, the four launch cartridges, the full hardware design, and one assembled, working reference unit. Not done: tooling and BOM economics for a run of many, enclosure panels validated for repeatable assembly, and any retail path. The launch says so plainly. It announces a built thing and a public design. There is no store yet.

Q: What does the ~50-unit run mean, and is 50 the number? 50 is a planning anchor. The real number gets set when the economics do. The run has to do three jobs at once: fund itself, reach the people who followed the build, and prove the unit economics of a sellable device. The end goal is a profitable product. If the first run sells and the economics hold, it scales past 50.

Q: Is this a platform or a single product? A platform, by intent. The KN-86 is the first device, with two more in concept. The first device has to earn the line by showing that people want the object and that it can be built at a defensible margin. Nothing about devices two and three gets announced until the first one clears that bar.

Q: What is the biggest risk to the April 2027 date? The reference unit not being reliably assemblable by then. The custom panels, the split-keyboard integration, the two-display wiring, and the coprocessor bring-up all have to land in one working box. The emulator and the design carry less risk. Mitigation: if the single unit slips, the design and emulator launch still stands, and the unit follows within weeks.

Q: What is the second risk? Cartridge and enclosure economics for the run. Two-piece clamshell shells and 3D-printed panels are cheap at quantity one and not obviously cheap at fifty. The commercial goal depends on a per-unit cost that leaves margin.

Q: What is the third risk? The input model not being good in the hand. The whole premise is that a Lisp keyboard is genuinely good to operate. If the reference unit proves it awkward, that is a real finding, and the way you get it is by building and using the actual device.

Q: What does “this went well” look like a year after launch?

The reference unit is in daily use and the input model holds up.
Enough waitlist demand to commit a production run and lock its price.
Per-unit economics that show a margin.
The emulator has real users, and at least one cartridge comes from someone other than us.
A credible path to device two.

Q: What kills it? In order of likelihood: the physical unit cannot be made reliably, so the “built and working” claim does not hold; the run economics never reach margin, so “profitable product” stays out of reach; or the input model is bad in the hand and the premise does not survive contact. The April 2027 build is designed to surface all three early.

Document owner: Josh Schairbaum, Great Western Productions. Working-backwards draft. Not for external distribution.