Expand description
Durable public AT Protocol repository transactions.
This module is the storage boundary between native authorization and the public repository codec. It keeps public record bytes and public commit bytes in a separate RocksDB key namespace, and writes the record, signed head and publication intent in one batch. It deliberately does not mint identities, evaluate native policy itself, or expose native signing keys. A caller must supply the native authorization gate for every request.
Structs§
- Hosted
Account Public Repo Writer - Hosted
Account Self Authorizer - Public
Commit Result - Durable result of a successful public repository transaction.
- Public
Create Request - A request to create one immutable public record under an owned repo.
- Public
Pending Create - Public
Repo Snapshot - Public
Repo Store - Durable public repository storage. It uses a distinct RocksDB directory and key namespace so native signed artifacts are never re-encoded as public bytes.
- Public
Repo Writer - Public repository writer with an explicit native authorization gate.
Enums§
- Public
Create Preparation - Public
Repo Write Error - Write failures are classified at their origin. HTTP callers must use these variants and fixed public messages; sources are for local diagnostics only.
Constants§
- MAX_
PUBLIC_ RECORD_ BYTES - Deployment ceiling on complete canonical DAG-CBOR record bytes (64 KiB). A conservative storage policy, not a universal protocol maximum; large payloads belong in linked blobs. Includes CBOR map/type/length overhead. See https://atproto.com/specs/repository#security-considerations.
- MAX_
PUBLIC_ SNAPSHOT_ BYTES - MVP repository capacity: bounds raw records, decoded trees and MST work for every snapshot caller. Key bytes count too; tiny records also have a limit.
- MAX_
PUBLIC_ SNAPSHOT_ RECORDS
Traits§
- Public
Publication Authorizer - Native policy gate required by PublicRepoWriter.
Functions§
- json_
to_ dag_ cbor - Convert AT JSON into the value type used by the public codec. Reserved
single-key
$linkand$bytesobjects become links and byte strings, never ordinary maps. Invalid wrappers, floats and integers outside signed 64-bit range are rejected before serialization.