jake/Lumotia
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(hardware): file pendant research + NLnet GenAI policy; reconcile roadmap

Browse Source 
Two new docs in docs/hardware/:

- pendant-research-2026-04-27.md — buildable plan for a Corbie-paired
  open-hardware audio capture device. Nordic nRF5340 silicon (LE Audio
  is effectively a Nordic monopoly outside Apple/Samsung), Raytac
  MDBT53-1M pre-cert module to dodge GBP 8-15k EMC chamber bill, drop
  Wi-Fi for USB-MSC sync, single Knowles SPH0645 mic, microSD disguised
  as cassette spool, hardware-locked LED in series with mic V_DD,
  Sifam analogue VU meter, Sony WM-D6C / Nagra E / Playdate / TP-7
  aesthetic. ~GBP 107 BOM at qty 100. Funding sequence: NLnet first
  (deadline 2026/06/01), Corbie waitlist soft pre-orders second,
  Crowd Supply third. 22-month timeline, ~GBP 1,200 founder personal
  capital exposure.

- nlnet-genai-policy.md — verbatim NLnet GenAI policy v1.1 with TL;DR
  and a Corbie-specific compliance plan. Read before drafting any
  NLnet application or doing GenAI-assisted work on a funded milestone.

Roadmap entry under "Post-v0.1 ideas -> Hardware companion" rewritten
to match the compass research. The earlier off-the-cuff Tier-A/Tier-B
sketch (Hailo, Wi-Fi 6, three-mic array) is wrong on most decisions
and is superseded.

Hard discipline: hardware never ships before Corbie software hits
GBP 2k MRR.
This commit is contained in:
Jake
2026-04-27 11:48:52 +01:00
parent fcca6509cc
commit 7dea5533f7
3 changed files with 610 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

270
docs/hardware/nlnet-genai-policy.md Normal file
View File

@@ -0,0 +1,270 @@
---
name: "NLnet GenAI policy (v1.1, 2026-01-26)"
description: "Verbatim NLnet GenAI policy filed alongside the pendant research because NLnet NGI Zero Commons Fund is the recommended primary funding pathway. Read before drafting any NLnet application or doing GenAI-assisted work on a funded project."
type: reference
tags: [funding, nlnet, genai-policy, compliance, open-source, foss, hardware, pendant]
captured_at: 2026/04/27
status: active
related:
- docs/hardware/pendant-research-2026-04-27.md
source_url: https://nlnet.nl/foundation/policies/generativeAI/
policy_in_force: 2025/12/08
policy_version: 1.1 (2026/01/26)
---
# NLnet GenAI policy
Filed in this folder because the pendant research recommends NLnet NGI
Zero Commons Fund as the primary funding pathway. Any application we
submit, and any GenAI-assisted work on a funded project, must comply with
this policy.
## TL;DR
If we apply to NLnet and use GenAI in the application:
1. **Disclose the use.** Drafting, translation, summarisation. All count.
2. **Maintain a prompt provenance log:** model used, dates and times of
prompts, the prompts themselves, the unedited output. Submit with the
application.
3. **Trust your own skills first.** NLnet explicitly encourage applicants
to write their own proposals.
If we receive a grant and use GenAI during project development:
1. **All outputs must be legally publishable under a FLOS licence.**
Verify GenAI-assisted code does not reproduce copyrighted material.
2. **Purely AI-generated outputs are not eligible for payment.** Under EU
law they fall into the public domain (no copyright protection).
3. **Don't pass AI work off as your own.** Human contributors remain
accountable for accuracy, originality, integration.
4. **Disclose substantive use publicly.** README declaration of how
GenAI is used (logic, tests, docs, etc.).
5. **Mark generated content per commit.** Specify model and version,
include prompts and outputs (or summary), in commit messages or
equivalent. Don't host the log on a third-party platform that
could disappear.
Failure to comply may result in rejection of the proposal or termination
of a running grant.
## Funding pathway hooks
- **Next deadline:** apply before **1 June 2026**.
- **Office hour (live Q&A):** 2026/04/29, "Ask us Anything"
https://nlnet.nl/events/20260429/office-hour/index.html (worth attending
given the deadline proximity).
- **Recent precedent:** 57 projects received NGI Zero grants in the
2026-04-09 announcement. Pendant research notes audio-hardware
precedents (Tiliqua, MILAN) that are directly relevant.
- **Application format:** short web form. The compass research estimates
4 to 8 hours of focused effort. Two-month decision after submission.
## Pendant project compliance plan
If we apply for the Corbie Pendant track:
- **Licences:** CERN-OHL-S-2.0 for hardware, GPL-3.0-or-later for
firmware, CC BY-SA 4.0 for documentation. (Picked in the compass
research.)
- **Prompt provenance log:** start one *before* drafting. Capture every
Wren/Claude prompt that contributes to the application text, in a
structured log alongside the proposal draft.
- **README declaration:** Corbie's existing "Pre-alpha; contribution
process TBD" line stays, plus a new GenAI-disclosure section before
any NLnet milestone work begins.
- **Commit hygiene:** for any pendant-project commit that uses
GenAI-generated content, the commit message follows NLnet's example
format (Author: Harry Hacker with CodeLLM-3.4, prompt cited, output
attached).
## Verbatim policy text
Below is the full policy as captured 2026/04/27 from the email forward.
Reformatted from the email body for readability; semantic content
unchanged.
### Foundation of the policy
This policy is grounded in longstanding principles that apply to all
NLnet-funded work. From these fundamental principles we have deduced
what we consider common sense consequences with regards to the use of
GenAI.
**Fundamental principles:**
1. **FLOS licence.** All projects must be free/libre/open source: all
scientific outcomes must be published as open access, and any
software and hardware developed must be published under a recognised
free and open source licence in its entirety.
2. **No misrepresentation.** Grantees and applicants should not claim
work as their own, if it is not. This has always been true and
GenAI doesn't change that.
3. **Project quality.** Grantees are expected to deliver project
outcomes to the best of their ability. Tools may assist but do not
replace human responsibility for correctness, clarity, and
reproducibility.
### Use of GenAI in the application process
We encourage applicants to trust their own skills and write their own
proposals. That being said, applicants may use GenAI tools in preparing
applications, but any such use must be disclosed. This includes
drafting, translation, or summarisation. It applies both to written
proposals and to materials provided during interactive evaluation.
Disclosure allows evaluators to understand how the proposal was
produced and ensures fairness.
**How to disclose.** If GenAI is used in the application process a
prompt provenance log must be maintained. This log should list:
- the model used,
- dates and times of prompts,
- the prompts themselves,
- the unedited output.
Instructions about how to submit the prompt log for applications are
provided on the proposal form: https://nlnet.nl/propose/
### Use of GenAI in project development
- Grantees must ensure that all submitted work can be legally published
under a FLOS licence. This includes verifying that GenAI-assisted
outputs do not reproduce copyrighted or incompatible material.
- **Example:** when using a code assistant, check the assistant's
terms of use, and ensure that outputs are not reconstructed from
copyrighted sources.
- **Example:** Under EU law, purely AI-generated outputs without
substantial human intellectual contribution are not eligible for
copyright protection. In any case, outcomes purely generated by
AI are not allowed to be submitted as work eligible for payment
(as part) of the grant.
- Grantees must not present AI-generated content as if it were their
own human-authored work.
- **Explanation:** When we provide a grant to a person to develop a
project, we expect that person to do the work. They should not
outsource the work to another person while pretending they did it
themselves. Similarly, grantees should not deliver GenAI outcomes
and pretend it was their own human effort. Human contributors
remain accountable for accuracy, originality, and integration of
GenAI-supported work.
- Use of GenAI must not reduce the quality, clarity, reliability, or
reproducibility of the work.
- **Explanation:** Tools may assist, but human responsibility for
quality remains. Human contributors are expected to understand and
be able to explain design and code decisions.
- It is allowed to work on the topic of GenAI itself within the scope
of a grant, but only if this is explicitly part of approved work.
### Transparency and logging for project development
Use of GenAI should be disclosed and transparent. For any substantive
use of GenAI that materially affects outputs, public disclosure is
required, making it available to both users and contributors.
- The general stance toward the use of GenAI within a project should be
disclosed and transparent for the public by providing a broad
description.
- **Example:** A codebase declares, typically in its README, broadly
how GenAI is used (logic, boilerplate, tests, documentation, etc.).
- **Example:** A project publishes its own policy for contributors,
outlining its dos and don'ts with regards to the use of GenAI.
- Generated content should be marked as such. When adding (partially)
generated code, make sure the provenance is clear for each such
contribution. Specify which model was used (including version), and
how it was used. Provide the used prompts/interactions and resulting
output, or a summary thereof.
- **Example:** When using git, distinguish commits that add generated
code and include the used model and prompts in the commit message.
- Make sure to provide the information in a logical place where it
can easily be found. Avoid hosting it on third-party platforms
that require a log-in or may disappear over time.
- If GenAI is not used for generating code but only for tasks like
testing or creating documentation, it suffices to provide a general
description of the use in the README. More detailed logging on a
per-commit basis is preferred but not required.
### Alternative methods for logging
The goal of disclosure is to inform NLnet, users and contributors about
the extent to which GenAI was used to generate project results. If you
prefer to use different methods for logging with equivalent results,
this can be acceptable too. Use common sense to determine such
equivalence and make sure you are able to answer questions about the
use of GenAI from the NLnet team.
### Exceptions for grantees with active projects
For grantees with ongoing projects (Memorandum of Understanding signed
before 8 December 2025), logging is **not** required retroactively. It
applies to milestones started after the policy came into force.
Grantees of ongoing projects who feel that none of the disclosure
options offered above will work for them can propose a personalised
plan for transparency to their contact person at NLnet.
### Non-compliance
Failure to comply with the above policy may result in rejection of the
proposal or ultimately in the termination of the running grant.
### Scope
This policy explicitly deals with GenAI only (such as Large Language
Models). NLnet is a strong proponent of automation and of deterministic
and reproducible generation of source code, formal and symbolic proofs,
etc. based on specifications and scientific and engineering rigour.
Similarly, it does not in any way seek to prevent the use of other
forms of machine learning, fuzz testing or other beneficial use cases.
When in doubt, contact NLnet.
### Note 1: AI copyright in the EU
See: *Generative AI and Copyright*, page 93, a report requested by the
European Parliament's Committee on Legal Affairs.
> Given this framework, it follows that purely AI-generated outputs,
> those created automatically by an AI system without substantial
> human intervention, are not eligible for copyright protection in the
> EU. Such outputs are considered to fall into the public domain,
> making them freely available for anyone to use, reproduce, or adapt
> without seeking permission or providing attribution. The legal and
> commercial implications of this are significant. For creators and
> companies investing in AI systems that generate music, art, or text,
> there is no proprietary right over the final output unless a human
> has contributed in a way that meets the "intellectual creation"
> standard.
https://www.europarl.europa.eu/RegData/etudes/STUD/2025/774095/IUST_STU(2025)774095_EN.pdf#page=95
### Note 2: Example commit messages
```
Author: Harry Hacker <hh@example.org>
Date: Sun Jan 18 10:32:15 2026
Fix compliance tests
Fix several mistakes in generated code, make it compile; manually
verify each test with RFC123 specification.
```
```
Author: Harry Hacker with CodeLLM-3.4 <hh@example.org>
Date: Sun Jan 18 10:52:08 2026
Generate compliance tests
Prompt: Generate tests for compliance with RFC123 messages.
Output: (this commit)
```
## Source
Captured from email forward 2026/04/27 10:42 BST. Authoritative source:
https://nlnet.nl/foundation/policies/generativeAI/

290
docs/hardware/pendant-research-2026-04-27.md Normal file
View File

@@ -0,0 +1,290 @@
---
name: "Corbie Pendant — hardware, design and zero-upfront funding plan"
description: "Buildable plan for a Corbie-paired open-hardware audio capture device. Nordic nRF5340 silicon path, Sifam analogue VU aesthetic, NLnet + Crowd Supply funding sequence, 22-month timeline, 1.2k personal capital exposure."
type: research
tags: [hardware, pendant, corbie, funding, open-hardware, nlnet, crowd-supply, industrial-design]
captured_at: 2026/04/27
status: research
related:
- docs/hardware/nlnet-genai-policy.md
- docs/roadmap/2026-04-23-corbie-feature-complete-roadmap.md
---
# Corbie Pendant: hardware, design and zero-upfront funding plan
> Filed 2026/04/27. Compass-style research artefact superseding the off-the-cuff Tier-A/Tier-B sketch in the roadmap. Read this before scheduling any pendant work.
>
> **Naming.** The doc body still uses "Kon" / "Kon-Compatible" because that's how the research was framed before the rebrand. Treat every "Kon" reference here as "Corbie" once the rename sweep lands. The product name on launch will be Corbie or a Corbie-prefixed sub-brand.
A working planning document for shipping a "dumb but elegant" tape-recorder-aesthetic open-hardware audio capture device that pairs with the Corbie (formerly Kon) desktop. UK context, GBP, April 2026.
---
## 1. Executive summary
**The product is buildable, on a £2k discretionary budget, in roughly 6–9 months of part-time work, but only on one specific silicon path and one specific funding sequence.** Everything else either fails on cost, capability, or executive-dysfunction overhead.
Three findings dominate everything else in this document. **First, in 2026 LE Audio outside Apple and Samsung is effectively a Nordic monopoly** — every credible LE Audio product shipping today uses an nRF5340 or a module derived from it; Espressif have formally declined to add LC3/Auracast to ESP-IDF, and TI/Ambiq have no shipping stack. **Second, the lowest-friction credible grant in the world for this exact device is NLnet's NGI Zero Commons Fund** — €5k–€50k, two-month decision, a single short web form, and an open hardware audio precedent (Tiliqua) explicitly funded for builders with "low/no hardware development experience." **Third, the only crowdfunding platform whose operating model is compatible with a solo founder with executive dysfunction is Crowd Supply** — they handle video direction, copy, BoM review, fulfilment via Mouser, customs and VAT; Kickstarter does none of that and the post-campaign workload kills solo hardware founders.
The recommended sequence is therefore **NLnet first, soft pre-orders to the Kon waitlist second, Crowd Supply third** — with the explicit operating principle that the hardware must never cannibalise Kon software development time. A realistic minimum viable BOM lands around **£87 per unit at qty 100** for mechanical/power/PCB and **~£20 of silicon plus a microSD card**, hitting a sustainable £249–£299 retail price with healthy margin.
---
## 2. Recommended hardware specification
### 2.1 Silicon and audio chain
The core decision is the SoC, and in April 2026 there is functionally one answer. **Nordic nRF5340 — used as a pre-certified module — is the only hobbyist-accessible path to LE Audio with LC3 and Auracast.** Espressif's entire ESP32 family (S3, C6, C5) cannot run LE Audio; Espressif have closed the relevant feature request as "Won't Do." Ambiq Apollo4 Blue, TI CC2340 and the various STM32H7 variants have no production-grade LC3 stack. Nordic's newer nRF54H20 will be the right answer in 2027 but its LE Audio port from nRF5340 is not yet GA-mature. **For v1, ride the proven horse.**
Use a **pre-certified module** rather than a bare chip. The Raytac MDBT53-1M (nRF5340-based, ~£9–£10 qty 10 from Mouser UK) carries FCC/IC/CE/UKCA pre-certification, transferring module compliance to the finished device. The alternative — bare-chip RF design with an EMC chamber slot at a UK lab — costs £8–£15k and is the single biggest hidden expense in any "build your own BLE device" plan. A solo founder in Northampton with no RF lab access should not fight this battle on v1.
Drop the nRF7002 Wi-Fi 6 companion. **Wi-Fi belongs on USB-C only** — when the device is plugged in, expose its microSD as a USB Mass Storage Class device and let Kon read files directly. No Wi-Fi stack to maintain, no second radio cert, no PSTI complications, and the user experience ("plug in to sync") is more honest than a flaky Wi-Fi handoff. The nRF5340 has native USB 2.0 FS and Zephyr's MSC support is rock-solid.
The microphone is **a single Knowles SPH0645LM4H-1** PDM digital MEMS mic. SNR is 65 dB, sensitivity is fine, and it drops directly onto the nRF5340's PDM peripheral with zero external audio chips. At ~£1.20 qty 100 it is cheap, well-documented on every hobbyist platform, and the SNR delta to Infineon's IM73A135 (73 dB, the premium voice MEMS) is real but largely irrelevant for transcription — Whisper handles 65 dB SNR audio comfortably. Reserve the IM73A135 for a "Pro" tier later, where it would pair with a TI TLV320ADC3140 four-channel ADC at ~£3.50 qty 10. **One mic, no beamforming**: AirPods Pro 1 used a single mic plus bone conduction and that is the correct precedent.
There is **no dedicated DSP**. Opus encoding at 16 kHz mono needs roughly 8 MIPS on a Cortex-M33 with DSP extensions; the nRF5340 application core has ~192 DMIPS and already runs the more complex LC3 codec for LE Audio. xMOS XU316 is brilliant for USB audio sources but draws ~120 mA — an order of magnitude worse than software Opus encoding's ~5 mA penalty.
Storage is **a microSD card in a Hirose DM3AT-SF-PEJM5 push-push socket** (~£1.10 qty 100). This is the single most important design decision after the SoC choice. A 32 GB consumer card (~£5 retail) holds roughly 4,400 hours of 16 kbps Opus or 100 hours of 48 kHz/24-bit FLAC. The card socket can be visually disguised as a cassette spool inside the enclosure — the cassette aesthetic stops being decoration and becomes literal storage. Sync becomes trivial: USB MSC means Kon sees a thumb drive, drag-and-drop. No drivers, no app to install, no flaky Wi-Fi handoff to debug.
**Silicon BOM at qty 100, all-in:** ~£20 plus a £5 SD card. Dev-kit budget for prototyping: roughly £600 (two nRF5340 Audio DKs at £170 each, an nRF7002 DK at £60, a Power Profiler Kit II at £90, an IM73A135 eval at £60, miscellany at £50).
### 2.2 Power and battery
Power-budget arithmetic: ~60 mA active, ~1 mA standby, gives ~890 mAh for the 12 h active + 7-day standby spec, or ~1.4 Ah with margin. **A single 18650 cell in a Keystone 1042 surface-mount holder** is roughly 3.7× this — comfortable headroom for end-of-life and cold operation, and the right answer for the right-to-repair positioning.
**Cell: Molicel M35A 3500 mAh from Fogstar UK, ~£5.50–£6.99 qty 10.** Fogstar are Bromsgrove-based, WEEE-registered, and ship with UN38.3 / MSDS docs you will need for retailer listings. The cell is a vape-shop commodity worldwide — zero lock-in, infinite replacement supply, perfect right-to-repair story.
The Keystone 1042 (gold-plated, UL94 V-0) is ~£3.20 qty 100 from DigiKey UK. Add a 1S protection PCB (DW01-P + dual MOSFET, ~£0.10 in 100s from LCSC) for the safety case file even though the charger IC's built-in over-charge/discharge protection is also there.
Charging is **a Microchip MCP73831T** linear LiPo charger (~£0.40 qty 100), USB-C receptacle with the standard 5.1 kΩ × 2 CC pull-downs to advertise as a 5 V/3 A sink, and the IC's status pin driving the charge LED. **No USB-PD silicon** — PD is for >5 V or >3 A and a 3500 mAh cell wants neither. The whole charging sub-circuit is four passives and one IC, fits in 1 cm², and total port-and-charger BOM is ~£1.50 qty 100. Adafruit's product 1304 schematic is the open-source reference.
Reject LiPo pouches. They cannot be user-replaced, they swell after 2–3 years, and they kill the right-to-repair story.
### 2.3 Indicators, mute switch and trust
**The hardware-locked recording LED is the single design detail that earns the device's privacy claim.** The right topology is the LED in series with the mic preamp's V_DD rail — the analogue chain physically cannot draw current without forward-biasing the LED. Firmware can switch the rail off (LED off, mic off, honest), but cannot switch the LED off while keeping the mic on. Tampering requires deliberately shorting the LED with solder paste, which is a hardware modification, not a firmware compromise.
The voltage-drop arithmetic works either by running the analogue chain off a boosted 5 V rail with the LED in series before its 3.3 V LDO, or via a PNP/PMOS current mirror that derives ~3 mA LED current from the mic-chain current draw. The current-mirror version is the textbook approach (TI app note AN-1118 "Current Sense for LED Indication"). Omit any covert bypass diode; smooth with a 10 µF cap across the LED instead. **Total BOM cost for the trust property: about £0.10 per unit.** This is the same topology used by Axon Body 3 cameras and broadcast tally lights.
LED part: Kingbright L-7104ID 3 mm diffuse red, £0.06 qty 100 from Farnell. A chrome bezel (VCC CMC_220_RTW, ~£0.40–£0.80) sells the seriousness of the "REC" indication.
The **hardware mute switch must cut power to the mic, not signal an interrupt to the MCU**. If the switch were a soft signal, a compromised firmware could record while showing "muted." A DPDT toggle (NKK M2022SS1W03, MIL-style chrome bat, panel-mount, ~£4.80 qty 100) opens the mic-chain power rail on one pole and shorts the analogue output to ground through 1 kΩ on the other — kills any residual capacitively-coupled signal and removes click on re-engage. The MCU can read mute state via a third pole of a 3PDT for UI updates, but the security property does not depend on it. Pair this with the series-LED so muting also extinguishes the recording indicator automatically (because the rail powering it is broken). An NKK AT507A chrome safety guard (~£3–£4) over the toggle makes flipping it up to mute genuinely satisfying.
### 2.4 Display, controls, and other mechanical
The hero display element is **a Sifam Tinsley AL19 analogue VU meter** (~£35–£55 qty 10, less direct from Sifam Bracknell at qty 50+). Sifam are the spiritual heir to the British VU-meter trade and will print custom dial faces in batches of 50+. Pair with **a 0.91" 128×32 SSD1306 mono OLED (~£2 qty 100)** tucked behind a smoked window for clock, file counter, and battery percentage. Combined display BOM ≈ £8 qty 100. The CPC PM11118 V-22 panel meter at £8.99 inc VAT is the lowest-risk first prototype meter before committing to a Sifam custom dial.
Tactile controls cost more than novices expect, but they are non-negotiable for this product. The recommended set at qty 100 is APEM AV1953F6A04Q04 illuminated 19 mm anti-vandal momentary buttons (red-ringed for Record, green-ringed for Play, ~£8 each) with two black AV091003C940 buttons for Stop and Pause (~£5.20 each), plus a Bourns PEC11R rotary encoder with knurled aluminium knob for record-level (~£4) and the NKK DPDT mute toggle. **Total tactile-controls budget: ~£35 qty 100, ~£45 qty 10.** A "100% retro vibe" alternative using AliExpress vintage transport latch buttons drops the cost to ~£14 qty 100 but introduces supply risk. A novel third path uses Cherry MX-style mechanical keyboard switches as transport keys with custom 3D-printed transport-symbol caps — clever, hacker-y, cheap (£3–£8 per button qty 100), but reads as "keyboard" rather than "tape."
PCB: **JLCPCB Economic 4-layer with SMT assembly.** A roughly 60×100 mm board with 50–100 mid-density components lands at £160–£220 for ten fully-populated prototype boards, dropping to £6–£9 per unit fully populated at qty 100, all-in including DDP shipping with UK VAT prepaid. JLC's Jan 2021+ DDP option means no FedEx brokerage surprises. Hand-soldering 50–100 components is *technically* feasible but the £80–£140 component-line cost dominates, so spend the time on firmware instead. For a v2/v3 production run of 100+, **JJS Manufacturing in Lutterworth (35 minutes from Northampton)**, Tioga in Bedford, or Newbury Electronics are credible UK EMS partners — pricier than JLC but unlock the "Made in UK" story when it becomes a marketing point.
Enclosure: **3DPrintUK PA12 SLS body, dyed black, with a JLCCNC anodised aluminium top plate for the faceplate.** This is the Teenage Engineering recipe at small-batch scale — UK printing for the body keeps lead times short and quality consistent; Chinese CNC for the small alu plate works because the part ships fast DDP and the cost saving is significant. Per-unit total: **~£40–£55 at qty 10, ~£22–£32 at qty 100**, including fasteners, heat-set brass inserts (Ruthex M3) and feet. Graduate to injection-moulded ABS only at qty 1000+ when £6–£15k of Chinese soft-tool tooling amortises.
### 2.5 Total mechanical/power/manufacturing BOM
The full per-unit cost picture, excluding the silicon line covered earlier:
| Subsystem | Qty 10 | Qty 100 |
|---|---|---|
| Display (Sifam VU + small OLED) | £14 | £8 |
| Tactile controls (5-button + encoder + DPDT) | £45 | £35 |
| Battery (Molicel + Keystone 1042 + PCM) | £12 | £9 |
| Charger (MCP73831 + USB-C + passives) | £2 | £1.50 |
| Hardware-lock LED + bezel + passives | £1 | £0.20 |
| PCB + SMT assembly | £18 | £8 |
| Enclosure (SLS body + CNC alu plate) | £45 | £25 |
| **Mechanical/power/manufacturing total** | **~£137** | **~£87** |
| Plus silicon (nRF5340 module + mic + storage socket + SD card) | ~£25 | ~£20 + £5 SD |
**All-in BOM at qty 100: roughly £107–£112 per unit before packaging.** This supports a £249 retail with ~55% gross margin or a £299 "Founders Edition" with ~63% margin — comfortably in the range that boutique audio hardware lives at.
---
## 3. Industrial design moodboard
### 3.1 The lineage in one sentence
**The Kon recorder is a Sony WM-D6C in spirit, a Nagra E in proportion, a Playdate in commitment to one colour, and a Teenage Engineering TP-7 in operating logic.** Every other reference in this section either supports those four anchors or is a counter-reference for what to avoid.
### 3.2 Vintage anchors
The **Sony WM-D6C "Walkman Professional"** (1984–2003) is the primary visual ancestor. Glass-bead-blasted aluminium top and bottom plates, ribbed black plastic side panels for grip, a glass cassette window, five-key piano transport, a single rotary record-level with a detent at zero, a tiny LED bargraph, and one small red LED for record. It was used by professionals for nineteen years unchanged. Image search: `Sony WM-D6C top view`, `WM-D6C amorphous head badge`.
The **Nagra E** (Switzerland, 1976) provides the proportion and the leather strap. Matte natural-finish aluminium chassis in the famous "Nagra warm grey," stainless-steel transport levers, knurled aluminium knobs, real leather strap, hand-engraved/silk-screened legends in an unusual semi-serif logotype that still reads as the brand from a hundred yards. The Nagra SN ("Série Noire") miniature commissioned by Kennedy for the Secret Service and used on Apollo missions is the reference for "small but uncompromising." Image search: `Nagra E reporter`, `Nagra IV-S modulometer`, `Nagra SN spy recorder`.
The **Uher Report 4000** (Munich, 1961–1999) provides the brown-leather-case-with-shoulder-strap supplementary aesthetic — cast siluminum case, ivory dial faces, a single red record indicator, piano-key transport, the "Akustomat" voice-activated switch (a precedent for hands-free record). The BBC reporter's standard for forty years. **Sound Devices' modern MixPre series** validates that "professional recorder" still means matte aluminium, restrained palette, deep orange (PMS 165 C) accent reserved for level/warning — direct precedent for using one accent colour as semantic signal, the same logic Jesper Kouthoofd applies at TE.
### 3.3 Modern boutique anchors
**Teenage Engineering's TP-7 field recorder** is the closest living competitor and the closest reference. Cast-aluminium body, motorised tape-reel-style jog wheel as primary control (a deliberate Nagra nod), white/silver base, single orange RECORD button. Kouthoofd's stated rules to steal directly: he specifies colours in **RAL not Pantone** because RAL has fewer choices and forces decisions, and his absolute rule — **"if it's orange or red, it means recording."** Use this rule wholesale on Kon-Compatible.
The **EP-133 K.O. II** is the closest sibling for the Kon brief — PA66 polyamide housing, immersion-gold 4-layer PCB, laser-engraved keys (TE's published material spec MT 83352), 12 silicon pads, calculator/Game-&-Watch reference, palette of cool light grey body plus dark grey trim plus RECORD red. The **EP-1320 Medieval** is the same industrial design with a different colour and silk-screen, proving the platform-with-skin approach works (relevant: Kon could ship multiple finishes off the same shell).
**Panic's Playdate** (hardware designed by Teenage Engineering, software by Panic — make this explicit in any internal discussion, the crank "is specifically credited to Teenage Engineering") teaches the single most useful production lesson: **commit to one colour absolutely, including the shipped USB-C cable.** Playdate yellow lives on the body, the box, and the cable. A Kon device that ships with a coloured USB-C cable lands the same trick.
**Mutable Instruments' panel pipeline** (Émilie Gillet, Paris, 2010–2022, all designs open-source) is the cheapest path to high-quality finishing in small UK runs: a 2 mm aluminium panel, screen-printed legends, Rogan PT-1 knobs, Schurter switches. Fully realised premium Eurorack-quality aesthetic at under $50 BOM. Do not over-engineer beyond this if you copy the pipeline.
The strong counter-references — what the device must not look like — are Zoom H-series and Edirol R-09 (generic black plastic, anonymous, "techy"), Make Noise's busy hand-drawn graphics (too noisy for a productivity tool), any rugged rubberised PMR/walkie-talkie aesthetic (wrong tribe), and Nothing Phone's transparent + LED Glyph aesthetic (reads as smartphone-future, not field-tool; TE has since stepped back from Nothing's design lead, which is itself telling).
### 3.4 Specific colour, type and material specification
**Body:** RAL 7035 Light Grey or RAL 9002 off-white, matte. Never gloss. Never soft-touch rubberised coating — it ages badly and feels cheap within 18 months.
**Faceplate:** brushed-or-bead-blasted natural anodised aluminium. Closest paint match if anodise is unavailable: RAL 9006 White Aluminium or RAL 9007 Grey Aluminium.
**One accent colour:** PMS Orange 021 C / RAL 2009 Traffic Orange. Used only on the record button, the recording-state indicator, and the end-of-tape warning. Nowhere else.
**Typography:** FF DIN (Albert-Jan Pool, FontFont) for body legends, DIN Next (Akira Kobayashi, Linotype) for OLED UI, Berkeley Mono for the model-number/serial badge. One face per role, no mixing. Avoid script faces, rounded "friendly" sans-serifs, and emoji icons. Iconography: ISO 7000 / IEC 60417 standard transport glyphs, not the rounded Apple/Google ones.
**Materials hierarchy:** anodised aluminium faceplate; brushed stainless steel for transport buttons; matte ABS (Cycolac or equivalent, never glossy) for the main shell; machined PMMA for the cassette-style window over the storage card slot; chrome-tanned leather wrist strap (Ettinger or Tusting in Northampton can do small runs).
### 3.5 Why this resonates with neurodivergent users
The cassette form factor is not nostalgic decoration — it is therapeutic logic. **Tactility and proprioception**: physically inserting and removing a finite object book-ends a recording session as an embodied act, supporting sensory-seeking ADHD/autistic profiles. **Finite tape length forces discipline**: the same external-boundary logic as Pomodoro timers, outsourcing executive function. **One-thing-at-a-time**: the device records voice and does nothing else; you cannot get a notification while recording, and the monomanic single-purpose nature is itself the feature. **Tangible ownership of recordings**: a discrete, holdable thing solves the object-permanence problem digital-only voice memos cause for many ND users. **Forgiveness of imperfection**: tape hiss and slight wow-and-flutter lower the bar for recording — nothing is fixable, so nothing has to be perfect, killing the perfectionist freeze response. **Slowness as feature**: the seconds of waiting are the cognitive space in which insight forms.
Marc Masters' *High Bias: The Distorted History of the Cassette Tape* (UNC Press, 2023) and Rob Drew's *Unspooled* (Duke University Press, 2024) are the best recent academic-adjacent treatments to cite when pitching to ND-adjacent funders.
### 3.6 The Ten Rules of Kon hardware
A single design language brief, ranked, to be broken only with explicit reason:
1. Brushed or bead-blasted natural aluminium faceplate. No painted faceplate. No gloss.
2. One accent colour, used semantically only — PMS Orange 021 C, on the record button, the recording-state indicator, and the end-of-tape warning. Nowhere else.
3. Body in matte light grey or matte off-white. RAL 7035 or RAL 9002. Never gloss, never soft-touch rubber.
4. DIN typography only. FF DIN for legends, DIN Next for OLED, Berkeley Mono for serial.
5. One real analogue VU meter, illuminated dim warm white. Sifam AL19 with a custom dial face.
6. Visible-but-honest controls. The control hierarchy must be readable from across the room.
7. Cassette-form-factor reference, not pastiche. A clear PMMA window over the SD card. No fake mechanical reel — that's costume, not design.
8. One leather strap, one knurled metal knob, one window — never two of any of these.
9. Off-state must be beautiful. The device must look like an object, not an interface, when not in use.
10. One brand, one mark, one place. Small silk-screened logo on the bottom edge of the faceplate, in DIN Mittelschrift, no larger than the smallest legend.
### 3.7 UK suppliers for the design language at small-batch scale
**Anodising:** Badger Anodising (Birmingham, 60+ years, full colour range including orange) or RMC Anodising. Realistic price ~£3–£8 per faceplate at qty 100. **Silk-screen / pad print on enclosures:** OKW Enclosures (UK office) or GSM Valtech, ~£60–£120 setup per screen per colour, ~£0.60–£2 per piece. **Laser engraving on anodised aluminium:** Razorlab (London/Manchester) or HPC Laser (Yorkshire), no setup cost beyond artwork — perfect for low quantities, this is what TE uses on EP-133 keys. **VU meters:** Sifam Tinsley (Bracknell) for custom dials at qty 50+. **Leather:** Tusting (Northampton, on Jake's doorstep) or Ettinger (London) for straps at qty 50+. **Cassette-style PMMA window:** Hindleys or The Plastic People.
---
## 4. Minimum viable specification
### 4.1 What is essential and what is cuttable
The MVP must do four things and only four. It must capture clearly intelligible voice audio (not audiophile, just transcription-quality). It must have a hardware record indicator and hardware mute switch (these are the trust property — without them the device has no story for ND users wary of always-on microphones). It must pair to Kon and sync audio reliably. And it must look unmistakably "Kon" from across the room — the design must be recognisable.
Working from this, the cuts and keeps fall out clearly. **Cut Wi-Fi**: the nRF5340 alone, no nRF7002, USB-C only for sync. Saves £4 silicon, removes a Wi-Fi cert headache, simplifies the firmware enormously, and the user experience (plug in to sync) is more honest. **Cut multiple mics**: a single Knowles SPH0645 is enough. Beamforming code on the desktop side is a software feature, not a fundamental hardware capability gap. **Cut the dedicated DSP**: Opus encoding runs on the application core in software. **Cut the IMU, NFC and haptic motor**: none earn their place on v1. **Cut the colour OLED**: a 0.91" mono SSD1306 hidden behind a smoked window does the file-counter and battery-percent job, and the analogue VU meter does the recording-state job analogue-ly.
**Keep the analogue VU meter** even though it is the single most expensive non-silicon part. It is the design's recognisability from across the room, the mechanism by which the device feels "alive" when idle, and the proof that the off-state is beautiful. Cutting it cuts the project's identity.
**Keep the hardware-locked recording LED and DPDT mute switch** at all costs. These are the trust story.
**Keep the microSD card slot** — disguised as a cassette-style spool window. This is the cassette aesthetic made literal, and it makes USB sync trivial via Mass Storage Class.
### 4.2 The bare-minimum BOM
At qty 10, all-in including silicon, mechanical, power and SD card: **roughly £165 per unit**. At qty 50: **roughly £115 per unit**. At qty 100: **roughly £107 per unit**.
This supports a **Founders Edition kit price of £249** (44% gross margin at qty 100) or **£299** (52% gross margin) — the latter being the right number for the maker community given the boutique design pitch and the comparable price points of Teenage Engineering TP-7 (£1,499), We Are Rewind (£140), and FiiO CP13 (£90). Kon-Compatible at £299 sits at the "boutique but accessible" sweet spot — clearly above mass-market plastic, clearly below TE pricing, justified by the open-hardware story and the ND-targeted positioning.
A "kit" SKU at £179 (PCB + silicon BOM only, user supplies enclosure and battery) is a credible secondary product for hardcore makers, with an even higher gross margin and zero enclosure cost — useful as a Crowd Supply add-on tier.
---
## 5. Funding pathway analysis
The funding question is dominated by one constraint: **application overhead, not grant size, is the binding variable for a solo founder with executive dysfunction**. A £20k grant with a four-hour application beats a £200k grant with a 200-hour application every time, because the latter does not get filed.
### 5.1 Comparison of all options
| Pathway | Realistic timeline | Capital from founder | Equity / IP cost | Realism for solo ND founder | Notes |
|---|---|---|---|---|---|
| **NLnet NGI Zero Commons Fund** | 2 months to decision, 4–8 hours to apply | £0 (free) | 0% equity; mandatory open licence on outputs (CERN-OHL-S, GPL, CC BY-SA all fine); commercial use permitted | **9/10** ✅ | €5k–€50k (~£4k–£42k), short web form, rolling deadlines every 2 months. Audio-hardware precedents (Tiliqua, MILAN). Next deadline 1 June 2026. |
| **Crowd Supply** | 6–8 months application-to-cash | ~£500–£2k (prototype-for-video, shipping a sample to Portland, DIY video) | 0% equity, retains IP, open hardware preferred | **8/10** ✅ | 12% campaign fee + 2.9% + ~$1–18/item fulfilment + ~50% wholesale on long-tail. >90% campaign success, 100% historical delivery rate. They handle video direction, copy, BoM review, fulfilment via Mouser, customs, VAT, returns. |
| **Direct pre-orders via Kon waitlist (Stripe)** | 2–4 months | £50 Ltd company + ~£500–£800 landing page, Stripe, T&Cs | 0% | **7/10** ⚠️ | Fastest cash, but founder carries all UK consumer-law liability (Consumer Rights Act 2015 + Consumer Contracts Regs 2013). Section 75 chargeback exposure. Must form Ltd company before taking a single pre-order. Cap at 100–250 units to stay under the £90k VAT threshold. |
| **Microsoft Innovation & AI for Accessibility** | ~90 days | £0 | 0% equity, you retain all IP | 6/10 | £8k–£16k Azure credits + cash for engineering — but software/AI side only, not hardware. Useful as background runway. |
| **GitHub Sponsors / Open Source Collective** | Days to set up | £0 | 0%; OSS only | 8/10 | £0–£5k/month recurring once Kon software has audience. Builds the audience that later buys the hardware. |
| **GroupGets** | 4–6 months | £200–£1.5k | 0% | 6/10 | Engineer-to-engineer, low ceremony. AudioMoth proves the model exactly. Smaller ceiling than Crowd Supply but lower stakes. Useful as parallel/backup. |
| **Access to Work for the founder personally** | 2–8 weeks | £0 | n/a | **9/10** ✅ | Up to £69,260/year for self-employed founders. Cannot fund product dev, but can fund ADHD coaching, virtual assistant for grant admin, body-doubling apps — directly easing the executive-dysfunction barrier to all the other funding work. |
| **Access to Work as a distribution channel** | Post-launch | n/a | n/a | 9/10 (post-launch) | Likely the single largest post-launch revenue channel. Seed via Microlink, Iansyst, AbilityNet assessor community. |
| **Kickstarter** | 3–5 months | £500–£3k | 0% | 4/10 ❌ | 8–10% all-in fees, ~30–35% hardware success rate. Post-campaign fulfilment is brutal solo with no hardware experience. Tax/customs/refunds/support all on you. Exec dysfunction will choke on this. |
| **Indiegogo (primary)** | 3–5 months | £500–£3k | 0% | 3/10 ❌ | Weaker brand signal, no fulfilment help. Useful only as InDemand post-Kickstarter relay. |
| **BackerKit Crowdfunding** | 3–5 months | £100 + video | 0% | 2/10 ❌ | Wrong audience (tabletop/RPG dominant). Use the $99 Launch teaser tool only. |
| **Innovate UK Smart Grant** | n/a — programme paused since Jan 2025 | High match-funding | 0% | **2/10** ❌ | Currently paused; replacement not formally launched as of April 2026. When it returns: 6–8 weeks of focused application work; 3–5% solo success rate. Not realistic without a paid grant writer (£5k–£20k). |
| **EIC Accelerator (UK grant-only)** | 4–9 months | £20k+ for grant writers | 0%; UK excluded from equity component | **1/10** ❌ | Up to £2.1m grant but ~5% success rate, very heavy admin. Reconsider in late 2027 with prototype + traction. |
| **Sovereign Tech Fund** | n/a | n/a | n/a | **1/10** ❌ | Explicitly does not fund user-facing applications or prototypes. Skip. |
| **HAX / Bolt / YC / EF / Antler / Plexal** | n/a | n/a | 7–12% equity + relocation | **0/10** ❌ | All require full-time, often residential, commitment. Incompatible with running Kon as primary product. |
| **Hardware Pioneers (London)** | n/a | n/a | n/a | n/a | Not a fund; events business. Use for networking only — June 2026 conference at ExCeL, ~£80 train Northampton↔London. |
| **NIHR i4i** | 6+ months | High | 0% | 3/10 | Worth a follow-up look if positioned as health-tech/mental-health adjunct. Flagged as missing pathway worth investigating. |
| **Autistica** | 3–6 months | Medium | Research outputs open | 4/10 | £10k–£100k research grants, academic preferred. Useful as future partner-of-record. |
| **B2B partnership with Microlink/Iansyst/AbilityNet** | Months | £0 | Reseller margin 25–40% | 7/10 (post-prototype) | Won't pre-fund development, but commitment-letter pathway strengthens any grant application. Approach once a working prototype exists. |
### 5.2 The two pathways that matter
**NLnet NGI Zero Commons Fund and Crowd Supply** are the two pathways that fit this founder. NLnet is the only credible grant in the world with an application format compatible with executive dysfunction — a short web form, two-month decision, mandatory openness as the only string. Crowd Supply is the only crowdfunding platform whose operating model handles the parts a solo founder cannot do alone (video direction, copy, BoM review, fulfilment, customs, VAT, returns) and whose >90% funding rate / 100% historical delivery rate means the founder is not gambling against the 60% Kickstarter failure base rate.
Direct pre-orders to the Kon waitlist sit alongside as a fast-cash supplement, contingent on forming a Ltd company first to cap personal liability. Everything else is either too slow, too narrow, too equity-hungry, or too admin-heavy for this founder's specific constraints.
---
## 6. Recommended sequence with timeline
The sequence below assumes Kon software remains the primary product — every step is sized so the hardware project never consumes more than ~10 hours per week, which is the maximum sustainable load given Kon's beta runway and the founder's executive-dysfunction profile.
**Week 1 — administrative foundation.** Form a Ltd company via Companies House (~£50, 24 hours online); the Ltd is required before taking pre-orders and is good practice for grant applications. Phone Access to Work (0800 121 7479) to start a personal application — likely outcome is funding for an ADHD coach, a part-time virtual assistant for grant admin, and ergonomic kit, all of which directly reduce the executive-dysfunction tax on the rest of this plan. Set up GitHub Sponsors for the Kon software repo (zero fee, ~1 hour) so passive supporter revenue starts ramping while the rest of this plan executes.
**Weeks 2–4 — NLnet application.** Read the Tiliqua project page and the latest Commons Fund announcement to calibrate language. Draft a one-paragraph problem statement that links neurodivergent productivity, local-first audio, and open hardware. Pick licences now: CERN-OHL-S-2.0 for hardware, GPL-3.0-or-later for firmware, CC BY-SA 4.0 for documentation. Submit by 15 May 2026 to leave buffer before the 1 June deadline. **Decision by ~1 August 2026.**
**Weeks 4–12 — prototype on existing dev kits.** Spend ~£600 of the discretionary £2k on dev hardware: two nRF5340 Audio DKs, an nRF7002 DK, a Power Profiler Kit II, an Infineon IM73A135 eval flex board, and miscellaneous breakouts. Build a working hand-soldered prototype using the dev boards plus a Knowles SPH0645 mic on a breakout, a microSD breakout, and an off-the-shelf 18650 holder. The point is not a beautiful prototype yet — the point is end-to-end audio capture from the mic, through Opus encoding on the nRF5340 application core, to a microSD file, with USB MSC sync to a Mac running Kon. **Demo target: by 31 July 2026.** Document publicly on GitHub from day one — this becomes the open-source artifact that NLnet's mandate requires and that the Crowd Supply application later evidences.
**Weeks 8–14 — pre-order soft launch to Kon waitlist.** Once the prototype demos end-to-end, build a "Founders Edition" landing page (Carrd or Webflow, ~£80–£300) with Stripe `payment_intent` and explicit T&Cs covering the Consumer Rights Act 2015, the Consumer Contracts Regs 2013, the 14-day cooling-off, the estimated delivery window (promise nine months even if the real estimate is six), and the Section 75 chargeback context. Single-shot solicitor review ~£200 (worth it). **Soft-launch to Kon's existing waitlist only — do not promote publicly. Cap at 100 units at £299 = £29,900 maximum, comfortably under the £90k VAT threshold.** Ringfence the cash in a separate business savings account; do not spend deferred revenue on operating costs.
**Weeks 12–24 — first real PCB, NLnet money lands.** With the NLnet decision in hand by August (success or not, the momentum is real) and pre-order cash secured, do the first real PCB design in KiCad. Use a Raytac MDBT53-1M pre-certified module to dodge the EMC chamber bill. Order ten boards via JLCPCB Economic SMT assembly with DDP shipping (~£200 all-in). Order the SLS body from 3DPrintUK and the CNC anodised faceplate from JLCCNC. **Target ten finished prototypes by end of January 2027.** This is also the right window to seed the prototype with Microlink/Iansyst/AbilityNet assessors for letters of support — even informal "yes, this is interesting, send us a unit when you have one" emails are useful evidence for the next step.
**Weeks 24–36 — Crowd Supply application and pre-launch prep.** Apply to Crowd Supply (https://www.crowdsupply.com/apply) once the ten prototypes are in hand, the GitHub repo is mature, and 50–100 pre-orders are validated. Application review: ~2 weeks. Statement of Work negotiation: ~3 weeks. Pre-launch prep with their team (video, copy, image assets, BoM review, pricing): 8–16 weeks. Live campaign: 30–45 days. **Target campaign launch: Q3 2027.**
**Weeks 36–60 — production and fulfilment.** Crowd Supply campaign closes, funds disbursed within two weeks. Production run via JJS Manufacturing in Lutterworth (the geography earns the "Made in UK" story; the proximity to Northampton makes site visits feasible). Bulk DDP consignment to Mouser Texas, Mouser fulfils to backers globally, residual inventory becomes a permanent Mouser SKU for long-tail revenue. **First units shipping ~Q1 2028.**
**Total elapsed time: ~22 months from today to first units shipped.** This is slower than the Path B and Path C scenarios in the original brief — but it is realistic for a side project to a primary software product, with a founder profile that genuinely cannot sustain six-month grant-writing marathons, and crucially it does not cannibalise Kon software development. The first 12 months of this sequence run on roughly 8 hours of hardware work per week; the second 12 months ramp to 15–20 hours per week as Crowd Supply pre-launch begins.
The total external capital required from the founder personally over this period is **roughly £1,200**: £600 dev hardware, £200 Ltd-company-and-T&Cs setup, £200 PCB iterations beyond what NLnet covers, £200 contingency. This sits comfortably within the £2k discretionary budget with ~£800 of headroom for unexpected costs.
---
## 7. Risks and what could derail this
The single largest risk is **Kon software stalling because the hardware is more fun**. Hardware is novel, tactile, photogenic — it produces dopamine in a way that another bug-fixing session in Tauri/Svelte does not. The hardware project must remain explicitly secondary. The operating discipline: no hardware work in any week where Kon software has not shipped a meaningful change. If Kon does not reach £2k MRR, the hardware does not ship. Full stop.
The second risk is **LE Audio source-side maturity**. Even on Nordic, sending LC3 *up* to a phone (acting as a microphone source, which is what Kon-Compatible needs) is less battle-tested than sending audio *down* to earbuds. Phone-side LE Audio support in Android 13+ and iOS 17+ exists but is reportedly flaky on many shipping handsets in 2026. Mitigation: support at least one fallback transport (BLE GATT custom + Wi-Fi/USB) for the first year; treat LE Audio as the headline capability but not the only path.
The third risk is **post-Brexit regulatory compliance on a powered radio device**. Even with a pre-certified Raytac module dodging the EMC chamber bill, the device still needs UKCA marking, PSTI compliance (UK Product Security and Telecommunications Infrastructure Act, in force for connectable consumer products — minimum password requirements, vulnerability disclosure policy, defined support period statement), and the EU Cyber Resilience Act mandatory from late 2027 (Nordic launched a flat-rate FOTA package in February 2026 specifically aimed at small customers needing CRA compliance — budget ~£400/year for this). Budget £1.5k–£5k for pre-compliance EMC at a UK lab (TÜV SÜD Fareham, Element Materials Hitchin, or ETL Wokingham) before launch.
The fourth risk is **pre-order non-delivery exposure**. Even via a Ltd company, Section 75 chargebacks expose the founder personally if reckless statements were made about delivery dates. Mitigation: the Ltd company structure, conservative delivery promises (nine months on the page, six in the head), the ringfenced cash account, and a hard cap on pre-order units in year one.
The fifth risk is **grant rejection cascading into discouragement**. NLnet has roughly a 15–25% success rate for well-aligned proposals; rejection is the modal outcome. Mitigation: treat NLnet as one input to the sequence, not a gate. The pre-order soft launch and Crowd Supply application both proceed regardless of NLnet's decision — the grant accelerates the timeline by ~3 months and de-risks the prototype budget, but it is not the critical path.
The sixth risk is **enclosure cost overrun**. The £45–£55 per-unit prototype enclosure cost assumes a clean first-pass design. First passes are never clean. Realistic budget: two enclosure design iterations at ~£500 each, paid out of the contingency.
---
## 8. Open questions to validate further
The investigation surfaced eight questions that warrant further work before they become blocking issues:
**Phone-side LE Audio compatibility in 2026.** Specific testing required across iPhone 17/18, Pixel 9/10, Samsung S25/S26, OnePlus, and Nothing handsets to confirm LC3 source-mode reception works reliably end-to-end. The Nordic Audio DK can act as the source for these tests cheaply — budget a long weekend.
**NIHR Invention for Innovation (i4i) programme.** Flagged as a missing pathway in the funding research. The i4i fund supports medical/health-tech device development at £50k–£1m and has historically supported assistive devices. Worth a 30-minute investigation into current call status and whether Kon-Compatible can credibly be framed as mental-health-adjacent assistive tech.
**Sifam Tinsley custom dial face minimum order quantity and lead time.** Quoted as 50+ units at 6–8 weeks based on community report; needs a direct quote with a CAD file to confirm exact pricing. If the MOQ is genuinely 50, the v1 prototype run of 10 must use the off-the-shelf AL19 face, which is a meaningful design compromise.
**Microlink, Iansyst and AbilityNet assessor onboarding criteria.** Each provider has informal vendor-onboarding processes that are not publicly documented. A short call with each (info@iansyst.co.uk, sam@microlinkpc.com, enquiries@abilitynet.org.uk) before the prototype is finished would shape the hardware spec and generate letters of support for the NLnet application.
**Crowd Supply pricing and fulfilment calculator for the specific BOM.** Their published pricing guide (https://www.crowdsupply.com/guide/pricing-products) gives the framework, but exact per-item fulfilment costs depend on weight, packaged dimensions and whether free international shipping is offered. Pre-application conversation with Crowd Supply (they accept introductory emails) would calibrate the realistic campaign goal.
**UK Ltd company versus sole-trader trade-offs given exec dysfunction.** A Ltd company adds annual filing burden (Confirmation Statement, accounts, Corporation Tax return) which may itself be an executive-function tax. Some founders find this manageable with a £30/month accountancy package (Crunch, FreeAgent + accountant); others find it derailing. Worth a candid conversation with an ADHD-aware UK accountant before forming the company.
**Tusting (Northampton) leather strap pricing at qty 50.** Direct geographic proximity to the founder makes this an attractive partnership, with a "made in Northampton, by hand, for a Northampton-built device" story that could earn local press. Needs a direct quote.
**JJS Manufacturing (Lutterworth) versus continuing with JLCPCB at qty 100.** The 35-minute drive from Northampton makes JJS the logical UK EMS partner, but their per-unit cost at qty 100 is likely 1.5–2× JLCPCB. The "Made in UK" story versus the cost saving is a genuine trade-off — quote both, decide based on what the Crowd Supply audience actually values, and be honest in the campaign about where assembly happens.
---
The shape of the answer to "is this buildable?" is yes, on this exact path: Nordic silicon, Sifam analogue VU, Tusting leather strap, JLCPCB prototyping graduating to JJS Manufacturing for production, NLnet money first, Kon-waitlist pre-orders second, Crowd Supply third, and a hard discipline that the hardware never ships before Kon software hits £2k MRR. The two-year horizon is honest. The £1,200 personal-capital exposure is honest. The 22-month elapsed timeline is honest. None of it is fast, but all of it is real.

50
docs/roadmap/2026-04-23-corbie-feature-complete-roadmap.md
View File

@@ -341,6 +341,56 @@ Ideas worth keeping warm once the v0.1 release is out. Not tracked as phases unt
- **Calendar integration.** Read-only first pass could parse a local ICS file (Thunderbird / Evolution export) and surface day events alongside the tasks list — stays local-first. A cloud-sync pass (Google / iCloud / CalDAV) is a v0.2+ conversation because it re-opens credential handling and refresh-token plumbing that v0.1 deliberately avoids.
- **Right-click highlighted text → capture as task.** Two flavours: (a) *In-Corbie* — context menu on a selected transcript range or viewer segment, routes to `create_task_cmd` with the selection as text. Small — lives naturally in Phase 9 polish or a bolt-on. (b) *System-wide* — highlight anywhere (browser, Slack, IDE) and call Corbie. Platform-painful: macOS Services API, Windows shell-extension, Linux desktop-env-specific context menus. Scope as a separate post-v0.1 phase.
### Pocket-inspired features (2026/04/27 competitive review)
Captured after a feature scrape of heypocket.com. Pocket is the closest direct competitor in the AI transcription space. Some of its features map cleanly onto Corbie's local-first principles, others conflict and are flagged below. None scheduled into v0.1; these sit alongside the calendar and right-click ideas above as post-v0.1 candidates.
- **Multiple summary styles.** A named library of cleanup templates. Realistic target is 6 to 10 well-chosen presets: action items, narrative, decisions made, meeting minutes, SOAP (clinical), brain-dump tidy-up, daily standup. Slots into the existing `kon-llm` cleanup pipeline; each style is a system prompt plus light GBNF grammar where structure matters. Per-profile default style. Effort: 1 to 2 days. Already half-built (the cleanup prompt does this for one style today).
- **Mind maps from transcripts.** Visual topic clusters generated from a transcript. Local LLM extracts nodes and edges (GBNF-constrained), Svelte renders with Cytoscape or vis-network. Screenshot-shareable, strong marketing surface, runs entirely on-device. Differentiating, not common in this space. Marketing asset for the Innovate UK pitch (visible artefact of "on-device intelligence"). Effort: 3 to 5 days for a usable v1, mostly in the rendering and interaction layer.
- **Bulk export format expansion.** Phase 9 shipped single-transcript markdown export and bulk select. Pocket ships JSON, plain text, SRT subtitles, and audio bundle. Adding format options to the existing dialog is mechanical. Effort: half day.
- **Local webhooks.** HTTP POST to a user-configured local URL on `transcript-finalised`, `task-created`, `task-completed` events. Stays local-first (no cloud relay). Powers Obsidian plugins, Hermit integration, home automation, n8n flows. Doesn't break any design principle; composability is principle 3. Effort: 1 day. Small Tauri command, settings UI, retry-with-backoff.
- **Language picker UX.** Whisper already supports 120+ languages; Corbie's UI defaults to English with no per-profile picker. Pure UX gap. Per-profile language default plus a language picker on the dictation page. No model work needed. Effort: half day.
- **"Ask the transcript" Q&A — scope expansion, requires explicit decision.** Pocket's "Ask Pocket" is RAG over the user's recording history. Corbie's design principle 4 says "LLM scope is narrow ... not a chat UI". Adding this is a deliberate doctrine change, not a feature add. If it ships, scope tight: single-transcript Q&A only (not cross-history initially), local Qwen3, no chat history retained, output renders as a one-shot answer not a conversation thread. Effort: 2 to 3 days if scoped tight, open-ended otherwise. Decision required from Jake before scheduling.
### Hardware companion (Corbie Pendant) — separate track
Long-horizon hardware play surfaced by the Pocket review. Not a phase of the desktop roadmap; tracked as its own programme.
**Authoritative spec:** `docs/hardware/pendant-research-2026-04-27.md`. Read that before any hardware planning conversation. The earlier Tier-A / Tier-B / Hailo / Wi-Fi-6 / three-mic sketch in this section's previous draft was off-the-cuff and is superseded.
**Headline decisions (from the research):**
- **Silicon:** Nordic nRF5340 only. Espressif have closed LE Audio support as Won't Do; TI/Ambiq have no shipping LC3 stack. Use the Raytac MDBT53-1M pre-certified module to inherit FCC / IC / CE / UKCA, dodging an £8k to £15k EMC chamber bill.
- **Connectivity:** drop Wi-Fi entirely. Sync via USB-C Mass Storage Class. The microSD card mounts as a thumb drive when plugged in. Simpler firmware, no Wi-Fi cert headache, more honest UX.
- **Mic:** single Knowles SPH0645LM4H-1 PDM digital MEMS mic, ~£1.20 qty 100. AirPods Pro 1 used a single mic; that's the right precedent. No beamforming on v1.
- **No DSP.** Software Opus encoding on the nRF5340 application core. xMOS XU316 draws ~120mA vs ~5mA software penalty; not worth it for v1.
- **Storage:** microSD in a Hirose push-push socket, disguised as a cassette spool window inside the enclosure. Cassette aesthetic becomes literal storage.
- **Battery:** single 18650 Molicel M35A from Fogstar UK (Bromsgrove), Keystone 1042 surface-mount holder. Replaceable, vape-shop-commodity supply, right-to-repair story.
- **Hardware-locked LED:** in series with the mic preamp V_DD rail. Firmware physically cannot record without forward-biasing the LED. Tampering requires solder paste, not firmware compromise.
- **DPDT mute switch:** cuts mic power directly, not a soft signal to the MCU.
- **Aesthetic:** Sony WM-D6C × Nagra E × Playdate × TP-7. RAL 7035 or 9002 body, PMS Orange 021 C accent reserved for record button and recording indicator only. Sifam Tinsley analogue VU meter (Bracknell, custom dial MOQ 50+).
- **UK suppliers:** 3DPrintUK SLS body, JLCCNC anodised faceplate, JLCPCB Economic 4-layer SMT for prototypes, JJS Manufacturing in Lutterworth (35 minutes from Northampton) for production. Tusting in Northampton for leather strap.
**BOM and pricing.** ~£107 all-in at qty 100 before packaging. Supports £249 retail at 55% margin or £299 Founders Edition at 63%.
**Funding sequence (the research's strongest finding):**
1. **NLnet NGI Zero Commons Fund first** — €5k to €50k, 4 to 8 hour application, two-month decision, mandatory FLOS licence on outputs (CERN-OHL-S, GPL, CC BY-SA all fine), commercial use permitted, 0% equity. Audio-hardware precedents (Tiliqua, MILAN). **Deadline 1 June 2026.** GenAI compliance details in `docs/hardware/nlnet-genai-policy.md`.
2. **Soft pre-orders to Corbie waitlist second** — Stripe payment_intent, conservative delivery promise, capped at 100 units to stay under the £90k VAT threshold. Requires Ltd company first.
3. **Crowd Supply third** — only credible crowdfunding platform whose operating model handles solo-founder fulfilment via Mouser. 12% campaign fee, >90% campaign success, 100% historical delivery rate. Apply once 10 prototypes exist plus 50-100 validated pre-orders.
**Total elapsed timeline:** 22 months from 2026/04/27 to first units shipped.
**Total founder personal capital exposure:** ~£1,200 across dev hardware, Ltd company setup, T&Cs review, PCB iterations beyond what NLnet covers, and contingency.
**Hard discipline:** hardware never ships before Corbie software hits £2k MRR. No hardware work in any week where Corbie software has not shipped a meaningful change.
**Why it fits Corbie's positioning.** Plays directly to the local-first moat; Pocket cannot match because their stack is cloud-routed. The pendant's marketing line writes itself: "your audio never leaves your machine."
## Anchors
- Spec: [docs/brief/feature-set.md](docs/brief/feature-set.md) + [docs/brief/design-principles.md](docs/brief/design-principles.md)