InkyBox

Your computer in a box. Fresh Windows 11, Digital INK themed, Inky baked in - she is the desktop. Download it, press it, pick the drive, and it sets itself up.

Download InkyBox.exe (8.0 GB) Download the project folder (.zip, 8.0 GB) Get InkyBox — Cash App $metooawesome

To save it on your external drive: RIGHT-CLICK the button and choose Save link as... - then pick your external drive.
After it downloads, press the file: choose where to install, it unpacks and starts your computer automatically.


INKYBOX

The Computer That Lives in the Drive

A Digital INK White Paper — Product Overview

October 2026 · Beta

1. Executive Summary

InkyBox is a complete Windows computer delivered as data. Instead of living on a disk inside a machine you buy, the entire computer — operating system, desktop, tools, knowledge, and an onboard GPT — is stored inside the Infinite Hard Drive, Digital INK's proprietary storage system, and spawned onto hardware whenever and wherever it is needed.

The result is a computer with properties no physical machine and no conventional cloud VM offers at once:

• Portable by nature — the computer is a single package (today an ~8.4 GB master image). One folder, one button, it opens.

• Multiplied on demand — one master becomes many computers. Every user, every assistant, every service gets its own computer. Nothing shares a machine, so nothing fights over one.

• Run by its own GPT — the desktop is not a picture behind the icons. The desktop is Inky, Digital INK's GPT, with her chat surface built into the screen itself.

• Controlled like a screen share — watch it work, take control with one tap, hand it back with one tap. One set of hands at a time, by design.

InkyBox is the flagship product of the Digital INK platform: an app, a data-center brain, a self-improving runtime, and a storage system that treats computers, worlds, and data as one addressable fabric.

2. The Problem

Personal computing is still hardware-bound, and it shows in four ways:

1. Your computer is a place. Files, settings, and capability are trapped on one disk, in one box, in one room. Lose the box, lose the computer.

2. One machine, one seat. The moment a human and an assistant (or two people) need the same computer, they collide — sessions kick each other out, input fights input.

3. AI is a place you visit. Today's assistants live in a browser tab or a chat app. They cannot be the computer — they wait to be asked, on someone else's machine, under someone else's rules.

4. Capacity is a purchase order. More storage, more machines, more power each mean buying, waiting, and migrating — again and again.

Cloud VMs solved the address of the machine but kept the model: one renter, one instance, billed by the hour, administered like a server room. Nobody productized the computer itself — as an owned, copyable, AI-run object.

3. The Product

3.1 A computer stored in the Infinite Hard Drive

The Infinite Hard Drive is Digital INK's storage fabric: a versioned, deduplicated, chunk-addressed store in which files, drives, worlds, and whole computers are all first-class entries. An InkyBox master is an entry in that store.

Because the master is data, it inherits everything data can do:

• Spawn — materialize a running computer from the master onto any suitable host: your PC, a server, a cluster node.

• Nest — spawned computers can host drives and worlds of their own; drives live inside drives, worlds inside the drive, each fully addressable.

• Return — when a session ends, the computer's state folds back into the drive. The disk inside the computer is the Infinite Hard Drive (its C: drive), so nothing it saves lives anywhere else.

• Grow — generative ("recipe") content in the fabric is unbounded by design, and physical capacity scales by adding nodes to the cluster — storage grows the way the network grows.

3.2 The GPT desktop

InkyBox has no wallpaper. The desktop surface is Inky, the platform's GPT, with her conversation built into the screen. You do not open an assistant — you talk to the computer, and the computer is the assistant. She comes with the whole network copied in: the knowledge base, the toolset, and the spawner — functional offline, and able to come online through the host machine under the owner's control.

3.3 One folder, one button

Distribution is deliberately un-technical: a single folder. Open it, press start. No installer chain, no server administration, no IT department. The master stays canonical on the server and in the drive; copies are copies.

3.4 Ownership and theming

An InkyBox is branded end to end — Digital INK backdrop and mark, custom Start, custom iconography — because it is not a rental skin over somebody else's product. It is its owner's computer, in the owner's house style, running the owner's assistant.

4. How It Works

