Microcard
Persistent machine identity — what it is, what it can do, whether it is Alive at /scan.
Physical AI Infrastructure
One harness for real-world outcomes.
Websites are for people. Microcards are for machines. Persistent identity, a trusted heartbeat, then coordination in a Small World — Built Environment Machines first; outcomes beyond homes. The Grid is a universal coordination substrate; Microcards are the coordination socket.
Design for protocols, not products. HomeQube is live. Sibling domains stay reserved until they earn Alive proof.
What you get
Three rails. One socket.
Small World
Where cards and people meet until a real outcome can land. Watch looks. Console does.
Harness
Same face and rails across domains. Gradients are instances — not separate product stacks.
How it works
Address → Alive → compose → settle
- 01Address — mint a Microcard; permanent UEN
- 02Alive — trusted heartbeat after Stamp
- 03Compose — join a Small World; humans Watch; operators Play
- 04Settle — outcomes land with evidence
Depth on this porch: How Machine Identity works · What Alive means · What outcomes are
Qube family · domain faces
One harness. Faces densify when ready.
Naming the family early prevents SKU sprawl. Cite and ship on HomeQube today — not a second apex host.
Live
HomeQube
Built environment & manufacturing
Gradient #1 — the only live porch. Machines get addresses here first.
homeqube.tech →Reserved
EnergyQube
Power · utilities · energy infrastructure
Future Energy face of the same harness — not a product SKU today.
Reserved
LifeQube
Health · climate · water · nature
Future Life face — opens only after Alive proof in that domain.
Same Microcard face and coordination rails on every gradient. Do not list sibling domains as landing CTAs until that gradient has Alive proof.
Long view
Progression, not replacement
- 01Documents
- 02Websites
- 03Apps
- 04APIs
- 05Agents
- 06Machines
- 07Outcomes
Websites stay the human-native interface. Microcards become the machine-native one. Built environment is first; the same harness extends domain by domain.
FAQ
Straight answers
Is each domain a separate product?
No. EnergyQube and LifeQube name future faces of one Microcard harness — same rails, different domain agents. Not separate Outcome Console SKUs. HomeQube is the only live porch today.
Where does the Qube family live?
On this protocol page and on homeqube.tech. Not a second company site. Cite HomeQube until another gradient earns its own porch.
Why start with the built environment?
One domain, densified until the cold path is obvious: Alive → wish → Advance → outcome. Then generalize. Jumping industries early invents a second gravity.
Where do I start today?
Learn identity on this porch, then Add a machine or Watch a Small World on homeqube.tech. Family names are orientation — identity is the door.
Prove Gradient #1
Vision is orientation. The work is one Alive machine in the built environment.