games.cavu.codex
A card in a game's world: an item (a program, a weapon), an encounter (a piece of ICE, a monster, a trap), a character or a place. One record per card, not a player's copy of one: a player owns an item as an equipment.rpg.item whose `give` is this record's URI and whose stats carry a strongRef to it. It lives in the repo of the player whose play made it, signed by the game service so its stats can be trusted. rkey MUST be '<game>:<id>' (a TID); readers reject records whose rkey doesn't start with their own `game`.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | cavu.games |
| Indexed |
Record
record · key anyProperties
What sort of card, in terms any app understands: something a player can own (item), something a player faces (encounter), someone (character), somewhere (place).
maxLength: 32knownValues: item | encounter | character | place
description
stringmaxLength: 3000maxGraphemes: 300
image
blobmaxSize: 1000000accept: image/png, image/jpeg, image/webp
imageAlt
stringAlt text for the image.
maxLength: 3000maxGraphemes: 300
What sort of card in the game's own terms (e.g. 'ice', 'program', 'hardware'). Copied to equipment.rpg.item's `kind` for items.
maxLength: 20
maxLength: 640maxGraphemes: 64
signatures
arraystats
unknownGame-specific, typed by the game: an object with $type in the game's own lexicon (e.g. games.cavu.aiSlop#ice).
#origin
objectHow the thing was made.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
games.cavu.addon
recordContent a player made for a game, such as a Tier Madness category or criterion. It lives in its author's repo; the game uses it only once the game's publisher approves it (a games.cavu.approval whose subject is this record's exact version, so an edit needs approving again). rkey MUST be '<game>:<id>' (a TID); readers reject records whose rkey doesn't start with their own `game`.
-
dev.malpercio.cards.item
recordA card (or sealed pack) held by the repo owner. Not authoritative on its own: validity comes from the chain of strongRefs back to a provider give whose recipient matches the current owner at each hop. Blobs are the owner's local copies and must hash to the CIDs on the root give.