THE HOST PROBE · what this host offers, and the walls it has
WAKES WHEN an agent starts in a new environment, or a build must pass through a size or tool limit
THE LOOP
hostprobe.py probe · the record, no packet
wall · every limit learned, with its note
needs · what the task will want
check · the mismatches, before any work
the walls travel: next task, first step
NEVER
Test the network on the wire to describe it
Learn the same wall twice
Start a long build without the check
IT MAKES probe — the record, read from the host itself; wall — a wall learned, kept; needs — a needs file to fill in; check — every need against the record.
THE STANDARD probe before work; no packets; a wall is learned once; needs are written, not assumed; a mismatch is named before any step; unknown is a value.
PROOF SELFTEST 11/11 · witnessed in Claude 2026-10-09 · 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 · 130FDB9D078DD8E308D13735
CITE THIS CARDTHE HOST PROBE, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=host-probe-card. Punch 130FDB9D078DD8E308D13735. Retrieved 2026-10-10.
What it is.
Records what a host actually offers before work starts — the Python and platform, the tools on the path, which folders can be written, disk and memory, the proxy and network rules the environment declares — without sending a single packet; keeps the walls a task meets (a chat's file limit, a zip limit, an upload cap) once learned; and checks a task's needs file (tools, folders, network, every output with the wall it passes through) against the record, so a wall is met at the first step.
It carries a machine that shows its working: probe — the record, read from the host itself; wall — a wall learned, kept; needs — a needs file to fill in; check — every need against the record — 11 checks in its selftest, every command on the record. It will never test the network on the wire to describe it; never learn the same wall twice; never start a long build without the check.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
PROBE BEFORE WORKThe record costs a second; the wall at the end costs the build.
NO PACKETSThe network is described from the environment, never tested on the wire; the probe sends nothing.
A WALL IS LEARNED ONCEMeasured the hard way one time, kept with its note, checked at every later start.
NEEDS ARE WRITTEN, NOT ASSUMEDTools, folders, network, outputs with their walls, in a file the check can read.
A MISMATCH IS NAMED BEFORE ANY STEPA mismatch is named before any step, with the wall and the size side by side.
UNKNOWN IS A VALUEA network not declared open is reported as not declared, never as open.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/KNOW-THE-HOST-FIRST.md
THE MACHINEhostprobe.py · four commandsprobe — the record, read from the host itself; wall — a wall learned, kept; needs — a needs file to fill in; check — every need against the record. Every command prints its working and refuses a bad input; 11 checks in its selftest, every command on the record.
What it does once your AI has it.
probe The record, read from the host itself
wall A wall learned, kept
needs A needs file to fill in
check Every need against the record
On the record This host probed without a packet — tools on the path, writable folders, disk, memory, the network as declared; the 30 MiB chat wall kept with its note; a needs file written and filled; the check named the 38 MiB theme zip as over the wall before any work, and passed the register.
What it will never do.
It will never test the network on the wire to describe it; never learn the same wall twice; never start a long build without the check.
It reads the host; it does not test the network, so a proxy it sees declared may still refuse a given site. Walls are what a person records; the probe cannot discover a product's limits on its own. Tool detection is by name on the path. 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
KNOW-THE-HOST-FIRST.md — the guide in references/, in the card's own voice
scripts/hostprobe.py — the machine: probe · wall · needs · check, standard library only, selftest 11/11
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 11/11 · 4 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-09 · EDITION 1 · PUNCH 130FDB9D078DD8E308D13735
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º 909 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-09
hostprobe.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.
probe
the record, read from the host itself
wall
a wall learned, kept
needs
a needs file to fill in
check
every need against the record
selftest
11 checks that prove the machine; it must print 11/11
$ python3 scripts/hostprobe.py needs --out needs.json
wrote needs.json — fill in the tools, the folders to write, the network and every output with the wall it goes through
(the needs file filled in: python3 and zip, a 38 MiB theme zip and a 220 KB register, both through the chat)
$ (the needs file filled in: python3 and zip, a 38 MiB theme zip and a 220 KB register, both through the chat)
check · EVERY NEED AGAINST THE RECORD
$ python3 scripts/hostprobe.py check host.json needs.json
NOT AS PLANNED · 1 finding
the theme zip is 38MiB, over the chat_file_limit wall of 30MiB (the chat refuses a bigger file)
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?
Hostprobe.py probe · the record, no packet. It asks first for a minute at the start, and the limits the person already knows about the place the work lands.
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 (11/11) 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. It reads the host; it does not test the network, so a proxy it sees declared may still refuse a given site. Walls are what a person records; the probe cannot discover a product's limits on its own. Tool detection is by name on the path.
What will it never do?
It will never test the network on the wire to describe it; never learn the same wall twice; never start a long build without the check.
