THE HOUSEHOLD ROBOT CARD · a home's robots as one crew, by its rules
WAKES WHEN a household sets rules for its robots, or asks whether a robot may do something
THE LOOP
template · members, rooms, quiet hours
check · the five parts of a house file
may · yes or no, with the rule deciding
change · signed by enough adults
read it together as a household
NEVER
Let a child or guest command what adults keep
Send a robot into a room kept private
Call a check of house rules a safety approval
IT MAKES check — the five parts of a house file, each PASS or FAIL; may — YES or NO, with the rule that decides; change — what changes, and whether enough of the right people signed; template — a house file to start from.
THE STANDARD one crew, one file; the floor; private means private; quiet hours hold; changed by the right people; a check, not a safety approval.
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 · AFEB42409D44F5BCF94DD56F
CITE THIS CARDTHE HOUSEHOLD ROBOT CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=household-robot-card. Punch AFEB42409D44F5BCF94DD56F. Retrieved 2026-10-11.
What it is.
A home's robots run as one crew under one written house rule file. It waits on robots in ordinary homes; today it serves the robot vacuums, smart locks and speakers a household already has. check reads the file for the members and what each may command; children and guests on restricted rights, under a floor of actions only an adult may command (unlocking, cooking, medicine, blades, buying and the like); private rooms no robot enters, or enters only with a named member's consent; quiet hours; and who may change the rules and how many must sign. may answers "may robot X do Y in room Z for person P now?" with YES or NO and the one rule that decides it. change lists what a new rule file changes and whether enough of the right people signed it. template writes a house file to start from. A check, not a safety approval.
It carries a machine that shows its working: check — the five parts of a house file, each PASS or FAIL; may — YES or NO, with the rule that decides; change — what changes, and whether enough of the right people signed; template — a house file to start from — 8 checks in its selftest, every command on the record. It will never let a child or guest command what adults keep; never send a robot into a room kept private; never call a check of house rules a safety approval.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
ONE CREW, ONE FILEEvery robot in the home answers to the same written rules.
THE FLOORUnlocking, opening the door, cooking, medicine, blades, buying, driving and changing the rules are for adults only, whatever the file says.
PRIVATE MEANS PRIVATEA room marked never is never entered; a room marked consent is entered only with a named member's consent.
QUIET HOURS HOLDAcross midnight too, with only the actions the file allows then.
CHANGED BY THE RIGHT PEOPLEA new rule file stands only when signed by enough of the adults the old file names, and only if it passes its own check.
A CHECK, NOT A SAFETY APPROVALIt answers from the house's rules and drives no robot; a robot's own safety systems come first.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-HOUSE-FILE.md
THE MACHINEhomecrew.py · four commandscheck — the five parts of a house file, each PASS or FAIL; may — YES or NO, with the rule that decides; change — what changes, and whether enough of the right people signed; template — a house file to start from. 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.
check The five parts of a house file, each PASS or FAIL
may YES or NO, with the rule that decides
change What changes, and whether enough of the right people signed
template A house file to start from
On the record The template house (two adults, two children, two robots, three private rooms) passes all five parts. At 10:15 a parent may have the mop clean the kitchen; the teen's room is shut to it until the teen consents; the bathroom stays shut even with consent; the small child cannot have the arm unlock a door, by the floor; at 22:10 cleaning is refused by quiet hours while a guest may still have something fetched. Moving quiet hours to 22:30 is not accepted on one parent's signature and is on both; letting the teen command cooking is not accepted even on both, because the new file breaks the floor.
What it will never do.
It will never let a child or guest command what adults keep; never send a robot into a room kept private; never call a check of house rules a safety approval.
It waits on robots in ordinary homes. It answers from the house file alone: it does not see the robot, the room or who is really speaking, and it does not drive a robot. The floor is the card's own and no file can loosen it. Emergencies belong to the robot's own safety systems and the people present. A check of the house's rules, not a safety approval. 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-HOUSE-FILE.md — the guide in references/, in the card's own voice
scripts/homecrew.py — the machine: check · may · change · template, 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 AFEB42409D44F5BCF94DD56F
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º 1179 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
homecrew.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.
check
the five parts of a house file, each PASS or FAIL
may
YES or NO, with the rule that decides
change
what changes, and whether enough of the right people signed
template
a house file to start from
selftest
8 checks that prove the machine; it must print 8/8
template · A HOUSE FILE TO START FROM
$ python3 scripts/homecrew.py template --out house.json
wrote house.json · a house of two adults, two children, two robots, three private rooms and quiet hours; replace every value with your own
check · THE FIVE PARTS OF A HOUSE FILE, EACH PASS OR FAIL
$ python3 scripts/homecrew.py check house.json
house.json · a family of four · house rules for the robots
PASS · members and rights · 4 members (2 adults) · 2 robots: mop (clean, tidy, fetch), arm (cook, carry, fetch, tidy, open-door, unlock)
PASS · children and guests · 2 children · guests may ask: fetch · only adults: unlock, open-door, cook, give-medicine, use-blade, buy, drive, change-rules
PASS · private rooms · bathroom (never), parents-bedroom (with consent of parent1 or parent2), teen-bedroom (with consent of teen)
PASS · quiet hours · 21:30 to 07:00 · allowed then: fetch
PASS · who may change the rules · parent1, parent2 · 2 must sign
PASS · 5 of 5 parts in place
a check of the house's own rules, not a safety approval
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json mop clean kitchen parent1 --at 10:15
house.json · may mop clean in kitchen for parent1 at 10:15?
YES · members · parent1 may command clean; kitchen is open; 10:15 is outside quiet hours
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json mop clean teen-bedroom parent2 --at 10:15
house.json · may mop clean in teen-bedroom for parent2 at 10:15?
NO · private rooms · a robot enters teen-bedroom only with the consent of teen
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json mop clean teen-bedroom parent2 --at 10:15 --consent teen
house.json · may mop clean in teen-bedroom for parent2 at 10:15 (consent given by teen)?
YES · members · parent2 may command clean; teen-bedroom is private, entered with the consent of teen; 10:15 is outside quiet hours
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json mop clean bathroom parent1 --at 10:15 --consent parent1
house.json · may mop clean in bathroom for parent1 at 10:15 (consent given by parent1)?
NO · private rooms · no robot enters bathroom, with or without consent
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json arm unlock hall small --at 16:00
house.json · may arm unlock in hall for small at 16:00?
NO · the floor · only an adult of the house may command unlock, whatever the file says
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json mop clean kitchen parent1 --at 22:10
house.json · may mop clean in kitchen for parent1 at 22:10?
NO · quiet hours · 21:30 to 07:00; only fetch then
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
may · YES OR NO, WITH THE RULE THAT DECIDES
$ python3 scripts/homecrew.py may house.json arm fetch kitchen guest:aunt --at 22:10
house.json · may arm fetch in kitchen for guest:aunt at 22:10?
YES · guests · guest:aunt may command fetch; kitchen is open; 22:10 is in quiet hours, when fetch is allowed
a check of the house's own rules, not a safety approval: the robot's own safety systems come first
change · WHAT CHANGES, AND WHETHER ENOUGH OF THE RIGHT PEOPLE SIGNED
change · WHAT CHANGES, AND WHETHER ENOUGH OF THE RIGHT PEOPLE SIGNED
$ python3 scripts/homecrew.py change house.json later.json --by parent1,parent2
house.json → later.json · 1 change
quiet_hours: {"from": "21:30", "to": "07:00", "allow": ["fetch"]} → {"from": "22:30", "to": "07:00", "allow": ["fetch"]}
ACCEPTED · signed by parent1, parent2, as the old file asks (2 of parent1, parent2), and the new file passes its check
change · WHAT CHANGES, AND WHETHER ENOUGH OF THE RIGHT PEOPLE SIGNED
$ python3 scripts/homecrew.py change house.json teen-cooks.json --by parent1,parent2
house.json → teen-cooks.json · 1 change
members: teen changed: {"rights": ["clean", "fetch", "carry", "tidy"]} → {"rights": ["clean", "fetch", "carry", "tidy", "cook"]}
NOT ACCEPTED · signed by enough, but the new file fails its own check (1 part)
check · THE FIVE PARTS OF A HOUSE FILE, EACH PASS OR FAIL
$ python3 scripts/homecrew.py check teen-cooks.json
teen-cooks.json · a family of four · house rules for the robots
PASS · members and rights · 4 members (2 adults) · 2 robots: mop (clean, tidy, fetch), arm (cook, carry, fetch, tidy, open-door, unlock)
FAIL · children and guests · teen is a child granted cook, which only an adult may command
PASS · private rooms · bathroom (never), parents-bedroom (with consent of parent1 or parent2), teen-bedroom (with consent of teen)
PASS · quiet hours · 21:30 to 07:00 · allowed then: fetch
PASS · who may change the rules · parent1, parent2 · 2 must sign
FAIL · 1 of 5 parts to mend
a check of the house's own rules, not a safety approval
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?
Template · members, rooms, quiet hours. It asks first for the house file: the members (adult or child) and what each may command, what guests may ask, the robots and what each can do, the private rooms and whose consent opens them, the quiet hours, and who may change the rules.
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. It waits on robots in ordinary homes. It answers from the house file alone: it does not see the robot, the room or who is really speaking, and it does not drive a robot. The floor is the card's own and no file can loosen it. Emergencies belong to the robot's own safety systems and the people present. A check of the house's rules, not a safety approval.
What will it never do?
It will never let a child or guest command what adults keep; never send a robot into a room kept private; never call a check of house rules a safety approval.
