Files
bfe-core1106-sdk/docs/decisions/0003-standalone-repo.md
T
BFE Engineering d465d97b99 docs: repo renamed to bfe-core1106-sdk
The last product-first artifact after ADR-0008 was the repo name itself.
Current and forward-looking references updated; period-bound history in
the ADRs keeps the old name, with the rename recorded in ADR-0008.
Crate names, WARDEN_* env vars, and binaries are unchanged.
2026-08-31 07:17:00 -06:00

1.2 KiB

ADR 0003 — Standalone Repo

Status: Accepted (2026-08-25). Repo-visibility half superseded by ADR-0007 (2026-08-30) — warden-sdk went public; the "private for now" consequence below no longer holds. Original decision kept for the record.

Context

Our real SDK changes lived as uncommitted edits in a 2GB opaque vendor fork, with no CI, tests, or versioning of their own. The SDK requirement (future-features-2 §SDK) calls for "its own repo, held to firmware standards."

Decision

A private warden-sdk GitHub repo (now blueflare-energy/bfe-core1106-sdk and public per ADR-0007), standalone from day one with its own CI/versioning. Work lands on a bringup branch; the first commit to main is gated on a passing review run, green CI, and the maintainer's fresh explicit go-ahead.

Consequences

  • flare-edge consumes this repo later (flared depending on warden-sim, drivers built from here) — a separate, maintainer-gated integration step; flare-edge is not edited by the SDK-completion effort.
  • Private for now (references bench devices / in-progress hardening); can be opened later once scrubbed, matching how flare-deployment is handled.