Lexicon Garden

org.governedcrossing.temp.commitment

DRAFT in the temp namespace; may change without notice. Optional public commitment to the crossing-completion of a completed private substrate crossing, published in the emitter's own repository. A remote proof under the ATProtocol Attestation Specification v1.0 with this profile's repository rule: `cid` is the CIDv1 of the committed record with `signatures` removed and `$sig` inserted, where `$sig` is this commitment record minus `cid`, plus `repository` set to the committed record's `emittedBy`. The committed record is housed in no repository, so a verifier must be given `emittedBy` as the repository DID. This CID differs from the emitter inline-signature CID. Discloses existence, emitter and time only. Never published for a crossing that did not complete, for a crossing-intent, or for a blocked gate check.

Repository @localboundary.bsky.social did:plc:4xoefmmbsulm4xns3kbb6mnk namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritytemp.governedcrossing.org
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

cid

requiredstring · cid

Remote-proof CID of the committed record.

committedAt

requiredstring · datetime

emittedBy

requiredstring · did

Emitting party of the committed record; must equal the housing repository's DID.

previous

ref

Optional link to the emitter's previous commitment.

Reference

Similar lexicons

semantic match

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

  • org.governedcrossing.temp.crossingRecord

    record

    DRAFT in the temp namespace; may change without notice. A projection of a seam:CrossingRecord whose canonical copy lives on the emitting party's own substrate. Published publicly only when the crossing itself was public and, for a substrate crossing, only once it completed; records of blocked gate checks are never published. Private crossings publish at most an org.governedcrossing.temp.commitment. Crossing records are intentionally non-repudiable (every record carries the emitter's inline signa

  • app.certified.signature.proof

    record

    A remote attestation proof record holding the CID of attested content. Lives in the attestor's repository and is referenced from the attested record's `signatures` array via `com.atproto.repo.strongRef`. Conforms to the ATProtocol Attestation Specification.

  • org.governedcrossing.temp.defs

    DRAFT in the temp namespace; may change without notice. Shared definitions for governed crossing records: the inline signature type, record references, and the substrate-crossing extensions. An AT Protocol binding of the seam:CrossingRecord vocabulary (https://jediwright.github.io/seam-stack/vocab/crossing-record/0.1#), which is the semantic contract.

  • network.attested.proof

    record not from the namespace authority

    A remote attestation proof: a standalone record in the attestor's repository that binds, via a canonical attestation CID, to a subject record living elsewhere. Referenced from the subject's `signatures` array via com.atproto.repo.strongRef. The `cid` is computed from the subject record (signatures stripped) with this record's metadata (cid/signature/signatures stripped, `repository` = subject's repo DID added) inserted as $sig, DAG-CBOR + SHA-256 + CIDv1. Verifiers recompute that CID and require

  • network.attested.payment.proof

    record

    A remote attestation record stored in the attestor's repository (creator or broker). Referenced via com.atproto.repo.strongRef in the payment record's signatures array. The attestation CID is computed per the badge.blue spec from the payment record, attestation metadata, and the repository DID — meaning a record copied to a different repository automatically invalidates all its attestations.