pet.trezy.confessForgeries

trezy.pet

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "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.",
      "output": {
        "encoding": "application/json",
        "schema": {
          "properties": {
            "central": {
              "description": "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"
              ],
              "type": "string"
            },
            "error": {
              "description": "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"
              ],
              "type": "string"
            },
            "forgeries": {
              "description": "How many refused records the caller has. Zero is the ordinary answer and the successful one.",
              "minimum": 0,
              "type": "integer"
            },
            "message": {
              "type": "string"
            },
            "own": {
              "description": "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"
              ],
              "type": "string"
            }
          },
          "required": [
            "forgeries"
          ],
          "type": "object"
        }
      },
      "type": "procedure"
    }
  },
  "id": "pet.trezy.confessForgeries",
  "lexicon": 1
}

Validate Record

Validate a record against pet.trezy.confessForgeries

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:ollch4g7tes2reb5eceiwuol
CID
bafyreibpiigjm5wcd3qrcvbpcmvpqu2swpr2ggfcu6rzqwwvcdhvqz7gyy
Indexed At
2026-08-09 16:18 UTC
AT-URI
at://did:plc:ollch4g7tes2reb5eceiwuol/com.atproto.lexicon.schema/pet.trezy.confessForgeries

Similar Lexicons

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

  • 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; …

  • 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 rep…

Lexicon Garden

@