INTERSIGNAL
Intersignal Braid / Archangel 1.9.1

Your rigs.
Within
reach.

An inbox for the AI rigs you own. Share useful context for free on your LAN. Add membership-activated Away from home to connect across networks and ask a permitted question of your home rig.

One client. Free LAN. Optional managed reach.
Managed WAN early access · activation required. Python and local Ollama required.

Interface illustration, not a live connection or a recorded WAN answer. Physical evidence is kept separate below.

YOUR MACHINES   Independently operated.YOUR CONTEXT   Deliberately shared.YOUR CHOICE   LAN or managed relay.
Free local software. Optional membership.

Start free.
Build with us.

The same 1.9.1 client in both columns. Start locally without an account. Join for human support, early releases, and managed reach beyond your home network.

THE LOCAL CLIENT

Braid 1.9.1

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 sourceThe full public application and source. Away from home is already built in; membership activation is optional.
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 human help and a route beyond home.

  • Human supportReasonable, best-effort help with installation, pairing, troubleshooting, and upgrades.
  • Away from home MANAGED WAN EARLY ACCESSManaged Relay access for at least 2 unique devices when provisioned. Share context across networks and send separately permitted Channel questions to your home rig.
  • 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

Human support starts with membership. Managed WAN is early access and requires separate, operator-assisted activation. Checkout does not instantly enable remote access.

Membership adds support and reach. It does not unlock the free client. LAN and QR tools stay free. For away-from-home access, check activation availability with us before joining for that capability alone. No second installer.

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.

Managed Relay is in early access. At least two unique device identities are included once your access is provisioned during an active membership. Availability is confirmed through support; deployment, hardware compatibility and final workflow checks matter. Service use is subject to compatibility, capacity, location and fair-use limits. There is no promise of unlimited bandwidth, instant activation or additional-device entitlement. A payment receipt is not a relay credential.

Home rigs must remain awake, online and running Braid. Remote questions need a separate peer-and-Channel grant. Membership does not include computers, hosted inference, model subscriptions, Python, Ollama or model downloads. This page does not change billing or activate a rig. Read the current WAN test boundary.

PHONE HOME / BUILT INTO 1.9.1

Your home rig.
Still in the conversation.

Your laptop travels. Your local model stays home. Use Braid to carry a selected note or a permitted question between them.

Membership-activated · early access

Same inbox.
A longer reach.

Enable Away from home on your activated rigs. Choose Managed WAN for the approved destination, rather than opening ports on your home router.

For a remote question, the home rig decides which peer can ask which Channel. Its configured local model produces the answer and returns inspectable shared-note evidence.

ONE FIELD. ANY PATH.HOW IT WORKS
Traveling rigYour Braid client
Managed relayEncrypted payloads
Home rigYour local model
YOU CHOOSE WHAT LEAVES

A reviewed project note.
A question to an allowed Channel.
An answer with shared-note evidence.

Both rigs initiate outbound HTTPS. No customer DigitalOcean account, server SSH key or router port forwarding. Illustration only; not a live status display.
Home stays online.

Keep the rig awake, connected and running Braid. This is not remote power-on.

Permission is specific.

Receiving notes and answering remote Channel questions are separate choices.

Not remote desktop.

No shell, file browser, public Ollama endpoint or phone-browser portal.

The managed relay is deployed and client activation is integrated. Early-access workflow validation continues. Request delivery windows are at most five minutes; this is not a multi-day offline mailbox. See what the physical run established →

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.9.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. Approved local peers, signed-file transfers and exported QR reels carry the signed Channel identity into the same admission checks. Activated members can select Managed WAN. Camera scans require compatible decoder support and physical testing. Chat integration is inside Braid, not an automatic bridge into unrelated chat apps.

REAL MACHINES / RELEASE-LABELED EVIDENCE

Not just a diagram.

Earlier local handoffs established the workflow. The September 10 WAN record establishes cross-network delivery and the clock check that must still pass.

SEPTEMBER 10, 2026 / 1.9.0rc1 PHYSICAL SESSION

Across two internet connections.

Transport evidence · not an accepted-note claim

The Mac used condo Wi-Fi; the Windows rig used the independently operated Starlink connection. Both direct LAN receivers were paused. The deployed relay passed external HTTPS checks, both rigs activated and discovered each other, and the Mac's receipt identifies managed_wan delivery.

The particular frame shown in that receipt was rejected before commitment: its timestamp was eight seconds ahead of the receiver's clock. Delivery and acceptance remain separate. The clocks must be synchronized before a fresh accepted/indexed test.

Exact evidence boundary & remaining checks

Operator-reported physical session, not an independent audit. The receipt records source_transport: managed_wan, transport_completed: true, accepted: false, phase_b_committed: false and REJECTED_BEFORE_PHASE_B. Its stored copy is in the rejected-message directory, not accepted shared state.

