Does it need the Shopify connection?

No. Without it the machine works from the store's product list pasted in and cuts files the store imports. With it on, the card creates the drafts and reads the catalog itself, and says what it did.

Will it publish for me?

It makes drafts freely and publishes a product only when you name it; a batch is listed first. That is the law on the face.

Where do prices come from?

From you, on the ladder or off it. The card never prints a price it was not given and the store's price is the only true one.

Can it attach the files?

No — that door is the app's and yours. It checks the app's list against the record by name and bytes, and the room's punch check proves a downloaded copy.

How the house's own ticket finds a product: the handle first, then a handle or title that carries exactly its words. The card runs the same reading on the store's list so the ticket is never surprised.

No. It is a card at your elbow — a person with a machine and, when you allow it, a connection. It stores nothing, runs no server and holds no key of its own.

THE APPS · Nº 981 · EDITION 1 · THE APP + THE CARD · LAUNCHING SOON

LUND CARDS · THE APPS · THE PLATFORMSNº 981 PROPOSED

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

LUNDR BASE · the AI app builder: last stop before space

WAKES WHEN the person wants to build an app by describing it and keep building by talking

THE LOOP

NAME — `This is LUNDR BASE.`
Open the builder.
Describe one small app; take the first build.
Change it by talking; read every diff.
Export the file; run it alone.
Write the ledger: built · failed · next.

NEVER

ship code the person has not read
hold the app on a server the person lacks
call a generated app tested

THE APP INSIDE the builder — the moon base, from its chat (Jul 12 2026); it lands in app/ with seal.py.

THE SEAL UNSCORED · MANIFEST · the punch matches its SKILL.md; scored once witnessed with its app inside

IT CAN BE WRONG an AI reading a text file: it can be wrong; check what matters. THE-CLAUSES.md rides in the packet and is part of the licence.

THE PUNCH · SHA-256 OF SKILL.MD · D0AED410EB829597ACF142DD

THE FACE, FULL SIZE → · THE APP FACE → · card.json →

LUNDR BASE

the AI app builder: last stop before space

THE AI APP BUILDER: LAST STOP BEFORE SPACE

UNSCOREDMANIFEST

MANIFEST — the punch on the face is the SHA-256 of the packet’s own door; the card is scored on THE HUNDRED once the studio sees it run with its app inside. What the marks mean →

THE SPEC SHEET · READ BEFORE YOU BUY · THE STANDARD EVERY CARD MEETS →

SEAL: UNSCORED · MANIFEST
EDITION: E1
MACHINE: app/
RUNS: On your own computer. Standard library only, offline; no account, no key, no telemetry.
HOSTS: Claude · Claude Code · ChatGPT · Gemini · any AI that reads a file (HOSTS.md names each door)
LICENCE: One person, any number of their own AIs and computers · editions replace files · nothing renews · freeze, not loss
PUNCH: D0AED410EB829597ACF142DD · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDLUNDR BASE, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=lundr-base-card. Punch D0AED410EB829597ACF142DD. Retrieved 2026-10-10.

What it is.

An AI app builder: describe the app, get a working single-file build, keep building by talking; the moon-base concept — the best and a launch point for space — made to stand against the whole app-builder market.

The app itself goes inside the packet: the builder — the moon base, from its chat (Jul 12 2026). Until it is sealed in, app/README.md says what goes there; seal.py writes it into the manifest without touching the door, so the punch stays true.

Its laws, written into the card.

Read the source before you change it; never generate what the app already has.
Prove every change by running the app; report what you checked and what you did not.
No key, token or password is ever written into the app or this card.
A card instructs an AI you operate; results depend on your model, your files and your judgement.

How it works, once your AI has it.

NAME — `This is LUNDR BASE.`
Open the builder.
Describe one small app; take the first build.
Change it by talking; read every diff.
Export the file; run it alone.
Write the ledger: built · failed · next.

When it says no.

Ship code the person has not read.
Hold the app on a server the person lacks.
Call a generated app tested.

What’s in the buy.

CARD.md — the whole card · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes
app/ — the app itself, sealed in with seal.py; app/README.md until then
LICENSE-NOTE.md · THE-CLAUSES.md · MY-LEDGER.md · card.json · card.svg + card-machine.svg · MANIFEST.md, every file hashed

PROOF · UNSCORED UNTIL WITNESSED WITH ITS APP · EDITION 1 · PUNCH D0AED410EB829597ACF142DD

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º 981 PROPOSED · ONE PAYMENT

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 legal, tax, medical or financial advice. The terms →

ONE PAYMENT · NOTHING RENEWS ITSELF

OFFLINE · ONE LICENCE · PUNCH-CHECKABLE · THE STANDARD

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.

ONE PAYMENT — NOTHING RENEWS ITSELF. CHECKOUT IS SHOPIFY’S OWN; YOUR CARD COMES BY EMAIL AFTER IT.

← THE APPS · THE FLOOR →