AT Protocol · proposed · not yet published
AT Protocol Lexicons
Proposed only. These Lexicons aren't yet published under jollyrogercharter.org's _lexicon DNS record, so other apps can't resolve them, and field names may change through RFC. Nothing on this site publishes records: you publish from your own AT Protocol account, on any server, if and when you choose. Records are public and can be copied; deleting one doesn't remove copies.
The three record types
| NSID | What it records | Schema | Example |
|---|---|---|---|
org.jollyrogercharter.adoption | A project's own declaration that it is working toward JRCv1, pointing to its manifest and, optionally, an assessment record. | adoption.json | example |
org.jollyrogercharter.assessment | A JRCv1 assessment of a software project, published by whoever made it. It records claims and scan results; it is not a certification. | assessment.json | example |
org.jollyrogercharter.contribution | A contribution someone made to the movement or to a project working toward JRCv1: an RFC, criticism, reproduction attempt, fix or review. | contribution.json | example |
An assessment record always says independenceVerified: false; software alone can't establish independence. A scan the tool fetched from GitHub itself says kind: "automated-scan". A scan of a snapshot someone supplied says kind: "replayed-snapshot", because a snapshot can be edited and so proves nothing about the repository. Both carry snapshotSha256, so anyone holding the snapshot can re-run the scan. The example assessment record was built from this repository's own committed snapshot, so it is a replayed snapshot.
Prepare a contribution record
Fill this in to get a record and the com.atproto.repo.createRecord request to send from your own account. It's built and checked in your browser; nothing is sent.
Contribution record
Without JavaScript: jrc tool export_atproto_record --input FILE, then jrc tool prepare_atproto_publication --input FILE.
What publishing would involve
- Your own account on any PDS. Nothing here picks one.
- A client you trust signs you in (app password or OAuth) and sends the prepared request body to your PDS.
- Your PDS returns the record's
at://URI and CID.
Publishing directly from this site with your account is planned, not built: it needs an AT Protocol OAuth client and an explicit consent step. See the capability list.