at.tensei.subscription

The subscriber reads `pipeline` as a feed. It names the subscriber's own pipeline, authored or adopted: adopting another person's pipeline copies it, with its mappings, into the subscriber's repo, and a subscription targets that copy, never the original author's configuration (§1.3). The lexicon language cannot state that the pipeline is in the subscriber's own repo, or that it is an at.tensei.pipeline record.

Repository @tensei.at did:plc:7fk7ea7vlnlpzgy225x66vro namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritytensei.at
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

pipeline

requiredstring · at-uri

at://<the subscriber's DID>/at.tensei.pipeline/<rkey>. Not pinned to a CID: a subscription follows the subscriber's own edits to their pipeline.

Similar lexicons

semantic match

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

  • Record declaring a subscription to a publication.

  • Record declaring a subscription to a series.

  • Use the lenses published by another account. Like a follow, it lives in the subscriber's repository.

  • A subscription record in the social graph. Represents a user following a publication.

  • page.cavu.graph.authorSubscription

    record not from the namespace authority

    Record declaring a subscription to an author — the sibling of site.standard.graph.subscription, which targets publications only. Following an author means wanting the books they have not written yet, so the subject is the author's DID rather than any record: a publication that does not exist yet cannot be referenced. One record per (reader, author) by convention: clients list their own repo and reuse the existing record rather than create a second (the same convention page.cavu.progress uses). T