pet.trezy.foodDrop
One morsel lying on the ground. Lives in the player's `pet.trezy.terrarium` SPACE, not their public repo: it is transient scenery, and a repo record would need a new OAuth scope in three places — which happyview-config.ts documents as breaking sign-in outright when the third is missed. A high price for recording that a morsel is at x=412. ⚠ NOTHING HERE IS SIGNED, SO NOTHING HERE MAY CARRY CONSEQUENCES. setPreferences.lua states the rule this obeys: a space is access control, not attestation. Forging one of these moves your own morsel and nothing else — every claim about who was actually FED is a signed pet.trezy.activity record, written by createInteraction and resolveFeeding and by nothing else.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | trezy.pet |
| Indexed |
Record
record · key tidProperties
When it was put down. ⚠ LOAD-BEARING FOR resolveFeeding, which replays an absence in this order and uses this as the earliest moment the morsel could have been eaten.
The id of a published pet.trezy.food. Validated against the index by dropFood, so a morsel can never name something the client has no way to draw.
Horizontal position in scaled world px. An integer because AT Protocol lexicons cannot express floats — and a pixel is finer than anyone can aim anyway, so nothing is lost.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
pet.trezy.dropFood
procedurePut one morsel on the ground. Writes to the caller's terrarium space; the space is created lazily by the first drop, so a player who never feeds anything never gets one.
-
pet.trezy.food
recordOne kind of food. Published by the game, never by a player — the definitions guard refuses these from anybody but the publisher, the same as species and tiers. A food a client cannot draw must render nothing rather than a substitute, so these outlive any given build on purpose.
-
pet.trezy.resolveFeeding
procedureSettle what happened in the terrarium while nobody was watching, and report the state feeding needs. Called on load. HappyView has no scheduler — the only job trigger is job.run:<type>, fired by jobs.create — so an absence is replayed here rather than ticked by a cron. The player cannot tell the difference: they close the tab with four morsels down and come back to find the pets fed and one morsel left. What they gain is that the gap is computed at the moment it can be REPORTED, and that resolut
-
pet.trezy.createInteraction
procedure