Engineering desk demonstrations

Watch the system run while the architecture is explained.

The videos are part of the learning path. They show the code and running system rather than replacing either with presentation slides. Older videos remain useful where noted; historical mechanisms are labeled rather than silently presented as current.

Windows and Android: the next live demonstration.

Windows and Android, October 12.

This new operational recording begins with Windows outside the private FrogNet network. Starting the bridge enables a path; the PC becomes a named member. Android joins and the two clients run a live Communicator call.

The latest recording is supplied in the current work record as a transcript. No public playback URL was supplied with it, so this page records the observed sequence without inventing a player link.

Step	Observed behavior
Before the bridge	Ordinary Internet reachability; private FrogNet ping fails.
Start membership	Forward-via-hub path appears; private ping and SSH work.
Inspect state	PC in /etc/hosts and monitor; live topology map accessible.
Add Android	Device in /etc/hosts; Communicator presence and call.
Observe call	Displayed 1280×720, 20 fps, roughly 1.2–1.5 Mb/s on the receive-side stats.
Stop bridge	Windows private-network access disappears.

The transport is WireGuard beneath shared-state membership. The call uses the actual RAM and media services on the network. These mechanics remain visible even though the application does not configure them.

On-camera observation	Result	Context
runMerge rebuilding the network view	4.9 s, then 0.79 s	Timed command after removing the hosts file; the second invocation is a repeat run, not a separate failover measurement.
Windows–Android call	1280×720 · 20 fps · roughly 1.2–1.5 Mb/s	Displayed receive-side statistics in this demonstration, not a bidirectional total or a portable bandwidth requirement.
System code size	Under 35,000 lines	Reported in the demonstration for the system’s action code.
Android application code size	Under 6,000 lines	Reported in the demonstration for the Android app.

The line counts are reported in the October 12 demonstration, not a fresh source audit. A reproducible LOC comparison requires the checkout, counting tool and exclusions for tests, third-party/vendor code, generated files and build output.

Communicator evidence recordings

Three recordings worth seeing first.

These are separate recorded runs of the Communicator. They establish different operating points and different parts of the programming model; one measurement is not substituted for another.

Proof It Works

Steady-state 900 MHz run: bidirectional 1280×720 at 22 fps under a 1 Mbit ceiling. The on-screen did/would counter is the record; the narration states the savings several ways, and 89% saved is roughly 9×.

Bandwidth Experiments

A separate ladder walk: bandwidth driven from 987 to 637 to 450 Kbps while audio holds priority, then recovery toward 850 Kbps without redial.

Communicator and Shared Memory

The application reading and writing the shared store: the programming surface underneath the call.

On-ramp: install to working application

Follow these in order if you want the original guided path from hardware through discovery and into Memory and the Communicator.

Welcome

Root cause, instrument, prove, and where FrogNet came from.

What it is

A standalone, autonomous mesh and the first-implementation posture.

Hardware

What must be hardware and what only must be software.

Installation, part 1

Recording scope: Recorded installer and broker setup. Current .run packages update an existing FrogNet node into region mode; use the current operator path for that deployment.

Install, prompts, pond and LilyPad setup.

Installation, part 2

Recording scope: Recorded local/broker-era merge. Region-event application now uses shared facts, world and the graph; runMerge remains for boot/interface work.

First boot, routes and the node joining the network.

Broker install

Recording scope: Recorded broker path. Current region membership and relay use the RAM manager and fdf-hub.

Connect independent FrogNet sites through the broker.

The Monitor

Watch published network state and learn the Memory surface.

The Communicator

Recording scope: Recorded earlier Communicator and role machinery. The current desktop/Android implementation and per-viewer media path are described in the current chapters.

The adaptive media ladder running on the real path.

Deep dives

These explain individual mechanisms after the on-ramp. Notes identify material that describes an earlier implementation rather than the current contract.

Discovery deep dive

Recording scope: Recorded local recursive discovery. Current region membership derives from published facts and the region session.

How a node finds neighbours and installs routes.

More Discovery

Recording scope: Recorded local recursive discovery and route selection. Region mode uses facts/world/graph instead of this crawl.

Recursive expansion and route selection; some mechanism discussion is historical.

Proxy and Daemon

Intercept, permanent socket and live byte accounting.

Semantic Compression

BLDC/FNWP and live pipe_workload measurements.

Semantic Message Handlers

DatabaseHost

Recording scope: Recorded service-host implementation. Current region selection reads capability facts rather than querying the failed application store.

Historical implementation material about the moving service host.

Intro to Tuples

Tuple-space background and FrogNet three-coordinate addressing.

Tuples and REST

Older tuple/application discussion; notification-era passages are historical.

Tuples and REST, part 2

Continuation of the older tuple/application discussion.

Memory Backing Store

Older implementation view of where Memory bytes were backed.

Simulator

Attack the network mechanics under arbitrary topologies.

The Guild

Why the project is larger than one implementation or one person.

Security

The exposed surface as demonstrated in that implementation.

Existing Networks

Insert FrogNet beneath an existing network rather than migrating every host.

Troubleshooting

Where to look when the network does not behave as expected.

Recorded demonstrations

The older demonstrations also captured the 900 MHz Communicator path, bandwidth degradation, physical control, merge/reboot behavior, fan-out and mixed workloads. Those measurements remain in the evidence record; the current site does not turn planned recordings into evidence.

Read the evidence ledger Follow the complete workflow

Open qualification work

The current Windows and Android demonstration establishes the operations shown. Hardware failover timing, every device transition, region capacity and general application recovery remain separate qualification work. The implementation record names the current mechanisms and open items.