Every pet, a sovereign handle.
Today an animal's identity is fragmented across a microchip number, a vet's database, a breeder's paper book, and a shelter's spreadsheet — and 90% of it evaporates the first time they change owners. Hylaq Pet makes the pet itself the durable identity. Vet records, lineage, training, microchip, and insurance all travel with the animal forever.
The paradigm break
The cleanest way to model a pet is @owner/petname — a sub-handle of the current owner, the same pattern Compute Mesh uses for @owner/device-XX. The pet's name (the right side) and a durable internal id persist forever. Only the parent (the left side) changes when ownership transfers.
That's the architectural payoff. When Titan gets adopted, inherited, or rehomed, his vet history, microchip, breeder lineage, behavior notes, and insurance pool membership all come with him. Today they don't. Today every owner starts at zero.
What we replace
Six paws. One protocol.
Why @owner/name beats @name-owner
Shipped today
- src/lib/pets/ — types, registry with stable internal id, attestation lifecycle (8 kinds), two-sided signed transfer with Settlement-Grid-atomic price, lost-and-found with haversine geo-radius matching, micro-insurance pool with Settlement-Grid-atomic claim payouts, BigInt-safe wire serialize
- 12 API routes — register, attest, transfer/propose, transfer/accept, transfer/complete, lost, found, reunion, insurance/pools (GET + POST), insurance/enroll, insurance/claim, insurance/decide, insurance/pay, lookup, health
- Durability invariant proven by jest end-to-end test — register @trudell/titan -> attest VET_VISIT -> transfer to @nephew -> assert pet.id unchanged + petKey @nephew/titan + VET_VISIT still attached + PRIOR_OWNER attestation auto-written
- Lost-and-found radius matching — haversine distance, 50km default, species + radius gate; tested with NYC vs LA negative case
- Insurance pipeline — createPool -> enroll -> file -> decide (auto-APPROVE up to 80% of reserve) -> payClaim via Settlement Grid yields a sha256 receipt; oversized claims auto-REJECT
- Phase-2 swap points called out — persist to Postgres, vet practice-management integrations for real attestations, microchip-scanner integrations at vets/shelters, real actuarial pricing + reinsurance, working-animal verticals
The pet outlives any owner. The protocol should too.
Microchips were a 1990s fix to a 1990s problem. Hylaq Pet is a protocol-native, ownership-durable, vet-attested identity layer for every animal on Earth. Same primitives as the rest of the stack — handle, payment rail, intelligence — pointed at a $260B/yr industry that's been begging for a sovereign-identity layer for 30 years.