A separate accepted/indexed excerpt has a different frame digest and is not combined with this record. A matched successful WAN handoff after synchronization, a physical remote-model answer, native Safari confirmation of 1.9.1, and the remaining failure/endurance tests still need to be recorded.

1.9.1 passed 457 Python tests and six subtests, plus three compatibility tests against the original rc1 relay implementation with fixture models. Those are automated checks, not a replacement for the physical gates. The full QA record and physical-session note are included in the release ZIP.

The earlier screenshots below remain evidence for their named local releases. None has been relabeled as a 1.9.1 WAN demonstration.

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.9.1

One download.
Your whole fleet.

The inbox, Channels, local field and Away from home travel together. This is the same complete 1.9.1 application for free LAN users and activated members. No sidecar fixes or separate member installer.

Have these ready on each rig

Standard CPython 3.10–3.13. Get Python. Use a version supported by this release.

Local Ollama + an embedding model. The setup uses all-minilm. Get Ollama.

A local completion model for Channel Chat or answering questions on the home rig.

Start with two local machines for free. Managed WAN additionally requires Intersignal activation and internet access on both rigs.

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.9.1

Intersignal Braid 1.9.1

Free LAN · integrated Away from home · 2.52 MB ZIP
Same complete bundle for macOS, Windows and Linux.

macOS launcher included

Extract. Open Start Braid.command.

Supported-runtime discovery is built in. The launcher skips unsupported defaults, finds a supported installed Python, 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 launcher included

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 Braid 1.9.1 ZIP

Opens your complete Braid-Archangel-1.9.1.zip in Google Drive. Choose Download for the whole bundle, not only the nested source ZIP.

Verify the exact 1.9.1 download

File: Braid-Archangel-1.9.1.zip
Size: 2,517,085 bytes

a13da581eec0a62700429ba7c76ab8cc84fbbea6fd768287d98236bb100d4a3d

SHA-256 consistency check, not a publisher signature.

Save checksum · Save release metadata

INCLUDEDApp + source + launchersOne integrated release. Roomier WAN panel, receipt export, clearer errors and the existing corrected composer.
FREE LOCAL USENo membership needed for LANKeep context and model inference on your rigs. QR tools remain in the Advanced workspace.
OPTIONAL MANAGED ACCESSActivate. Approve. Choose WAN.Intersignal-assisted activation and explicit peer permissions. No second application to install.
START LOCAL / ADD REACH WHEN IT MATTERS

Two rigs.
One useful conversation.

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

Open and pair.

Launch 1.9.1 on both rigs. Prepare the local route, exchange signed rig cards and compare the full fingerprints before approving each other.

Create one Channel.

Create a project Channel on one rig and import its signed card on the other. Choose sending, receiving and use-in-chat permissions separately.

Review. Then share.

Write a harmless exact note. Check its text and destination, confirm once, then inspect the receiving rig's acceptance and indexing receipt.

Continue in Chat.

Ask the receiving rig with shared notes enabled. Expand the shared-note count to inspect the exact material supplied to the local model.

Received → Accepted → Indexed

Different confirmations, not interchangeable green lights. A local commit is not a remote receipt. An uncertain outcome is not permission to resend.

Already using Braid? Upgrade without starting over.

Quit the running client and back up its complete private profile, including the WAN encryption key when present. Extract the whole 1.9.1 ZIP to a new folder; do not replace individual files or run two versions against one profile. Launch normally and confirm 1.9.1 beside Settings & tools.

Existing rc1 activations, approved peers, Channels, saved settings and delivery records remain in the profile. Do not reissue activation files or re-pair solely for this update. The installed rc1 relay remains compatible and does not need redeployment. A previously enabled WAN profile resumes its existing settings; a fresh LAN installation starts unactivated/off.

Set up the first Channel.

Create a Channel once and exchange its signed Channel card. On the sender, choose the intended rig under Send to. On the receiver, explicitly allow the publisher under Receive from and enable Use in chat when desired. Matching names alone do not make two Channels the same identity.

Choose exact text for your first note. Review the recipient, send once and confirm the receiving receipt before asking a fresh question. Topic drafts and automatic sharing remain separate opt-ins. The complete setup and troubleshooting guides are inside the ZIP.

Set up Away from home with Intersignal.

Check early-access availability with support. Save a public .braidjoin request from each intended rig. Intersignal returns a device-bound private .braidmember activation. Import it only after independently comparing the full operator fingerprint supplied through support.

Enable Away from home and incoming notes where intended. Publish current rig cards, discover your member rigs, compare full peer fingerprints, and approve them. Select Managed WAN for the destination and save. Discovery alone is not approval; a LAN failure never silently selects the internet.

