Skip to content

ADR-0007: What is the System of Record for Operational Work?

Status

Candidate — conclusion UNKNOWN until receipts RX-BD-001 and RX-BD-002 pass on NAS sandbox or throwaway GitLab repo.

Context

OBSERVED: Operator binding (2026-07-07):

  • Beads + Dolt = operational work ledger (between Gas City orchestration and Gas City runtime).
  • Git = configuration only.
  • Dolt = operational state.

RETRIEVED: Beads stores issue/work state in Dolt; local Dolt DB is SoR for bd commands (SYNC_CONCEPTS.md).

RETRIEVED: Gas City on Oracle is Bluefly execution SoR for convoys/hooks (upstream-lawbooks.md).

INFERRED: Bluefly must not invent a parallel work ledger in Drupal markdown, JSON receipts, or custom sync scripts.

Decision drivers

  1. Reproducible multi-machine collaboration without manual JSON merge.
  2. Alignment with upstream Beads/Dolt semantics.
  3. Separation of config (git) vs operational state (Dolt).
  4. Evidence before standardization — receipts on disposable infrastructure.

Candidates

Candidate Description Pros Cons Validation
C1 — Embedded + Dolt remote Each rig uses embedded mode; sync via bd dolt push/pull on shared git remote (refs/dolt/data). Zero server ops; upstream default for solo/team git workflows. Single-writer per clone; concurrent writers on same embedded DB not supported. RX-BD-001
C2 — Server mode (dolt sql-server) Shared dolt sql-server; clients use bd init --server / gt dolt start. Multi-writer; orchestrator rigs. Server lifecycle, ports, lock behavior must be proven. RX-BD-002
C3 — Federation (peer sync) Peer dolt sql-server instances with bd federation sync. Decentralized; no single hub required. Topology and conflict strategy complexity. UNKNOWN — no receipt yet
C4 — Gas City Oracle beads only Operational work SoR only on Oracle ~/gt; Mac projection read-only. Matches current execution doctrine. Does not alone prove multi-writer or git-remote collaboration. Partial — Oracle verify separate
C5 — Custom Bluefly ledger Drupal/JSON sidecar sync. — Violates upstream-first; forbidden without gap receipt. Rejected (INFERRED)

Modes documented as inputs only

INFERRED: Per operator direction, three Dolt deployment modes are ADR inputs only — not production commitments:

  1. Embedded — UP-BD-021
  2. Server — UP-BD-021
  3. Federation — UP-BD-021

INFERRED: NAS is not designated as the shared Beads server in this ADR.

Decision

UNKNOWN

Select among C1–C4 after:

Receipt Pass criteria
RX-BD-001 Two-clone embedded workflow converges without manual merge, JSON edits, or custom sync
RX-BD-002 Two concurrent server-mode writers complete without lock failures

Consequences (when decided)

  • If C1: Document git-remote + bootstrap as default Bluefly collaboration path for repo-scoped beads.
  • If C2: Document server host authority (Oracle vs sandbox only) and forbid Mac as production server without receipt.
  • If C3: Add federation receipt before production topology claims.
  • If C4: Clarify projection vs execution boundaries in gas-town-workspace-contract.md.

References