INTERSIGNAL
Braid Messenger  /  Archangel 1.8.1

Your rigs.
On speaking
terms.

An inbox for the useful things your local AI should carry forward. Share reviewed context with an approved rig. Continue in channel chat with shared notes you can inspect. Keep control of both.

Channels + local chat + shared-note receipts. Now with the composer fix included.
Public 1.8.1 release. Mac fix retained. Python and local Ollama required.

Interface illustration, not a live session. Actual test photograph below.

PAIR ONCE   Your machines become contacts.SHARE DELIBERATELY   You review what leaves.QUERY LOCALLY   The receiver uses its own field.
Free local software. Optional membership.

Start free.
Build with us.

The same Archangel client in both columns. No membership required for local transfers. Join for human help, early access, and forthcoming managed reach.

THE LOCAL CLIENT

Braid Archangel

Free / no membership required

Connect the rigs you own. Keep the useful context moving.

  • Direct LAN transfersApproved rig-to-rig handoffs over your local network. No Intersignal relay needed.
  • QR reel / chunk transfersIncluded optical tools in the Advanced workspace. Camera and decoder requirements apply.
  • Your rigs, inbox, and receiptsReview a summary or exact text before sending. See acceptance and indexing separately.
  • Receiver-local shared field384D indexing, relevant-state retrieval, and guarded questions through your own local model.
  • Public releases and sourceUse the public client without a subscription. The Mac launcher fix is already included.
Download free Archangel

Python, Ollama, and models are separate prerequisites. About the QR tools.

THE FOUNDING MEMBERSHIP

Braid Founding Membership

$99 / year

Everything in the free client, plus a closer connection to the build.

  • Human supportReasonable, best-effort help with installation, pairing, troubleshooting, and upgrades.
  • Managed Relay access FORTHCOMINGFor at least 2 unique devices per active membership, once the member service launches and your access is provisioned.
  • First access to new versions & experimentsMember-first releases and experimental builds during your active membership term.
  • A direct feedback loopBring reproducible results and feature requests directly to the project. Not every experiment or request will ship.
Join Founding Membership

Support starts with membership; early builds are supplied as released. Managed Relay is forthcoming, not an active service included at checkout today.

Membership adds support and reach. It does not unlock the free client. LAN and QR tools stay free. Managed Relay has no announced activation date; its two-device minimum applies once the service is launched and provisioned during an active membership.

Service details & what is not included

Human support is reasonable and best-effort, not a 24/7 service or production SLA. Early access covers member releases and experiments as they become available during your active annual term; there is no fixed release schedule. Public software releases remain free.

Forthcoming Managed Relay access covers at least two unique devices per active membership once launched and provisioned. Service use will be subject to compatibility, capacity, location, and fair-use limits; no unlimited bandwidth or additional-device entitlement is promised here. A payment receipt is not a relay credential. Support starts when membership begins; there is no guaranteed relay launch date within the term.

Membership does not include computers, hosted inference, model subscriptions, Python, Ollama, or model downloads. Your local models remain yours to provision and run. This site update does not activate a relay or change existing subscriptions.

A familiar front door

Less control panel.
More “there’s my other rig.”

Think signed state mail for your local AI rigs: a small, deliberate place to carry useful facts, decisions, and constraints between the computers you own.

01  /  YOUR RIGS

Machines, not mysteries.

Name a rig. Prepare it locally. Exchange public rig cards and approve the full fingerprints in both directions.

Public cards. Private keys stay home.
02  /  YOUR INBOX

Share the useful part.

Paste context, make a local summary or keep the exact text, then review it before sending. Inbox, Sent, and receipts keep the work visible.

Write → Review → Share
03  /  YOUR SHARED FIELD

A handoff you can use.

The receiver indexes accepted material locally. Ask a new question through Braid and inspect the evidence behind the answer.

Relevant state. A fresh local question.
Included in 1.8.1 / Free for your rigs

One field.
Channels for what matters.

Your rigs are the contacts. Channels organize the project notes you deliberately share between them, and bring the relevant material into ordinary chat inside Archangel.

#Cobalt

A project conversation, not another context dump.

Create a channel once, share its signed card, and choose which rigs receive your outgoing notes, which publishers may send into your local copy, and whether notes can be used in your answers. Those are three separate choices, made on each rig.

