The implemented baseline.

This revision uses the October 11 source and documentation archive, plus the October 12 recorded demonstration. The broker cleanup remains a plan.

Versions reviewed.

Component	Baseline	Source record
FD&F region and node payload	fdf-2026-10-11-r19-a15	MANIFEST-2026-10-11.md and MERGE-r19-a15.md
Android member / packet engine	a15 / b11	October 11 manifest; earlier acceptance record in MERGE-r19-a14.md
Windows bridge	fdf-kt-2026-10-11-a15 / fdf-tun-2026-10-11-b11	Authoritative package label: opt/fdf/windows/bridge/BUILD.txt in the reviewed October 11 source archive. Check the deployed BUILD.txt and startup log when installing.
Desktop Communicator	comms-app-2026-10-10-r3	Communicator STATUS.md
Android Communicator	comms-android-2026-10-11-r5	One implementation inside the FrogNet member app.
Cleanup	PLAN-CLEANUP-2026-10-12.md	Proposed changes; completion not established.

What changed from the broker-era site.

Region mode derives discovery and routes from shared facts. The old crawl is bypassed. The daemon applies the graph on region events; runMerge remains for boot and interface changes. Role election uses capabilities from alive region participants and does not depend on querying the failed application RAM host.

Phones and PCs are first-class named members. An on-mesh device uses its existing address. An off-mesh device becomes a leaf through the hub. Devices can participate in several ponds and reach permitted ponds through per-scope aliases.

The Communicator has a C++ desktop application and Linux RAM/media servers; Android’s Communicator is part of the membership app. Older game, Python mediahost and broker material is not a current installation guide. The cleanup plan proposes removing runtime remnants, not pretending that none remain.

Where the current code lives.

opt/fdf/src/fdf-source/             # region, node integration, tests and release tools
opt/fdf/src/frognet-android/        # Kotlin member, Android app, Go packet engine
opt/fdf/windows/bridge/            # runnable Windows bridge folder
opt/frognet_semantic/ribbit/examples/communicator/
                                  # desktop application and RAM/media servers

The current source repository remains FawcettJohnW/FrogNet-Living-Network. The build records above freeze what was examined for this site revision; they are not a claim about later repository changes.

Open implementation work.

The cleanup review found that fresh region-node installation still depended on broker-generated keys and shared broker code paths. The .run packages require an existing FrogNet installation. Removing old directories before fixing those dependencies would break the supported path.

Other recorded open items include the Python wrapper’s reset integration, some monitor presentation differences, hardware failover timing and the emulator’s call startup lag. The frame timestamp and local “here” clock make that lag observable; its root cause is not established.

The latest October 12 demo shows the call’s resolution, frame rate and receive-side throughput, and times two runMerge invocations. It does not prove that the full cleanup, every handset transition or every recovery case has been qualified.