Pilot program · Mind My Presence
The embroidery agent
that lives on an SD card.
PISTICK plugs into your embroidery machine’s USB port as a plain, read-only FAT32 stick. Behind that port an agent works: you describe the piece, Axiom — the interactive common tongue — turns conversation into stitches, and finished designs simply appear on the stick. Designs in, status out.
- Read-only USB face — the machine can never write to the agent
- One deterministic render — eight formats, every major brand
- Protection proves itself before first boot
How it works
You talk. Axiom renders.
Your machine just stitches.
The whole agent fits on one microSD card — the card is the product. No installs, no drivers, no cloud account required to start.
- SpeakDescribe the design in plain language. Axiom, the interactive common tongue, carries the conversation through the universal translator front end — intent in, embroidery parameters out.
- RenderOne deterministic render writes the design to all eight industry formats in a single pass. Every file is hash-pinned to a manifest before it ever leaves the card.
- StitchYour machine browses PISTICK like any USB stick and loads the format it likes best. Nothing executes on your machine — the stick is read-only by construction and cannot be corrupted from the machine side.
And the machine talks back. Stitch progress, color changes and completion mirror through the agent via the machine’s own monitor channel — you hear done before the needle stops.
AXIOM-TEST-H · color 3/3 · completeThe universal library
One card speaks every machine’s language.
Every design is written eight times, from one deterministic render — so the file your machine likes best is already on the stick, whatever brand it is.
Trading up machines later? Your PISTICK moves with you. Same card, different chip file.
Protection
Guarded before it ever boots.
Gate 01
Static sweep — 221 rules
An OWASP Top-10 scanner combs the entire on-card stack for injection, misconfiguration, and secret-handling faults before install. Anything critical stops the build.
Gate 02
Sentinel — and the 13th Man
Sentinel probes dynamically, watching for what static scans can’t see. And when every check reports green, the 13th Man gate assumes they’re all lying — it attacks the stack anyway, in sandbox, hunting for the pass that wasn’t earned.
Gate 03
Claims gate — nothing ships on a promise
Every load-bearing claim in the build carries a tag and an evidence pointer, or the gate refuses to close. 15 of 15 green at press time — and the number isn’t ours to fudge; it’s a script’s.
Protection proves itself before first boot. That’s the house rule.
Proof, not promises
Every number on this page came from a tool.
Built proof-first. Hardware verification (gadget enumeration, hot re-plug, power budget) closes before the first cards ship — pilot members watch it close, step by step.
First stitches, in order of proof.
The pilot is open. Reserve now and your unit ships with its own proof chain — every gate it passed, every hash it matched, delivered with the card. You don’t take our word. You take the evidence.
Pilot pricing announced to the list first · no card charged until your unit’s gates run green