THE HOME GROUND · THE TRAILHEAD · Nº 1211 · EDITION 1 · LAUNCHING SOON
LUND CARDS · THE HOME GROUNDNº 1211
THE CARD AS TEXT · FOR EYES AND FOR MACHINES
THE TRAIL REPORT · Trail conditions from people who were just there, aged honestly and never called safe.
WAKES WHEN Someone reports what a trail was like when they were on it. · A runner asks for the latest word on a trail before heading out. · Reports disagree and someone needs to see which is newer.
THE LOOP
Log the segment, condition, time and who
Age it: FRESH, AGING, STALE
Hold closures until a report lifts them
Show conflicts and never say safe
NEVER
Never calls a trail safe
Never ages out a closure on its own
Never shows a stale report as current
IT MAKES log — append one report (condition: dry, wet, mud, snow, ice, closed, hazard); status — latest report per segment with its age: FRESH, AGING, STALE (no current word) or CLOSED (as of ...); conflicts — segments whose reports in the window before --now disagree; digest — every trail on one line: closed segments, fresh, aging and stale counts, latest word.
THE LAW A report is what one person saw at one time. The card keeps the who and the when on every line, lets reports age, and never turns them into a promise. A closure stands until someone reports otherwise.
PROOF SELFTEST 14/14 · witnessed in Claude 2026-10-13 on fictional fixtures · the test prompts in fresh chats owed · Edition 1.
THE SEAL 96 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 4
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. LICENSE-NOTE.md rides in the packet and is the licence.
THE PUNCH · SHA-256 OF SKILL.MD · F3EB8F2C3E4531FA9BFC292F
CITE THIS CARDTHE TRAIL REPORT, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=trail-report-card. Punch F3EB8F2C3E4531FA9BFC292F. Retrieved 2026-10-13.
What it is.
Use when logging or reading trail condition reports (mud, snow, ice, closures) with their age. Not for route planning, weather forecasts or saying a trail is safe.
It carries a machine that shows its working: log — append one report (condition: dry, wet, mud, snow, ice, closed, hazard); status — latest report per segment with its age: FRESH, AGING, STALE (no current word) or CLOSED (as of ...); conflicts — segments whose reports in the window before --now disagree; digest — every trail on one line: closed segments, fresh, aging and stale counts, latest word — 14 checks in its selftest. It never calls a trail safe; never ages out a closure on its own; never shows a stale report as current.
The law, written into the card.
It is in the card itself, so the AI follows it.
THE LAWA report is what one person saw at one time. The card keeps the who and the when on every line, lets reports age, and never turns them into a promise. A closure stands until someone reports otherwise.
The method.
Log each report with the trail, the segment, one condition word (dry, wet, mud, snow, ice, closed, hazard), the time and the reporter.
Read the latest report per segment with its age: three days or less is FRESH, a week or less is AGING, older is STALE and reads as no current word.
Keep a closure standing until a later report on the same segment says otherwise; print it as CLOSED with the date it was reported.
Show conflicts — two reports on one segment, close in time, that disagree — instead of picking one.
Write every line as what someone saw and when. The word safe is never used.
What you bring.
Reports from your club or community, each with a time and a reporter.
Your trail and segment names.
Planned as a separate seat, not in this box and not yet on sale: a trail report for the trails the studio covers, fed by its members.
status Latest report per segment with its age: FRESH, AGING, STALE (no current word) or CLOSED (as of ...)
conflicts Segments whose reports in the window before --now disagree
digest Every trail on one line: closed segments, fresh, aging and stale counts, latest word
What it will never do.
It never calls a trail safe; never ages out a closure on its own; never shows a stale report as current.
Where it hands off: Measuring a route or its stops → THE ROUTE VAULT; Race-day go or no-go → THE WEATHER CALL; Official closures → the land manager's own notices.
It is not safety advice. It is an AI reading a text file: it can be wrong, so check what matters against your own records and the source. The holder brings their own AI; no endorsement by Anthropic or any other AI company is claimed.
What’s in the buy.
SKILL.md — the card your AI reads: when it wakes, the loop, the never-lines, the hand-offs.
CARD.md — the whole card in ten sections: face, law, method, machine, what you bring, never, tests, seal, term.
scripts/trailreport.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
tests/EVALS.json and scripts/evals.py — 8 test prompts and the offline runner that scores your AI's answers.
references/ — the data schema and FICTIONAL demo files, invented to show the machine, not real.
MY-LEDGER.md — your own record of what you asked and what you decided.
START-HERE.md, system/short-prompt.md, system/rules.md — the doors, for any AI with or without skills.
card.svg, card.json, card.html, AUDIT.md, MANIFEST.md, WITNESS.md, SELFTEST.md — the faces and the proof.
NOT IN THE BOX — any studio edition (planned, not yet on sale: a trail report for the trails the studio covers, fed by its members). Also not in the box: any data you must bring, and advice of any kind (not safety advice).
PROOF · SELFTEST 14/14 · WITNESSED IN CLAUDE 2026-10-13 ON FICTIONAL FIXTURES · THE TEST PROMPTS IN FRESH CHATS OWED · EDITION 1 · PUNCH F3EB8F2C3E4531FA9BFC292F
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º 1211 — 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 CARD’S OWN SELFTEST.MD
trailreport.py, every command showing its working.
A small Python program, standard library only. Your AI runs it; you can too. The block below is pasted from the card’s own SELFTEST.md, as printed when it was run from inside the packet.
latest report per segment with its age: FRESH, AGING, STALE (no current word) or CLOSED (as of ...)
conflicts
segments whose reports in the window before --now disagree
digest
every trail on one line: closed segments, fresh, aging and stale counts, latest word
selftest
14 checks that prove the machine; it must print selftest 14/14
THE SELFTEST, AS PRINTED
ok 1 log appends a valid report
ok 2 log rejects a condition outside the list (exit 2)
ok 3 log rejects a bad time or a blank reporter (exit 2)
ok 4 status: 28h-old report is FRESH and carries who and when
ok 5 status: 5-day-old report is AGING
ok 6 status: 21-day-old report is STALE, no current word, and never says open or dry
ok 7 status: a 40-day-old closed report still prints CLOSED (as of ...)
ok 8 status: a later report on the same segment ends a closure
ok 9 status never prints the word safe, even from a note
ok 10 status ignores reports dated after --now
ok 11 status refuses a trail with no reports (exit 1)
ok 12 conflicts finds snow vs ice within 24h and nothing older
ok 13 digest prints one line per trail, byte-identical across runs
ok 14 comment lines are skipped
selftest 14/14
THE RUN IS PASTED FROM THE CARD’S OWN SELFTEST.MD AS PRINTED. ITS FIXTURES ARE FICTIONAL, INVENTED FOR THE TEST; NO PRIVATE PERSON IS NAMED.
QUESTIONS AT THE TABLE
Asked before the wire.
What does it need from me?
Reports from your club or community, each with a time and a reporter. Your trail and segment names. If something it needs is missing, it says what is missing and stops there.
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 machine's selftest (14/14), run from inside the packet in Claude on 2026-10-13 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: The 8 test prompts asked in fresh chats with the card installed. Until they are run and scored, the tests are owed. Any run on real data. Every demo file is fictional. 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 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. LICENSE-NOTE.md rides in the packet and is the licence. It is not safety advice.
What will it never do?
It never calls a trail safe; never ages out a closure on its own; never shows a stale report as current.
