Intersignal

Braid Light Client v1.4.9 · receiver-hardening candidate

Build the AI substrate first.

Braid moves signed AI state across machines without forcing every exchange through a cloud intermediary. QR reels remain intact. Version 1.4.9 hardens the receiver-owned acceptance boundary across optical, LAN, and explicit Internet paths, with scoped replay/session state and auditable receiver-local provenance.

Download v1.4.9 candidate ↗ Read release facts
Developer release candidate · optical + LAN + operator-controlled Internet paths · 83/83 conformance tests
BRAID
Air-gapped QR Reels Optical transport retained
Local LAN Direct Private-address transfer
Remote Internet Port Explicit host:port + TLS
One signed object, multiple paths

Transport is a choice. Trust stays local.

The transport layer carries the exact signed .brad bytes. It does not reinterpret, re-sign, or silently admit them. The receiving machine quarantines the object first, evaluates Phase A evidence, and only marks acceptance after the receiver-owned Phase B transaction commits finality.

TRANSPORT_01

Optical QR reels

The air-gapped path remains a first-class option for camera-based transfer, demonstrations, and environments where network access is undesirable or unavailable.

TRANSPORT_02

LAN direct

Signed state can move between machines on a private network, with optional discovery and explicit receiver ownership of quarantine, evidence, and finality.

TRANSPORT_03

Internet host:port

Operators can expose an intentional TCP endpoint for remote transfer. Public routes require TLS 1.3 by default; there is no silent router mutation or hidden relay.

Release facts

Braid Light Client v1.4.9

A finality-hardened developer candidate that preserves the established optical and network paths while tightening the boundary between evidence, validation, and receiver-owned authority.

Status
Developer release candidate
Primary object
Opaque signed .brad bytes
Network paths
LAN + explicit Internet TCP
Public security
TLS 1.3 required by default
Receiver flow
Quarantine → Phase A evidence → Phase B atomic commit → accepted finality
Finality invariant
accepted == (finality == "committed")
Optical path
QR reels preserved
Local derivation
Receiver-generated state is lineage-bound and explicitly non-authoritative
Acceptance

Verified candidate behavior

  • 83/83 tests pass with ResourceWarning promoted to error
  • Clean wheel and source-distribution install gates pass
  • Transport cannot acknowledge acceptance without committed Phase B finality
  • Legacy external validators remain prevalidation evidence only
  • Replay/session heads are scoped by receiver + signer + route + session
  • Concurrent duplicate Phase-B commits yield exactly one winner
  • RFC 8785 UTF-16 ordering and numeric regression vectors pass
  • Receiver-local 384D artifacts emit explicit lineage sidecars
SHA-256 · release-candidate TAR
1148e303c36917747849c9097b46d83735e76f3a51a65d74c9d69da0afb72f90
Open release archive ↗
The Intersignal thesis
AI systems should be able to exchange useful state without surrendering identity, provenance, or operator control.

Braid is being built as an open coordination primitive for local and sovereign AI systems: compact state, signed envelopes, receiver-owned policy, and transport flexibility from a camera lens to an open Internet port. Version 1.4.9 keeps one rule deliberately simple: evidence may travel; authority remains local.