Keep talking to your local model in Channel Chat. Relevant, permitted notes can join the conversation without another trip to the Shared field window. The inbox and individual handoff receipts are still there.

Set up your first channel →

#Cobalt / Channel Chat

What should we carry into the launch?

The launch color is amber. The threshold notes disagree: 73 and 75 remain unresolved.

Using 3 shared notes#Cobalt · MacBook Air1 unresolved conflict

Three exact source notes supplied to this example answer:

  1. Project Cobalt's launch color is amber.
  2. Project Cobalt's threshold is 73.
  3. Project Cobalt's threshold is 75.

In the app, expand this receipt to inspect the exact text, originating rig, source objects, arrival time, and whether the guard substituted a fallback.

Illustrative conversation, not a live model result. The count describes unique source atoms actually supplied to the completion request, including retained-history and conflict evidence. It does not measure attention or certify truth. One longer handoff can supply several atoms.

01 / REVIEW IS THE DEFAULT

Sharing stays deliberate.

Write a note, review its exact text and destinations, then confirm. A channel name is not permission: importing a card enables no sending, receiving, or chat use by itself.

Send to / Receive from / Use in chat
02 / SUGGEST, THEN AUTHORIZE

Useful automation. Small scope.

Chosen topic phrases can suggest a local draft, never an automatic transmission. Automatic sharing separately requires channel authorization, a chat opt-in, and a newly typed /note message. Rate limits and pause controls stay visible.

No auto-forwarding of replies or incoming notes
03 / KEEP THE DISAGREEMENT

Inspect the competing claims.

Explore conflicts within the channel and see unresolved alternatives alongside the answer evidence. Archangel does not quietly pick a winner or turn a newer note into authority. Formal resolution authoring remains future work.

Original claims remain inspectable

One field, supported paths. Direct approved compatible peers, signed-file transfer, and exported QR reels carry the signed channel identity into the same channel admission checks. Camera scans need physical testing and compatible decoder support. Managed Relay remains forthcoming; 1.8.1 does not provision it. Chat integration is inside Archangel, not an automatic bridge into unrelated chat apps.

Actual Mac Shared field screenshot after the Windows test: two indexed items, two indexed objects, 384 dimensions, and a fresh question answered with the blue group.
Actual receiver-local answer screenshot, unaltered. September 7, 2026 · founder-reported Windows → Mac test on 1.8.1. Test record ↗
1.8.1 / PHYSICAL WINDOWS → MAC TEST

Sent on Windows.
Answered on Mac.

A new project note traveled from the Windows laptop to the MacBook Air. A fresh question on the Mac then returned the group named in that note.

Shared note: “Second Kestrel run should involve blue group only

“Which team or group should the second Kestrel run involve?”

The answer: the blue group.

2INDEXED ITEMS, TOTAL
2INDEXED OBJECTS, TOTAL
384DIMENSIONS

The field count rose from one to two. The screenshot preserves the complete response, including its cautionary wording. This is a Windows-sender / Mac-receiver Shared field test, not a claim of model-weight transfer or qualification of every platform and workflow.

Earlier attempts arrived but were rejected because the clocks disagreed by about 12 seconds. After synchronization, the fresh test returned the new information. Clock-sync guidance →

Earlier a6 / Linux → Mac spending demonstration
Actual receiver Shared field screenshot: one indexed item and object; a new question about server credits returns 500, followed by cautionary wording.
Actual field-answer screenshot, unaltered. September 7, 2026 · founder-reported a6-line Linux-to-Mac run. Mac receipt ↗ · Linux source ↗ · LAN connection ↗
A6-LINE / PHYSICAL LINUX → MAC DEMO

Sent on Linux.
Answered on Mac.

A practical project constraint crossed from the Linux laptop to the MacBook Air. The Mac accepted and indexed it. A fresh, differently worded field question then returned the transmitted limit.

Shared note: “spend no more than 500 credits on our second server today”

“What's the max number of credits we can spend on a server today?”

500CREDITS RETURNED
1INDEXED ITEM
384DIMENSIONS
✓ Received✓ Accepted✓ Indexed✓ Fresh field answer

The screenshot preserves the full response, including its generic cautions. It returned the correct number but did not repeat “second server.” This demonstrates retrieval of shared context, not automatic spending enforcement. The demo predates 1.8.1; it is not a new 1.8.1 or Channel Chat qualification.

Earlier a5 / Mac → Linux demonstration

