# Archangel: physical Mac-to-Linux run, September 5, 2026

## What this record is

A founder-run report, supported by the installation output and receiver photographs supplied during testing. It is not independent replication, a comprehensive benchmark, a signed receipt archive, or platform certification.

## Frozen software identity

- Application: Braid Messenger 1.7.0a5 (Archangel).
- Mac packaging revision: mac-launcher-fix1.
- Universal public download: `Braid-Archangel-1.7.0a5-Mac-Launcher-Fix1.zip`.
- ZIP SHA-256: `b6bf35bd10edcb687e89e21f9674db0ca58a9dc7adb37b667c9d139213ab4227`.
- Application wheel SHA-256: `c828c1c19a2359181ebbbb3dd0bae6dc97b8745b1138702c4a3adcc98e3ec507`.
- This website release republishes the corrected ZIP byte-for-byte. No engine, dependency, launcher, or profile-handling bytes were edited for the site refresh.

## Reported sequence and visible evidence

1. The original Mac shortcut selected a Python outside the supported 3.10-3.13 range. The corrected Mac launcher completed installation on the MacBook Air. The supplied log shows CPython 3.12 / macOS arm64 dependency wheels, installation of braid-client 1.7.0a5, and successful local page/API responses.
2. The Linux laptop was launched using `sh "Start Braid.sh"` in its extracted release folder. The founder reported both nodes interlinked.
3. The exact-text test material was `Project Cobalt's launch color is amber.` The intended direction was MacBook Air to Linux.
4. An earlier photo showed the sender at Review and the receiver with an empty field. Those images alone did not establish which transfer step was missing. The guide now explicitly distinguishes Review from Send and directs users to inspect the receipt before retrying.
5. The final receiver photos show one indexed item, one indexed object, 384 dimensions, and the question `What is Project Cobalt's launch color?`.
6. The displayed guarded answer identifies amber. The expanded query record identifies application version 1.7.0a5, embedding model `all-minilm:latest`, configured completion model `mistral:latest`, and retrieval method `receiver-local_384d_cosine_plus_mmr`.

## What is and is not established

The founder report and receiver screenshots support a physical cross-OS handoff followed by indexed receiver-local field-question output. The final answer is the guarded workflow output; the visible excerpt does not independently establish whether the published text was the raw model draft or a guard fallback. The page therefore describes the workflow and the configured model, not an unobserved internal trace.

This run does not provide a complete sender receipt/packet archive, a no-handoff counterfactual after reset, independent third-party reproduction, latency or throughput measurement, persistence after restart, reverse-direction success, physical Windows validation, cold offline setup, or Managed Relay/WAN proof. It does not establish universal latent coordinates, native hidden-state or weight transfer, or automatic ingestion from another chat application.

The a5 QA and Mac-fix reports in this folder are retained baseline documents written before this physical run. Their older 'pending physical test' language is historical; this note adds the narrow new result without rewriting that history. The original UAT remains the plan for the outstanding matrix.

## Public images

`assets/archangel/physical-field-answer.jpg` and `assets/archangel/physical-field-evidence.jpg` are cropped/resized exports from the supplied receiver photographs. No UI values were altered. The hero inbox graphic is separately labeled an interface illustration, not a photograph or live session.

## Reproduction

Follow `archangel.html` on the website. Prepare and approve cards in both directions, configure the receiver's local model before enabling receiving, send one exact harmless fact, require an accepted-and-indexed receipt, retrieve the evidence, and then ask through Braid's Shared field. Unknown receipts must not be blindly resent.


## Published demonstration link (website revision 2)

The founder supplied this video link for the same demonstration:

[PROOF On Camera: Two Ollama LLMs Shared State](https://www.youtube.com/watch?v=UruJhL3oIE4).

The website links directly to YouTube only after the visitor clicks; it does not auto-embed a player or load a remote thumbnail. This website-editing run could not fetch the video through the web tool and did not independently watch it. The supplied review is not treated as an independent security audit or evidence of market priority. The original photograph-based evidence boundaries above remain unchanged.