pet.trezy.featureConsent

trezy.pet

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "This keeper is happy for their pets to be Pet of the Week on Bluesky, with an @mention. The record existing is the yes; deleting it is the no. ⚠ PUBLIC ON PURPOSE, unlike pet.trezy.preferences: the weekly pick has to read it and cannot read a permissioned space, and agreeing to be posted about in public says nothing private. Not signed: forging your own consent is consenting, and a copy in anybody else's repo is never read.",
      "key": "literal:self",
      "record": {
        "properties": {
          "createdAt": {
            "format": "datetime",
            "type": "string"
          }
        },
        "required": [
          "createdAt"
        ],
        "type": "object"
      },
      "type": "record"
    }
  },
  "id": "pet.trezy.featureConsent",
  "lexicon": 1
}

Validate Record

Validate a record against pet.trezy.featureConsent

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:ollch4g7tes2reb5eceiwuol
CID
bafyreifiyaawxtt6rfosha4cxcvhvaa4mwtodurt6go6soeckawmps3fyi
Indexed At
2026-09-22 18:24 UTC
AT-URI
at://did:plc:ollch4g7tes2reb5eceiwuol/com.atproto.lexicon.schema/pet.trezy.featureConsent

Similar Lexicons

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

  • Say yes or no to the caller's pets being Pet of the Week. Yes writes pet.trezy.featureConsent/self into the caller's repo; no deletes it. Idempotent both ways.

  • One week's Pet of the Week, held in the publisher's repo. The record key is the ISO week (e.g. 2026-W39), so there is exactly one per week and every step that writes it is idempotent. ⚠ ONLY THE PUBLISHER'S COPY COUNT…

  • The featured keeper's answer for one week, keyed by that ISO week. Either a note to quote in the post (text, possibly empty) or decline: true for 'not this time'. Written only by pet.trezy.replyToFeature.

Lexicon Garden

@