▶ PROOF On Camera: Two Ollama LLMs Shared State

The September 5 a5 video shows the Cobalt handoff and a fresh field answer on Linux. It is separate from the September 7 spending test. Earlier field-answer photograph ↗

Public Archangel / Version 1.8.1

Archangel.
One bundle.
Your own rigs.

The Channels experience, with the corrected composer and Mac runtime discovery built in. One complete 1.8.1 bundle for every rig; no separate repair install. The demonstrated a6 predecessor remains available below.

Have these ready on each rig

Standard CPython 3.10–3.13. Get Python. Choose a supported version, not 3.14.

Local Ollama + an embedding model. The first-run guide uses all-minilm. Get Ollama.

A local chat model for Channel Chat. The earlier a5 field-answer demo used mistral:latest.

Begin with two machines on the same private LAN. No Intersignal relay enrollment is needed for that path.

Ready-to-run does not mean zero prerequisites. The launcher installs Python dependencies into its own environment. Python, Ollama, and model weights are not bundled. First setup needs internet access unless you prepare the documented offline pack.
PUBLIC RELEASE · 1.8.1

Braid Archangel 1.8.1

Channels · One integrated release · 752 KB ZIP
The same complete bundle for macOS, Linux, and Windows.

Mac launcher fix included

Extract. Open Start Braid.command.

The Mac fix is already in this ZIP. It skips an unsupported default Python, finds a supported installed runtime, and prints its selection.

sh "Start Braid.command"

Terminal alternative: run the command above inside the extracted folder. Python must already be installed. No global Python setting is changed. Mac security guidance.

Linux launcher included

Open the extracted folder in Terminal.

Right-click an empty space in the folder, choose Open in Terminal, and run:

sh "Start Braid.sh"

Run as your normal user, without sudo. The Linux launcher uses your default python3. For an unsupported default, explicitly use an installed supported version, such as python3.12 start_braid.py.

Windows → Mac physically tested

Choose a supported Python explicitly.

Open the extracted folder in Terminal. With standard Python 3.12 installed, use:

py -3.12 start_braid.py

Use -3.13 instead when that is your installed supported version. Start Braid.cmd is also included, but uses the default runtime. This is not an Authenticode-signed installer.

Download Archangel 1.8.1 ZIP

Opens Google Drive in a new tab. Choose Download for the complete launcher bundle, not just the source archive.

Verify the exact download4c303b6aea21113812466ee2323c21d8dac26cb45d7c54474d9c7b270d74111d

SHA-256 of the complete ZIP. Consistency check, not a publisher signature.

INCLUDEDApp + source + platform launchersThe corrected Mac launcher, isolated setup, offline-pack tools, test evidence, and full source travel together.
NOT REQUIRED FOR LANNo account. No managed relay.Direct approved-rig handoffs do not automatically use an Intersignal relay. Keep the local UI private.
VALIDATION SCOPEStart with harmless test context.The a6-line demo returned the transmitted 500-credit value. Exact 1.8.1 native-device checks remain separate. Windows, optical and WAN are not certified by that demo. Not a signed native installer.
A first channel, not a terminal marathon

Two rigs.
One useful conversation.

Start with a reviewed exact note and one receiver. Keep automation off until the basic channel path works on your machines.

Open and pair.

Launch 1.8.1 on both rigs. For a new pair, exchange rig cards, compare the full fingerprints, and approve in both directions. Existing a6 cards remain compatible.

Create one channel.

Create Cobalt on the Mac and import its signed channel card on Linux. Select sending, receiving, and use-in-chat permissions independently.

Review. Then share.

Write one exact note. Review destinations, confirm once, and inspect the remote acceptance and indexing receipt.

Continue in Chat.

Ask on Linux with shared notes enabled. Expand Using 1 shared note to inspect the exact supplied evidence.

Received → Accepted → Indexed

Three different confirmations. A local note commit is not a remote receipt. An uncertain outcome is not permission to resend.

The interface is small. The idea is not.

Useful context travels.
Authority stays local.

WORKING TODAY

A shared-state foundation.

Braid carries explicit, signed semantic material. Each receiver applies its own acceptance policy and builds its own searchable 384-dimensional field. Retrieved evidence and model output stay inspectable. Signatures and similarity do not make a claim true.

THE DIRECTION

Richer interchange, without pretending.

We are building toward richer validated interchange states across independent AI systems. Today’s release is the foundation, not native hidden-state transfer. It does not move model weights, KV cache, or a complete model mind.

Before you click

A few things worth knowing.

Does Share summary now start a new message?

Yes. In 1.8.1, Share summary and the N shortcut open blank at Write, instead of reopening an old saved delta. Open Drafts explicitly to resume saved work. New message, X/Escape, and Discard draft have distinct actions; discarding never clears accepted objects or delivery history. The single saved-draft slot asks before replacing other work. Composer guide.

What does “Using 3 shared notes” actually count?

Unique exact semantic atoms supplied to the successful completion request, including evidence carried with retained conversation history and any supplemental conflict notes. Identical atoms count once even with several source objects. It is not the number of documents, every retrieved candidate, verified facts, or the model's measured internal attention. Expand the receipt to inspect what went in and whether a guard fallback supplied the final answer.

Does this automatically share everything my local AI knows?

No. Reviewed notes are the default. Topic phrases can create local drafts only. Automatic sending requires a channel policy, a separate chat opt-in, and a new user-authored /note message. Incoming notes, model replies, and ordinary conversation never auto-forward. Channel Chat is inside Archangel; unrelated chat applications are not intercepted.

What did the Mac patch fix?

The original shortcut could choose an unsupported default Python and stop before opening Braid. The integrated Mac launcher checks supported installed runtimes, including common Homebrew and Python.org locations, then prints the interpreter it selects. It does not install Python, alter global aliases, or retry application failures under another interpreter. That correction is retained in 1.8.1, alongside the fix that makes Share summary start a genuinely new message.

Will this send traffic through an Intersignal relay?

Not for the direct private-LAN workflow shown here. Rigs connect to the approved endpoint in the exchanged card. Managed Relay / Jump Kit is a separate enrollment and configuration path, not a switch activated by downloading Archangel. No production relay availability or WAN result is implied by this LAN demonstration.

Can I use different models?

The completion model is receiver-local; Braid carries explicit material rather than requiring identical model weights. For the simplest first run, use the guide’s matching all-minilm embedding setup. The earlier a5 field-answer test used mistral:latest for the receiver’s configured completion model. The spending-demo screenshot shows a returned 500-credit value but does not display its exact model digest or raw query record; it is not a full compatibility matrix.

What has actually been tested?

On September 7, the founder reported a physical 1.8.1 Windows-to-Mac handoff followed by a successful fresh Shared field question. The supplied screenshot shows two indexed items and objects, and returns the new “blue group” detail. See the Windows-to-Mac test record for the exact scope. The earlier a6 Linux-to-Mac spending demo and a5 Mac-to-Linux video remain separate evidence.

The 1.8.1 build also passed 349 Python tests and six subtests with fixture models, plus composer-browser and installed-launcher checks. The physical run does not establish Windows receiver testing, restart persistence, Channel Chat, or WAN/relay qualification. Read the historical 1.8.1 build notes and the remaining checklist.

A message arrived, but it says Not accepted. Why?

An Inbox record can preserve a rejected transfer without adding it to the shared field. Open Receipt & provenance. If the reason is ERR_FUTURE_TIMESTAMP, check automatic time synchronization on both computers. Do not disable timestamp checks or repeatedly resend. Follow the clock-sync steps.

What should I do when the field is empty?

Stop at the receipt. Check the remote outcome in Notes & activity or the retained Inbox/Sent receipt. Confirm that both rigs imported the same channel card, the publisher is allowed, and shared-note use is enabled. Drafts and local commits alone do not prove remote acceptance. An unconfirmed receipt is not permission to resend. Open the troubleshooting guide.

What is free, and what does $99/year add?

Archangel's local Messenger, LAN transfers, QR reel / chunk tools, receiver-local field, and public releases are free. Founding Membership adds human support, first access to new versions and experiments, and forthcoming Managed Relay access for at least two unique devices once launched and provisioned during an active term. The QR tools use the Advanced workspace and depend on compatible camera/decoder support. Compare both options.

The inspectable record

Keep the evidence.
Keep the earlier work.

The 1.8.1 Windows-to-Mac record includes the new field-answer screenshot and the clock-sync lesson from the physical run. Full source, build evidence, the earlier a6 spending test, and the a5 demonstration remain available.

Looking for the older native installers? They remain in the historical download archive. They do not contain Archangel Messenger.