For Ask your home rig, separately grant that peer the intended Channel on the home machine, enable that Channel's Use in chat and Send to permissions, and select its local completion model. Send the intended question from the traveling rig and inspect the returned shared-note evidence.

Keep private activation files and profiles off public hosting. No router forwarding, DigitalOcean account or administrative SSH key is needed on a member's device.

macOS approval and other prerequisites.

Use a standard supported Python 3.10–3.13 installation and your own Ollama models. On macOS, use the operating system's per-item approval when required; do not disable Gatekeeper or other protection globally. This ZIP is not a notarized DMG or an Authenticode-signed Windows installer. Follow START_HERE.md inside the complete release for platform-specific and offline setup.

Where are the QR reel and chunk tools?

They remain included in the free client's Advanced workspace. Optical transfer needs compatible camera/decoder support and its own physical testing. It does not require Managed Relay activation. Follow the optical instructions in the downloaded source and guides; the WAN tests are not camera qualification.

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 start a new message?

Yes. Share summary and the N shortcut start blank at Write. Open Drafts explicitly to resume saved work. New message, X/Escape and Discard draft remain separate actions. Discarding a draft never erases accepted objects or delivery history. The single saved-draft slot asks before replacing other work.

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's new in 1.9.1?

Away from home now has a definite viewport-bounded layout, a generous scrolling body and readable fingerprint wrapping. This addresses the collapse reported in Safari; native Safari confirmation of the new layout remains part of the final physical check.

Action errors stay visible across refreshes. Clock failures get plain-language guidance. Explicit pre-commit rejections remain rejected even when a copy was stored in quarantine; incomplete evidence stays unconfirmed. Receipt & provenance adds Save receipt JSON without a resend. Activation-file errors clear stale previews.

The corrected composer, Mac runtime discovery, free LAN, Channels, wire protocol, cryptographic checks and relay implementation remain. No system clocks are changed, no validation gates relaxed and no automatic resend added. One complete package, not a repair kit.

Does Braid send everything through Intersignal?

No. Free LAN handoffs connect directly to your approved peers. Managed WAN is a separately activated, explicitly selected route through the Intersignal relay. Both rigs make outbound HTTPS connections; the encrypted payload is addressed to the approved peer.

The relay can see routing, timing, sizes and public rig-card metadata, not the plaintext inside the encrypted handoff. This is not a claim of post-quantum protection or forward secrecy after recipient-key compromise. Local state is access-controlled, not encrypted at rest. No other app's chat history is automatically uploaded.

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?

The named 1.8.1 Windows-to-Mac and earlier a6 Linux-to-Mac runs below show local handoffs followed by fresh field answers. The September 10 rc1 session additionally established deployed relay connectivity, two-device activation, discovery and cross-network receiver delivery with LAN receiving paused. The shown WAN frame was rejected for a clock mismatch, not accepted.

The 1.9.1 build passed 457 Python tests and six subtests, three rc1-relay compatibility tests with fixture models, and 70 new Chromium layout/diagnostic checks. Native Safari/Edge execution is not claimed by those tests. Matched successful WAN acceptance after clock synchronization, a physical remote answer, and remaining failure/endurance checks are still to be recorded. Read the WAN evidence boundary. Full QA and physical-session notes are inside the ZIP.

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

A receipt can preserve a rejected transfer without admitting it to the shared field. Open Receipt & provenance and read the reason. If it is ERR_FUTURE_TIMESTAMP, verify automatic time synchronization on both computers; the receipt alone does not identify which clock is wrong.

On Mac, check System Settings > General > Date & Time. On Windows, check Settings > Time & language > Date & time and the synchronization result. Different display time zones are fine. Do not alter signed timestamps, relax checks or repeatedly resend. Use Check WAN receipt (no resend) for an uncertain outcome. Save receipt JSON exports the existing record; review its text and local paths before sharing it.

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. .

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

The local Messenger, LAN transfers, QR reel/chunk tools, receiver-local field, project Channels, local chat and public source are free. Membership adds best-effort human support, early access and provisioned Managed Relay access for at least two unique device identities during an active term. Managed WAN is early access; confirm availability with support before joining for it alone.

QR tools remain in the Advanced workspace and depend on compatible camera/decoder support. The same 1.9.1 installer serves both offers. Compare both options.

Does “phone home” mean an iPhone app or remote desktop?

No. It means using Braid on a traveling computer to exchange selected context or ask an authorized Channel question on a home rig. This release does not include a smartphone-browser portal, remote desktop, filesystem access, shell or automatic wake-up. The home machine must remain awake, online and running Braid.

The inspectable record

Keep the evidence.
Keep the earlier work.

Full application source, release notes, QA and the September 10 physical-session record are in the 1.9.1 ZIP. The earlier Windows-to-Mac, spending-constraint and Cobalt demonstrations remain available with their original release labels.

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