Skip to content

SYSTEM Cited by 1 source

Lakebase App Dev Kit

What it is

The Lakebase App Dev Kit is an open-source toolkit (github.com/databricks-solutions/lakebase-app-dev-kit) maintained by Databricks Solutions that ships two executable state machines for teams using Lakebase database branching:

  1. SCM workflow — a five-state machine (scaffold-complete → feature-claimed → pr-ready → ci-green → merged) that governs all branch operations for both humans and agents.
  2. TDD workflow — an opt-in layer with six per-role agents (spec-author, architect-reviewer, test-strategist, scrum-master, driver, navigator) that fires between feature-claimed and pr-ready.

Both workflows use the artifact-as-API model: each transition produces schema-validated artifacts that the next gate consumes.

Architecture

SCM state machine

The gate surface is .lakebase/workflow-state.json, validated against scm-workflow-state.schema.json. Each state transition is driven by a dedicated CLI command:

Transition CLI
→ feature-claimed lakebase-scm-claim-feature-branch
→ pr-ready lakebase-scm-prepare-pr
→ ci-green lakebase-scm-wait-ci
→ merged lakebase-scm-merge

Gates are blocking, not advisory — a failed precondition leaves the machine recoverable at the prior state. Agents cannot invent parallel paths or retry in a different shape.

TDD layer

Fires between SCM states feature-claimed and pr-ready. Calls down into SCM for branch operations; does not call up. Dependency is one-way.

Roles and their outputs: - Spec-author → structured feature artifact (schema-validated) - Architect-reviewer → architecture.json + prose - Test-strategist → test-list.json + rendered markdown - Scrum-master → orchestrates build cycles on experiment branches - Driver + Navigator → RED-GREEN-REFACTOR inner loop

Each role has documented inputs/outputs validated against a schema. Missing or malformed artifacts are treated as failed gates.

Design principles

  • Substrate enforces, agents comply. The CLIs validate preconditions before doing work; agents call CLIs and cannot route around them.
  • Artifact is the API. workflow-state.json crosses the boundary between gate transitions; no chat-window context is relied upon.
  • Structural decisions are recorded, not discovered. Tier hierarchy, source tier, promotion path, and handoff contracts belong to architect/scrum-master roles and are declared once.

Seen in

Last updated · 542 distilled / 1,571 read