Lexicon Garden

pet.trezy.confessForgeries

Looks for records of the caller's that an ingest guard refused, and if there are any, writes the note twice: once into the game's own repo through a linked repo, where the caller cannot reach it, and once into the caller's repo, where they can delete it. Called on sign-in. It changes nothing about what the account may do — the forged records were refused at ingest, so the ledger was never wrong — and it is safe to call on every visit: an unchanged list rewrites nothing.

Repository @trezy.pet did:plc:ollch4g7tes2reb5eceiwuol namespace authority
Details · procedure
Kindprocedure
Authoritytrezy.pet
Indexed
Compare Edit in builder → Fork →

Procedure

procedure · POST

Output

application/json

central

string

What happened to the game's copy — the one that matters. `written` is new or updated, `unchanged` means the note already said this, `unavailable` means the linked repo could not be reached and NOTHING was recorded durably.

  • knownValues: written | unchanged | unavailable

error

string

Present instead of a result. `rejections-unavailable` means the store could not be read, which must NOT be treated as an innocent account — a caller that took it that way would overwrite a real note with an empty one.

  • knownValues: rejections-unavailable

forgeries

requiredinteger

How many refused records the caller has. Zero is the ordinary answer and the successful one.

  • minimum: 0

message

string

own

string

What happened to the caller's copy. `refused` is ordinary rather than alarming: they may simply not have granted the collection, and the durable copy does not depend on it.

  • knownValues: written | unchanged | refused

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • pet.trezy.shameOnYou

    record

    A note that somebody was caught forging records. Written in TWO places for two different reasons: one copy in the game's own repo, keyed by the offender's DID, which they cannot delete and which is the durable account; and one copy in the offender's repo, which they can delete the moment they notice — and noticing is the point of that one. Neither is a punishment. Nothing in the game reads these records or behaves differently because one exists; the forged records were already refused at ingest,

  • pet.trezy.getForgeries

    query

    Every record of this account's that an ingest guard refused, one entry each, with the reason written out. Reads `trezy_pet_rejections`, which the guards fill as forged records arrive on the firehose — so this is a report of what was already stopped, not a check performed now. Nothing here changes what the account may do: the refusal happened at ingest and the ledger never saw the record.