THE HORIZON CARD · the map of the cards an AI company will need
WAKES WHEN someone asks which AI skills will be needed, or whether a card for a need is built yet
THE LOOP
list · the map, by horizon or status
card · one entry in full
where · built, answered, or not yet
waits · what the later cards wait on
every date said as a horizon
NEVER
Call a horizon a promise or a date
Call an entry built without naming its card
Force a need onto an entry that does not fit
IT MAKES list — the map, filtered, with its counts; card — one entry in full: job, horizon, status, waits on, build order, shelf; where — built, answered or not yet, and as which card; waits — what each later entry waits on, grouped.
THE STANDARD a map of needs; a horizon, not a promise; built means a card; waits are named; no forced match; fifty-two, as drawn.
PROOF SELFTEST 8/8 · witnessed in Claude 2026-10-11 · Edition 1.
THE SEAL 98 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 5
IT CAN BE WRONG an AI reading a text file: it can be wrong and can invent a number, a rule, a name or a date; check what matters against your own records and the source; the risk is yours. THE-CLAUSES.md rides in the packet and is part of the licence.
THE PUNCH · SHA-256 OF SKILL.MD · A9AFD5AEFFC2B8C40301E28F
CITE THIS CARDTHE HORIZON CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=horizon-card. Punch A9AFD5AEFFC2B8C40301E28F. Retrieved 2026-10-11.
What it is.
A map of needs, not a promise of products or a forecast of dates. THE HORIZON is the studio's map of the 52 AI skill cards an AI company will need from 2026 to 2056, in three horizons: now to 2028, 2028 to 2036 and 2036 to 2056. Each entry is marked now, partial now or waits. list shows the map with its counts, filtered by horizon or status. card gives one entry in full: its job, its horizon, its status, what it waits on and its place in the build order. where says whether the studio has built it, and as which card on the shelf, or which card already does its job. waits groups the later entries by what the world must make first.
It carries a machine that shows its working: list — the map, filtered, with its counts; card — one entry in full: job, horizon, status, waits on, build order, shelf; where — built, answered or not yet, and as which card; waits — what each later entry waits on, grouped — 8 checks in its selftest, every command on the record. It will never call a horizon a promise or a date; never call an entry built without naming its card; never force a need onto an entry that does not fit.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
A MAP OF NEEDSIt names what an AI company will need. It promises no product and forecasts no date.
A HORIZON, NOT A PROMISEEvery date is a horizon: now to 2028, 2028 to 2036, 2036 to 2056. No entry is said to arrive in a given year.
BUILT MEANS A CARDAn entry is called built only with the card that does its job named, with its number and its place on the shelf.
WAITS ARE NAMEDEvery waiting entry says what the world must make first. Nothing is said to have arrived without a source.
NO FORCED MATCHA need that fits no entry is said to be off the map. When two entries fit, both are named and the person chooses.
FIFTY-TWO, AS DRAWNThe entries are the map as drawn on 2026-10-03. The machine never adds an entry or drops one.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-HORIZON.md
THE MACHINEhorizon.py · four commandslist — the map, filtered, with its counts; card — one entry in full: job, horizon, status, waits on, build order, shelf; where — built, answered or not yet, and as which card; waits — what each later entry waits on, grouped. Every command prints its working and refuses a bad input; 8 checks in its selftest, every command on the record.
What it does once your AI has it.
list The map, filtered, with its counts
card One entry in full: job, horizon, status, waits on, build order, shelf
where Built, answered or not yet, and as which card
waits What each later entry waits on, grouped
On the record Horizon two lists 14 entries: 4 now, 3 partial now and 7 waiting. The 4 partial-now entries are AGENT ID, TUTOR, ELECTION-SEASON and TRANSITION. THE MANDATE CARD comes up in full as Nº 784, while "robot" fits two entries and "quantum gardening" fits none, so both are refused. The knowledge entry is answered by THE READING SHELF, Nº 1086, and fleet-card on the shelf does another job. THE HOUSEHOLD ROBOT CARD was cut at 12.357.83 as Nº 1179. waits groups the 21 later entries, and a horizon of 4 is refused.
What it will never do.
It will never call a horizon a promise or a date; never call an entry built without naming its card; never force a need onto an entry that does not fit.
A map of needs as the studio drew it on 2026-10-03: not research, not a forecast, and not a promise of any product. It knows its 52 entries and no others. Nineteen entries wait on something that does not exist yet, such as robots in ordinary homes, consumer brain-computer interfaces and shared standards. The machine says what each waits on and cannot tell when, or whether, it will arrive. Its table of what is built was read from the shelf at 12.357.83 and does not update itself. It is an AI reading a text file: it can be wrong, so check what matters against your own records and the source.
What’s in the buy.
CARD.md — the whole card: who it is, its laws, when it says no, what it carries · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes, for you
THE-HORIZON.md — the guide in references/, in the card's own voice
scripts/horizon.py — the machine: list · card · where · waits, standard library only, selftest 8/8
WITNESS.md + SELFTEST.md — every command on the record, as it printed · MANIFEST.md, every file hashed · AUDIT.md, the twelve checks
MY-LEDGER.md — the card's memory, on your own machine · TIN.md · LICENSE-NOTE.md · THE-CLAUSES.md · HOSTS.md
card.svg + card-machine.svg + card.json · card.html, the card as one offline file · the doors for ChatGPT, Gemini, Cursor, Claude Code and MCP hosts (rules/, system/, mcp/)
PROOF · SELFTEST 8/8 · 4 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-11 · EDITION 1 · PUNCH A9AFD5AEFFC2B8C40301E28F
ON EVERY DOOR · A CARD FOR YOUR AI, A FILE FOR YOUR COMPUTER
In Claude: turn on code execution under Settings › Capabilities, then Customize › Skills › + › Create skill, and upload the zip as it is — START-HERE.md in the box walks you through it, and tells you how to keep the ledger. In ChatGPT, Gemini and the rest: a Project, a GPT or a Gem with the card’s files attached and the short door in the box pasted as its instructions. The words run anywhere an AI reads Markdown; the machines run wherever the host runs Python. Witnessed in Claude only. The host marks →
Take it.
Nº 1186 PROPOSED — LAUNCHING SOON
Sold as is under the term printed. A card instructs an AI you operate; results depend on your model, your files and your judgement. Not medical, legal, tax or financial advice, never the person’s boss, and not a licence to practise. The terms →
One payment. The file is yours to keep and keeps working at its edition; new editions issued in the year after you buy reach you by email as replacement files. Tax is added at checkout where it applies. Nothing auto-renews.
A TERM, NOT A SUBSCRIPTION: NOTHING RENEWS ITSELF AND NOBODY IS CHARGED AGAIN. WHEN A TERM ENDS THE FILES STAY ON YOUR COMPUTER AND STAY READABLE — FREEZE, NOT LOSS.
THE MACHINE · IN THE OPEN · FROM THE WITNESSED RUN OF 2026-10-11
horizon.py, every command showing its working.
A small Python program, standard library only. Your AI runs it; you can too. Every block below is pasted from the card’s own WITNESS.md, as printed.
list
the map, filtered, with its counts
card
one entry in full: job, horizon, status, waits on, build order, shelf
where
built, answered or not yet, and as which card
waits
what each later entry waits on, grouped
selftest
8 checks that prove the machine; it must print 8/8
list · THE MAP, FILTERED, WITH ITS COUNTS
$ python3 scripts/horizon.py list --horizon 2
THE HORIZON · the map as drawn on 2026-10-03 · a map of needs, not a promise of products or a forecast of dates
HORIZON TWO · 2028 to 2036 (a horizon, not a promise) · 14
now THE MANDATE CARD What an agent may spend, where and until when, signed by its person
now THE ENVELOPE CARD Work handed between AIs with a checkable done, sealed, answered with evidence
now THE AGENT AUDIT CARD A day of an agent's actions rebuilt and checked against its mandates and envelopes
now THE HANDOVER-TO-HUMAN CARD When an agent must stop and get a person, and the person's answer kept
partial now THE AGENT ID CARD A verifiable identity for an agent: who it acts for, what it may do, revocable · waits on a shared standard for agent identity
partial now THE TUTOR CARD Mastery tracked over years; the learner's record is theirs to keep
partial now THE ELECTION-SEASON CARD What an AI must and must not do around elections: sources, no persuasion, disclosure · waits on laws that differ by place
waits THE NEGOTIATION CARD Two agents bargaining for their people inside mandates; every concession logged · waits on agent-to-agent commerce at scale
waits THE MEMORY LEDGER CARD A person's long-term AI memory as a record they can read and correct · waits on memory that moves between companies
waits THE FLEET CARD Many agents on one job: roles, budgets, who checks whom, one record · waits on reliable long-running agent teams
waits THE LAB NOTEBOOK CARD An AI researcher's runs logged so a person can repeat and audit each claim · waits on AI-run research at scale
waits THE ROBOT ENVELOPE CARD The physical limits a robot works inside (zones, speeds, forces, people near), checked before each task · waits on general-purpose robots at work and home
waits THE COMPUTE BUDGET CARD Energy and compute per task, reported and capped · waits on providers reporting energy per call
waits THE DEEPFAKE CHECK CARD Images, audio and video checked for their content record before they are trusted · waits on content records being common
14 of 52 entries · now 4 · partial now 3 · waits 7
list · THE MAP, FILTERED, WITH ITS COUNTS
$ python3 scripts/horizon.py list --status partial
THE HORIZON · the map as drawn on 2026-10-03 · a map of needs, not a promise of products or a forecast of dates
HORIZON TWO · 2028 to 2036 (a horizon, not a promise) · 3
partial now THE AGENT ID CARD A verifiable identity for an agent: who it acts for, what it may do, revocable · waits on a shared standard for agent identity
partial now THE TUTOR CARD Mastery tracked over years; the learner's record is theirs to keep
partial now THE ELECTION-SEASON CARD What an AI must and must not do around elections: sources, no persuasion, disclosure · waits on laws that differ by place
HORIZON THREE · 2036 to 2056 (a horizon, not a promise) · 1
partial now THE TRANSITION CARD People moving through work that AI has changed: skills mapped, paths, a bridge
4 of 52 entries · now 0 · partial now 4 · waits 0
card · ONE ENTRY IN FULL: JOB, HORIZON, STATUS, WAITS ON, BUILD ORDER, SHELF
$ python3 scripts/horizon.py card mandate
THE MANDATE CARD
its job: What an agent may spend, where and until when, signed by its person
horizon: HORIZON TWO · 2028 to 2036 (a horizon, not a promise)
status: now (drawn built and proved on 2026-10-03)
waits on: nothing: everything it needs exists today
on the shelf: built · THE MANDATE CARD, Nº 784
a map of needs: the horizon is not a date promised, and the entry is not a product promised
card · ONE ENTRY IN FULL: JOB, HORIZON, STATUS, WAITS ON, BUILD ORDER, SHELF
$ python3 scripts/horizon.py card robot
"robot" fits 2 entries: THE ROBOT ENVELOPE CARD, THE HOUSEHOLD ROBOT CARD. Name one.
card · ONE ENTRY IN FULL: JOB, HORIZON, STATUS, WAITS ON, BUILD ORDER, SHELF
$ python3 scripts/horizon.py card quantum gardening
"quantum gardening" is not on the map. The map holds its 52 entries and no others; a need it does not fit may want a card nobody has drawn yet.
where · BUILT, ANSWERED OR NOT YET, AND AS WHICH CARD
$ python3 scripts/horizon.py where knowledge-card
THE KNOWLEDGE CARD · ANSWERED · a card already on the shelf does its job
THE READING SHELF (reading-shelf-card) · Nº 1086 · THE INSTRUMENTS · FOR AI BUILDERS
A person's documents as what a bot answers from, each passage cited.
read from the shelf at 12.357.83 (2026-10-11); the shelf may have moved since
where · BUILT, ANSWERED OR NOT YET, AND AS WHICH CARD
$ python3 scripts/horizon.py where fleet-card
THE FLEET CARD · NOT YET · a card of this name is on the shelf for another job
THE FLEET CARD (fleet-card) · Nº 685 · THE INSTRUMENTS · THE FLEET
Its record reads: a register of ventures, their stage and next gate. Many agents on one job is not a card yet.
read from the shelf at 12.357.83 (2026-10-11); the shelf may have moved since
where · BUILT, ANSWERED OR NOT YET, AND AS WHICH CARD
$ python3 scripts/horizon.py where THE HOUSEHOLD ROBOT CARD
THE HOUSEHOLD ROBOT CARD · BUILT · cut at 12.357.83 as what can be done today, saying what it waits on
THE HOUSEHOLD ROBOT CARD (household-robot-card) · Nº 1179 · THE INSTRUMENTS · HORIZON THREE
It waits on robots in ordinary homes; the card does what can be done today.
read from the shelf at 12.357.83 (2026-10-11); the shelf may have moved since
waits · WHAT EACH LATER ENTRY WAITS ON, GROUPED
$ python3 scripts/horizon.py waits
THE HORIZON · what the 21 later entries wait on, grouped by the kind of change the world must make
a shared standard or record · 5
THE AGENT ID CARD H2 partial now waits on a shared standard for agent identity · cut at 12.357.83
THE MEMORY LEDGER CARD H2 waits waits on memory that moves between companies · cut at 12.357.83
THE COMPUTE BUDGET CARD H2 waits waits on providers reporting energy per call · cut at 12.357.83
THE DEEPFAKE CHECK CARD H2 waits waits on content records being common · cut at 12.357.83
THE TRUST REGISTRY CARD H3 waits waits on shared certification across companies · cut at 12.357.83
a law or an agreement · 4
THE ELECTION-SEASON CARD H2 partial now waits on laws that differ by place · cut at 12.357.83
THE ARBITRATION CARD H3 waits waits on agent agreements recognised in law · cut at 12.357.83
THE CHARTER CARD H3 waits waits on AI-run organisations with legal standing · not a card yet (its name is another job)
THE PLANETARY COORDINATION CARD H3 waits waits on agreements across borders · cut at 12.357.83
machines in the world · 3
THE ROBOT ENVELOPE CARD H2 waits waits on general-purpose robots at work and home · cut at 12.357.83
THE HOUSEHOLD ROBOT CARD H3 waits waits on robots in ordinary homes · cut at 12.357.83
THE NEURAL DATA CARD H3 waits waits on consumer brain-computer interfaces · cut at 12.357.83
agents at scale, and AI that lasts · 6
THE NEGOTIATION CARD H2 waits waits on agent-to-agent commerce at scale · cut at 12.357.83
THE FLEET CARD H2 waits waits on reliable long-running agent teams · not a card yet (its name is another job)
THE LAB NOTEBOOK CARD H2 waits waits on AI-run research at scale · on the shelf
THE LIFELONG COMPANION CARD H3 waits waits on assistants that persist for decades · cut at 12.357.83
THE DIGITAL TWIN CONSENT CARD H3 waits waits on personal replicas being common · cut at 12.357.83
THE SUCCESSION CARD H3 waits waits on model lifecycles of that length · cut at 12.357.83
settled science · 1
THE MODEL WELFARE CARD H3 waits waits on settled science on AI experience · cut at 12.357.83
nothing named: a first version can be cut today · 2
THE TUTOR CARD H2 partial now on the shelf
THE TRANSITION CARD H3 partial now cut at 12.357.83
no date is given for any of them: each waits on a change, and the map cannot say when, or whether, it comes
list · THE MAP, FILTERED, WITH ITS COUNTS
$ python3 scripts/horizon.py list --horizon 4
a horizon is 1, 2 or 3
THE NUMBERS, NAMES AND DATES IN THESE RUNS ARE THE STUDIO’S OWN EXAMPLES, INVENTED FOR THE RECORD; NO REAL COMPANY, PERSON OR PROPERTY IS NAMED.
QUESTIONS AT THE TABLE
Asked before the wire.
What does it need from me?
List · the map, by horizon or status. It asks first for the need or the card in plain words, or a card's handle; a horizon (1, 2 or 3) or a status (now, partial, waits) to narrow the map.
Does it send anything anywhere?
No. The machine is a standard-library Python program that runs on your own computer and sends nothing anywhere; the words run wherever an AI reads Markdown. No server, no account, no key.
What is on the record?
The self-test (8/8) and every command run on real example inputs, pasted into WITNESS.md as they printed; the punch on the face is the SHA-256 of SKILL.md, so a downloaded copy can be checked against this room.
Can it be wrong?
Yes — it is an AI reading a text file. A map of needs as the studio drew it on 2026-10-03: not research, not a forecast, and not a promise of any product. It knows its 52 entries and no others. Nineteen entries wait on something that does not exist yet, such as robots in ordinary homes, consumer brain-computer interfaces and shared standards. The machine says what each waits on and cannot tell when, or whether, it will arrive. Its table of what is built was read from the shelf at 12.357.83 and does not update itself.
What will it never do?
It will never call a horizon a promise or a date; never call an entry built without naming its card; never force a need onto an entry that does not fit.
