pet.trezy.getDiagnostics

Everything the server knows about the CALLER's own game state. Read-only; writes nothing. Takes no input at all, and that is the security model: with no `did` parameter there is no way to ask about anybody else, so cross-account access is impossible by construction rather than gated by a check that could later be loosened. A PROCEDURE rather than a query for one concrete reason: HappyView enforces authentication on procedures at the transport, so an unauthenticated call gets a 401 and this script never runs, and `caller_did` is therefore guaranteed to be set. A query would receive `caller_did` too — it is `string?` in the query globals — but a Lua script cannot set its own HTTP status (src/error.rs:143 maps every raise to 500), so a query could only answer an anonymous caller with a 200 carrying an error, or a 500. The 401 has to come from the transport. It exists because diagnosing a stuck pet took an admin log, four greps and a chain of inference off two public endpoints. The ledger, the grant and the index are the three things that disagree in practice, and none of them was observable. This reports what each says and lets the reader compare, rather than deciding who is right.

Repository @trezy.pet did:plc:ollch4g7tes2reb5eceiwuol namespace authority

Details · procedure

Kind	procedure
Authority	trezy.pet
Indexed	48d ago · 2026-09-24

Compare Edit in builder → Fork →

Procedure

procedure · POST

Output

application/json

config

ref

The caps as this instance actually reads them, not as the record on disk says.

Reference

#config

did

string

The caller, echoed back. Always the authenticated DID — there is no way to ask about another account.

error

string

Reserved. Every failure this script can have is per-store and reported through `unreadable` instead, because a diagnostic that answers nothing is less useful than one that answers what it could reach and names what it could not.

knownValues: unreadable

grant

ref

The starter grant row, absent when the player never had one.

Reference

#grant

message

string

money

ref

Reference

#money

pets

array

Every row in the pet ledger for this player, retired ones included, each paired with whether the index has the matching record. A row with indexed=false is the state that made a pet invisible and unrecoverable on 2026-07-30.

itemsref

Reference

#pet

rejections

array

Rejection rows by reason. A stale row here is what put a false accusation in front of a player once, so seeing them matters.

itemsref

Reference

#reasonCount

sleepingInteractions

integer

How many of the caller's activity records landed inside their species' published sleep window. A non-zero value is a bug in createInteraction or resolveFeeding — the only two things that can mint a signed activity record — and is NEVER evidence that the player forged anything. Absent, rather than zero, when the sleep config or the activity store could not be read; check `unreadable`.

minimum: 0

unreadable

array

Which stores could not be read on this call, by name: pet-ledger, pet-index, grants, wallet-record, highwater, rejections, game-config, sleep-config, sleeping-interactions. NOT cosmetic — every absent value elsewhere in this answer is ambiguous until you have read this. An unreadable pet-index would otherwise make every pet look un-indexed, which is the exact wrong conclusion to hand somebody debugging a missing pet.

itemsstring

wallet

ref

Reference

#wallet

#config

object

Properties

activePetCap

integer

dayLengthSeconds

integer

The published game day length this instance is reading, in real seconds.

sleepWindows

integer

How many sleep windows the published config carries, so the reader can tell a present-but-empty table from one that failed to read.

minimum: 0

stageMoneyCap

integer

starterGrantCap

integer

#grant

object

Properties

amount

requiredinteger

grantedAt

string

#money

object

The balance decomposed, so an unexpected number can be attributed instead of guessed at. balance = collected + granted - spent, and every term is reported because two of them being wrong in opposite directions looks exactly like both being right.

Properties

balance

integer

collected

integer

granted

integer

spent

integer

#pet

object

Properties

active

boolean

createdAt

string

indexed

boolean

Whether happyview_records holds the record this ledger row claims. False means the game cannot see a pet it believes the player owns. ABSENT means the index could not be read, which is not the same as false — check `unreadable` before concluding anything from its absence.

#reasonCount

object

Properties

count

requiredinteger

reason

requiredstring

#wallet

object