Design Records (RFCs)
An RFC records a design before it was built and the alternatives it rejected. They explain why; for how barca behaves today, use the reference. Each RFC states its status (Accepted, Implemented in a release, or Superseded) at the top. The Process & Template page explains how to write one.
- RFC-0001: Node Kinds & Freshness Model
The asset/sensor/task vocabulary and the Always/Manual/Schedule freshness contract.
- RFC-0002: CLI Surface
The barca binary — commands, flags, exit codes, and the stdout/stderr contract.
- RFC-0003: Decorator Surface & Python API
@asset/@sensor/@task/@sink, partitions, parallel(), and the barca.api programmatic surface.
- RFC-0004: HTTP Server API
barca serve — endpoints, the async run/poll contract, cron scheduling, and the Python client.
- RFC-0005: Artifact Serialization & Content-Addressed Storage
json/pickle/parquet artifact formats, local and remote storage, staged writes, and @sink.
- RFC-0006: Configuration & Shared Remote State
barca.toml, env var/CLI precedence, --env separation, and the optimistic shared-state sync protocol.
- RFC-0007: Server Mode — the server is the ledger
One deployed barca serve owns the record of what exists. Laptops run their own work against it, or send a run to it. Still one node per run.
- RFC-0008: Freshness Propagation in barca serve
What Always and Manual do at run time: a scheduled tick brings the Always nodes below it up to date in one run; Manual is refreshed by hand only and pins itself.
- RFC-0009: The store as backup, and restore
A remote store with no server is this machine's backup and read-through cache. The metadata database is backed up on the minute, five copies are kept, and restore is one explicit command.
- RFC-0010: Slack Notifications
Setting BARCA_SLACK_WEBHOOK_URL posts to a Slack incoming webhook when a job starts failing, when it recovers, and once a day while it keeps failing. No new config file, no hooks system.
- RFC-0011: Signed URLs
barca.signed_url(uri) returns a time-limited HTTPS link to any object in S3, GCS or Azure using the credentials barca already uses, and barca get -o url returns one for a result.
- RFC-0012: A Size Limit for .barca
max_size caps what barca keeps on disk. Past the limit, barca evicts leftovers, then superseded results, then local copies the store holds, then the least recently read results, and recomputes or refetches anything evicted when it is needed.
- RFC-0013: Batched Partitions
batch= lets one call of a partitioned step compute many keys: N at a time, all of them, or groups you name. Each key keeps its own run hash and artifact, so caching, selection and change detection are the same as one key per call.
- RFC-0015: Configurable Metadata Backup Cadence
Control routine whole-database backups, retain the final shutdown backup, and report local backup storage outside the cache budget.
- RFC-0016: Server Tokens and Resumable Run Events
Opt-in Barca-issued API tokens, browser token management without accounts, consistent client credentials, and attempt-scoped Last-Event-ID replay.