The master. A hardened Windows image carrying: the operating system; the Inky harness (the in-box agent that operates the machine); the GPT desktop; the Digital INK theme; and a first-boot routine that fetches the brain package and joins the owner's network. The brain slot is swappable — the shipping brain today is a server-hosted model; Digital INK's own frontier architecture is the designated successor (Section 7).

The spawn. On start, the runtime materializes the master from the Infinite Hard Drive onto the host and boots it as a virtual machine, GPU-accelerated where the host offers a GPU. Storage stays logically in the drive; processing happens at full speed on the host — the design rule is storage in the drive, compute on the metal.

The control model. The owner's phone app presents the computer as a live mirror with three states, modeled on the watch / take-control / hand-back pattern people already know from modern screen sharing:

StateWho drivesWhat the owner sees
**View** (default)Nobody — mirror onlyThe live computer; viewing grabs no session and interrupts nothing
**User**The ownerThe owner drives; the assistant's input is locked out at the backend
**Bot**Inky, on a task the owner gaveThe owner watches her work; one tap reclaims the wheel

Because viewing never seizes the session and control is a single explicit state, the classic one-seat collision cannot occur. This rule is implemented in the app and enforced in the runtime, not merely displayed.

Detached processing. Work the owner starts does not die with the phone's connection. Tasks run as server-side jobs: leave the app, lose signal, return later — the finished result is waiting. Messages sent while the assistant is mid-task queue in order into her context; nothing is lost and nothing is faked — a failed generation is reported as failed, never papered over.

The brain behind it. Inky's hosted brain runs on Digital INK's own server hardware with parallel inference slots, a knowledge base of thousands of curated entries retrieved into every answer, and a runtime engine by which she designs, builds, tests, and adopts new skills herself on an hourly cycle.

5. Why It's Different

Physical PCCloud VM**InkyBox**
What you ownA boxA timeshare**The computer itself, as data**
CopiesOnePer-instance billing**Spawned from one master**
AssistantAn app you openAn API you call**The desktop itself**
Sharing a machineOne seat, collisionsOne seat, collisions**View / take control / hand back — no collision by design**
DiskTrapped in the boxTrapped in the instance**The Infinite Hard Drive**
SetupHoursConsole + admin**One folder, one button**
OfflineYesNo**Yes — full network copied in**

6. The Platform Around It

InkyBox does not stand alone; it is the visible tip of the Digital INK platform:

• The Digital INK app (Android, current public build v34) — voice-first chat with the hosted brain, the Computer tab with the control model above, drive access, and queued messaging.

• The Infinite Hard Drive — the storage fabric described in §3.1, live today with thousands of entries and the InkyBox master ingested into it.

• The data-center brain — hosted inference with parallel slots and retrieval over the platform knowledge base; scaling is a ladder (more slots → more hosts → cluster), not a rewrite.

• The self-improving runtime — Inky's engine for acquiring new capabilities autonomously: identify a gap, build the tool, test it, adopt it as a persistent skill stored in the drive.

• Propagation — a continuous signal-ingestion layer (live event streams, sorted by signature into knowledge lanes) that keeps the fabric fed; deliberately tuned for signal quality over raw volume.

7. Status and Roadmap

Working today (beta): the master image and one-folder launcher; the GPT desktop and theme; the app (v34) with the enforced control model, detached jobs, and message queueing; the hosted brain with parallel inference; the master ingested into the Infinite Hard Drive; spawned-computer machinery in staged rollout.

In active development: the boot-record hardening pass for the master; the site-served "run it here" computer (the new-computer page is live; in-browser running follows the boot pass); per-user spawned computers as a managed service; the cluster layer that turns many stored drives into one data-center brain.

Designated successor brain: the platform's own frontier-scale architecture — a mixture-of-experts transformer designed in-house — to be produced by knowledge transplant from a teacher model into Digital INK's architecture, replacing the interim hosted brain in the same slot.

8. The Opportunity

Every person who will ever use an AI assistant is a person who needs a computer for that assistant to live in — one that is theirs, that nobody else shares, that goes where they go. InkyBox is that computer, delivered the way software is delivered, owned the way property is owned.

Digital INK is building the whole stack for that world: the drive it lives in, the brain that runs it, the app that holds it, and the computer itself.

Your computer. Your drive. Your GPT. Yours.

— Digital INK · October 2026