Skip to content

docs: extensible firmware & marketplace engineering spec#104

Open
johnbuckman wants to merge 1 commit into
mainfrom
docs/extensible-firmware-spec
Open

docs: extensible firmware & marketplace engineering spec#104
johnbuckman wants to merge 1 commit into
mainfrom
docs/extensible-firmware-spec

Conversation

@johnbuckman

Copy link
Copy Markdown

Adds docs/extensible-firmware-and-marketplace.md — an engineering specification for the proposed extensible-firmware architecture and extension marketplace.

What it covers

  • Native-C extension model (no interpreter, no sandbox) with the rationale from the measured memory envelope.
  • Extension SDK (proposed) — registration via linker section, lifecycle hooks, host API, the two-button model (round-left / square-right), a USB/WiFi command & telemetry bus extensions can observe/extend/take over, and driver capabilities so apps consume drivers by type. Includes a worked grind-by-weight example.
  • Discovery via a openscale-extension GitHub topic + openscale-extension.json manifest.
  • Build & delivery — recipe → Decent-controlled Actions → pre-flight gate.
  • Pre-flight safety gate — deterministic checks + DeepSeek advisory + a hardware-in-the-loop rig (real scale on a server USB port, validated over USB/BLE/WiFi).
  • Ownership-based delivery — seal-number chain, phone-home to /support/api/, no firmware signing.
  • On-scale UX & recovery — non-removable Settings, dual-button recovery entry, three-failed-boot auto-revert.
  • Marketplace & moderation — private immediate, public requires approval.
  • Work breakdown (P0–P4) and open decisions.

The SDK surface in §5 is a proposal for review/ratification, not a frozen API.

🤖 Generated with Claude Code

Specification for a native-C extension architecture: an on-device
extension framework (registration, lifecycle hooks, host API incl.
buttons and a USB/WiFi command-telemetry bus, driver capabilities),
a GitHub-topic + manifest discovery model, a Decent-controlled build
pipeline with a hardware-in-the-loop pre-flight gate, seal-number
ownership-based OTA delivery, on-scale settings/app-manager with
three-failed-boot auto-revert, and a public-extension moderation flow.

SDK surface is proposed and subject to ratification.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants