Biper audit, plan, and structure

1. v0.8.1–0.8.17 • 19–20 Aug 2026

   Pair-trial day: seventeen patches to a working messenger

   Each from a defect the owner hit while testing two cubes: the hotspot name is a word, not digits — and each cube gets its own (both announced themselves as Biper-15FE, because the identifier slice the name came from is shared by a whole batch); the Wi-Fi password is fixed per cube and the hotspot window stays up while a phone is connected; the hotspot seats four devices, so a remembered laptop cannot lock the phone out; a cube in SIEC mode announces itself shortly after power-on, SAM stays silent; the contacts tab speaks a human word (KONTAKTY) and the Wi-Fi word can be set by the owner. The root of the pair that could not see each other turned out to be single: build-flag ordering compiled one class into two memory layouts, so the radio path stored contacts where the panel never looked. The panel now declares its protocol version (messages reach the phone), the password alphabet lost its OLED look-alike twins, the SLYSZE counter gained a presence beacon and treats a received message as proof its sender is alive, and the station word pool grew to 294. On the evening of 20 August the pair talks both ways from two phones, and an external UX audit closed the day inside the panel: a permanent recipient capsule at the input, the alarm reachable from every screen, green reserved for the link state.

2. v0.8.18–0.8.19 • 20 Aug 2026

   An external audit, four decisions, and a hard legal limit

   An external 36-area review of the whole fork (an independent AI model, 20 Aug 2026, internal report), executed with a falsifier on every claim — several findings rejected against evidence, the rest verified in code before anything was touched. The heaviest fixes: the radio oscillator powered as the vendor schematic demands (3.0 V instead of 1.8), the screen font completed (the wipe-in-progress caption was losing W, Y and U), messages received before the panel's first visit no longer lost, length gates on paths that read past the declared frame, and a compile-time guard on the contact-list geometry. On top of that, four owner decisions: a hard 10% airtime limit baked in so that no setting can raise it (the ETSI limit for the rescue sub-band), the hotspot gesture at a full three seconds, radio parameters kept community-compatible until measured, and a proper board definition with the real 16 MB of flash and a partition table ready for future cable-free updates. The pair trial after a full wipe: the cubes found each other on their own, and a private message got its radio acknowledgement in 1.2 seconds.

3. v0.8.20 • 20 Aug 2026

   The second independent audit: state truth and recovery

   A full review of both repositories by an independent AI reviewer (20 Aug 2026, internal report pinned to exact SHAs) confirmed nine P1 findings — each verified in code before anything changed. All six logic findings land in this release: DELIVERED lights up only when a confirmation hits the awaited marker — a late, duplicated or foreign one no longer changes the screen; the missing return in the frame-accept path is now a compile error, because the global warning silencer is stripped from our environments; the 10-second wipe gesture works with a dead display, and the countdown is audible; the hotspot window is held by a live panel, not by a merely remembered station; a full queue answers “busy” instead of losing a command silently; a phone taking over the panel flushes the old session’s pending commands. Plus a hard 8-character password check, verified page and task registration, Wi-Fi-name truth mid-window, 11 host tests of the pure delivery logic, and CI that now also builds the stock C6L profiles. This page now also tells the truth about the fork’s scale — see the metric above.

4. v0.9.0 • 20 Aug 2026

   The panel is the interface: Bluetooth leaves the release

   An owner decision after two independent reviews: the shipped system is the no-Bluetooth variant. The official app over BLE and the panel used at once could interleave each other’s responses (single-client protocol state in the MeshCore base), the BLE stack advertised pairing indefinitely, and conversations held outside the panel were invisible to the cube’s screen. After the change: the install file is a third lighter (1.56 MB), twice the free memory with the window open, and the screen sees every conversation. The full pair test ran on the exact bytes the installer ships: 10/10 messages confirmed both ways, median 0.82 s. The cube is not locked — whoever prefers the official app flashes stock MeshCore, and our installer always brings the Biper system back.

5. v0.8 • 19 Aug 2026

   The iPhone reaches the panel, the screen admits who it hears

   Apple’s network probe got the welcome page instead of a redirect, so the iPhone’s sign-in sheet browsed the cube as captive.apple.com and the panel’s origin guard rightly answered “bad host” to every tap. After the fix the sheet lands on the cube’s own address and the panel opens from the phone. Two visibility patches along the way: the SŁYSZY counter now counts a node the first time it is heard, and the panel bridge no longer goes deaf once the hotspot window closes.

6. v0.7 • 19 Aug 2026

   The wipe holds the screen to the end

   After the countdown the cube shows its fastest rings with the word WYMAZUJE until it reboots — previously the normal screen returned for a moment (owner-reported during testing). Along the way the site’s pixel-parity gate caught a never-ending loop in the rings’ square root before it reached a cube; the layer’s internals moved to English ahead of opening the repository.

7. v0.6 • 19 Aug 2026

   First public build in the installer

   The Biper system on MeshCore v1.17.1: the cube-served panel with contact backup on the phone, the screen language plus LED and buzzer signals, the SIEC/SAM relay switch persisted across restarts, a hotspot with the cube's password, wipe with a countdown, since 0.9.0 no Bluetooth in the release, identity-key export and import compiled out. The file's SHA-256 stands next to the installer and in the release manifest.

8. 17–18 Aug 2026

   Internal milestones, never released

   In order: hotspot, screen, sound and light, ninja mode, the memory diet (34 → 115 kB free), captive portal, the panel–radio bridge, the panel, hardening. Each milestone closed with a measurement on the development cube.

1. RESCUE IS FREE

   Crisis communication has no paywall

   The installer, the system file, the emergency panel and the instructions stay free. Supporting the project may cost money. A feature somebody’s safety depends on never will.

2. OPEN CODE

   The firmware layer will be published under MIT

   The decision was taken on 17 August 2026. Anyone will be able to read what the device they carry in a crisis transmits.

3. TRADEMARK

   We will register the “Biper” mark in the open

   With a public statement of who files it and why. The filing and its status go into this ledger, alongside the rest of the decisions.

4. AI DISCLOSED

   Biper’s development is AI-assisted and we say so plainly

   In the README, in the documentation and here. The code goes through reviews, quality gates and on-hardware tests. We see no reason to stay quiet about the tool we work with.

5. NO GATEKEEPERS

   We will not build an app you must have before the hardware works

   The phone will reach the cube through an open panel served by the device itself. A paid client as a condition of working is off the table.

6. COMMUNITY

   Community channels will be nobody’s private property

   When a forum, a chat or a map appears, administrative access will be documented and transferable.

The Charter is a statement of intent. The commitments about open code, the trademark and the panel concern things not yet built, and we track their state in the same ledger as the rest of the work.