Born Between 2 Generalswith the partner organisation Device Package Program
A program in development

Know your tech.

A safe, provenance-aware computing setup — preloaded, connected locally, and backed by training.

Most people receive a device with no idea what is on it, who made it, or what it sends home. This program starts from the opposite premise: a device whose origin is known, whose software ships safe by default, and whose owner is taught how it works.

In plain terms: a tablet or laptop that arrives ready to use — safe from the first minute, from a source you can point to — with a fixed set of apps already installed and training so the person holding it actually knows how it works.

Status In development. Hardware partnership under discussion — nothing here is an offer, and no partner is announced.
What it is

Three things in every package

Not a subscription and not an app to download. A physical device that shows up set up, with safe software already on it, and a person to teach you how it works.

1

A device, set up for you

A tablet or laptop that arrives configured and ready — no wiping, no guesswork. You turn it on and it works.

2

Safe software, already on it

A fixed set of apps installed and switched on before you open the box, with child-safety and privacy protections on by default.

3

Training that comes with it

A short course so the person using the device actually understands it — with a certificate at the end.

The software

What's on the device

The same safe set of apps ships on every package. In plain terms, it does three things — and the child-safety part is never something you pay extra for.

Keeps kids safer Child-safety and privacy protections — on out of the box, never behind a paywall, and not something you have to know to switch on.
Helps you tell what's true Tools to check what's real — look at a claim, see where a piece of information came from, and slow down before you pass it along.
Helps you learn An adaptive tutor and media-literacy activities — for a single student, a family, or a whole classroom.
How it's built

Four commitments

These hold at every tier. They are design constraints, not marketing — each one rules something out.

01

Safe by default

Child-safety and privacy protections are on out of the box. Nobody has to know a setting exists to be protected by it.

02

Provenance-aware

The device and its software have a known origin. Where your tech comes from is part of the product, not a footnote.

03

Connects locally

A package works as one unit — a family, a classroom, an organization — without routing everything through someone else's servers.

04

Least surprise

No preloaded app phones home in ways the owner cannot see or control. What it does is what it says it does.

Standing rule

Child-safety features are never paywalled — at any tier, in any package, under any partnership.

The packages

Four tiers

The same safe image at every level. What changes is how many devices, and how they connect to each other.

Tier 01

Solo

One person — a student, journalist, or staffer

A single provisioned device — tablet or laptop — with the safe app image.

Tier 02

Family

A household

A small set of devices with the child-safety layer on by default, connected locally.

Tier 03

Classroom / Team

A class, chapter, or small unit

A managed group of devices with shared enrollment and a local hub.

Tier 04

Org / Campaign

A full organization or campaign

An org-tier system that connects locally — fleet devices plus provisioning and management.

The shape of it

Who brings what

A device program needs two halves. We are assembling ours and looking for the partner who carries the other.

We bring the software layer

  • The imageA portfolio of provenance-aware, family-safe apps, licensed as a single preloaded set.
  • ReachDistribution through a trusted civic channel, tied to the partner organisation's the anniversary and America's 250th.
  • Pull-throughA training pipeline and a recurring convention that create ongoing demand rather than a one-time sale.

A partner brings the hardware

  • DevicesHardware across every tier — tablets, laptops, and org-tier systems.
  • BuildManufacturing, provisioning and enrollment, and the on-device security stack.
  • ServiceSupport and warranty for deployed fleets.
Where it stands

The path

An honest map of what is done and what is not. We are early, and the program is deliberately gated before anything reaches a participant.

PHASE 0 Package the program. Briefs, build plan, image spec, and pilot scope written. Done
PHASE 1 Get to the table. Open the hardware conversation; mutual NDA before any spec or pricing is shared. Current
PHASE 2 Define the pilot. Lock one tier and one audience; freeze the app image; clear counsel review. Next
PHASE 3 Build the image. Provision the pilot devices; QA against the frozen spec. Planned
PHASE 4 Run the pilot. Deploy to the cohort, run the training, capture what actually happened. Planned
PHASE 5 Decide. Review the pilot honestly, then scale or don't. Planned