tech.waow.lore.registry

Maps a project to the lore space used for it. Lives in a private tech.waow.lore.space of the person's own (skey = sha256 of "lore-registry"), under their repo, so which spaces they use is not public. The record key is the hex sha256 of the project key. The space may belong to someone else, when they have shared it.

Repository @waow.tech did:plc:siv7zbedip4vcet4v67piibr namespace authority
Details · record, key any
Kindrecord
Record keyany
Authoritylore.waow.tech
Indexed

Record

record · key any

Properties

createdAt

requiredstring · datetime

key

requiredstring

The project key: a normalized git remote such as tangled.org/zzstoatzz.io/pi-extensions, or an absolute directory path when there is no remote.

  • maxLength: 4096

kind

requiredstring

How the key was derived.

  • maxLength: 16
  • knownValues: remote | path

space

requiredstring

The space URI: at://{authority}/space/tech.waow.lore.space/{skey}, where skey is the same hash as this record's key.

  • maxLength: 1024

title

string

How to show the key to a person, e.g. tangled.org/zzstoatzz.io/pi-extensions for a repo-DID key.

  • maxLength: 512
  • maxGraphemes: 256

Similar lexicons

semantic match

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

  • Breadcrumbs left by the people on a project, written when asked. One space per project, keyed by the sha256 of the project key; the owner is the authority and decides who else may read and add. Holds tech.waow.lore.entry records, and tech.waow.lore.registry records in each person's private registry space.

  • Git repository declaration. Record is owned by the repository owner and record-key is slug of the git repository.

  • A reference to a record in the same space. Record keys are unique per repo rather than per space, so a bare key cannot address a record in a space that aggregates many authors.

  • page.cavu.forge.project

    space not from the namespace authority

    A StoryForge project: the working notes behind one book or series — its characters, places and things (entities whose every attribute is a fact on the timeline), the timeline of events, and loose notes (atproto permissioned data, proposal 0016). Anchored on the writer's own DID, so their PDS is both repo host and space host and nothing leaves it. Private by default (member-list policy, no members). Collaborators — a co-writer, an editor — join as members and write into their own repo inside the

  • A did-git ref stored in an AT Protocol repository. Each record maps a repository name and ref name (e.g. refs/heads/main) to the hex SHA-256 object ID it points to.