BFE EngineeringandClaude Fable 5
084df85450
The transfer removes the last personal-name slug from the project's public surface; old URLs redirect but the badge and ADR references now point at the canonical home. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018HUayid7W5w7jBdb9Rrj1K
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# ADR 0003 — warden-sdk is a 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/warden-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 warden-sdk 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.
|