BFE EngineeringandClaude Opus 4.8
189f7aec38
- Dual license (LICENSE / LICENSE-MIT / LICENSE-APACHE) matching the crate manifests. - ADRs 0001-0005: kernel base (direct 5.10->6.18.46 forward-port), tiered MC/DC, standalone repo, CI runner (3rd repo-scoped runner on 0640), driver source-of-truth. - README goal 1 reconciled to the verified 6.18.46 forward-port (was stale plan44/6.6). - Drop tracked build objects (*.o now gitignored). - Capture the display (VOP dclk-pol + WIN1) and GT911 touch bring-up VERIFIED docs + capabilities-audit update from this session. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
974 B
974 B
ADR 0003 — warden-sdk is a standalone repo
Status: Accepted (2026-08-25).
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 bfe-noah/warden-sdk GitHub repo, 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 code-review-harness run, green CI, and [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-deploymentis handled.