Engineering preview Mac signed execution passed Windows / Linux not yet

Connect your machines.
Feel the speedup.

Tether is a local-first elastic hardware fabric in ENGINEERING PREVIEW. Pair an authorized Mac you already own, verify usable capacity from signed receipts, and run an eligible class with tether --auto. Fail-local stays on. Windows and Linux peer proof is still blocked. This is not GA, not a consumer product, and not a billed service.

How pairing works Get the bits

Checkout or local-unsigned install only. No accounts, no billing, no telemetry. The public feed host exists; a signed stable.json has not been published.

Status now

What is actually ready

This page is static HTML. It does not query your fabric, invent peers, or refresh live capacity. Empty cells here mean “not on this page,” not “your machines are offline.” Live totals belong on the status dashboard after tether-fabric status --json.

Preview

ENGINEERING PREVIEW

Owned-hardware ENGINEERING PREVIEW. Surfaces must stay truthful. Doctor remains fail-closed.

Mac pass

Signed Mac execution

Generation 20260901T081436Z: n=3 signed exact-output auto-win, p95 17.121s vs local 28.230s, expiry fallback, zero residue.

Blocked

Windows and Linux

OS probes exist in tests. No authorized real Windows or Linux hosts yet. Do not claim parity.

Not ready

doctor stays NOT_READY

0/14 gates. ready_for_activation: false. That is honest, not a broken page.

Live peer list: empty on this page. After pairing, run tether-fabric status --json and open the status dashboard.

1.40x
legacy adopted-auto parallel CPU win on one qualified Mac peer
G3 PARTIAL · client-observed · exact output
64
Python modules in src/ as of the readiness matrix
snapshot 2026-08-31 · not a market count
3942
passed tests on the current-byte local full suite
8 skipped · 1 expected xfail · rc 0
How it works

Four checkout steps. No installer.

Eligible work uses tether --auto. A paired Mac can take a qualified class when receipts say it is usable. If the peer is missing, slower, or revoked, execution stays local. PATH shims exist in code and still fail doctor (0/14). Pairing itself is three numbered steps in the Mac app — the pairing steps page matches that copy exactly.

01

Install from checkout

Build the clean wheel and install it on the controller. A polished signed installer and updater are not shipped.

python3 -m pip install /path/to/tether-wheel.whl
02

Pair your machines

Create an explicit paired-key relationship with a machine you own or are authorized to use. Automatic discovery is not shipped yet.

tether-fabric pair create PEER_ID --display-name NAME --json
03

Read signed status

Inspect the receipt-backed snapshot. Physical, connected, and usable totals come from signed status, not this page.

tether-fabric status --json
04

Run one qualified class

Eligible commands use tether --auto. Local fallback stays on if a peer is missing or slower.

tether --auto python3 xover_par.py

Current pair grammar

Invite lines start with tether-invite-v1. and are never put in a URL or query string. Same-store second import is refused as already used. The Mac app runs these; this page only prints them.

  • tether-fabric pair create PEER_ID --display-name NAME --json --invite
  • tether-fabric pair import PEER_ID --invite CODE
  • tether-fabric pair import PEER_ID --key-file PATH --display-name NAME
  • tether-fabric ingest PATH
  • tether-fabric revoke PEER_ID WORKLOAD_CLASS --reason TEXT
What ships, what does not

Owned hardware. Signed receipts. Fail local.

Tether is built to borrow CPU, GPU, and RAM from machines you already control. The fabric is local. There is no cloud control plane and no account to create. Broader workload coverage is still gated by per-class evidence, not by this page.

Measured auto placement

Qualified work goes through tether --auto. Placement needs signed receipts and a never-regress record. Unknown classes stay local.

Local pairing only

Traffic stays on hardware you control. Tether does not phone home. There is no account auth surface. Pairing is tether-fabric pair.

Shims are not product-ready

Adapter modules exist in-tree. tether doctor is still NOT_READY with 0/14 gates, including interception and promotion. Do not treat adapter names as shipped coverage.

Measured, not claimed

Numbers on this page cite a matrix snapshot or a named generation. The dashboard shows live gate status from a collector snapshot. No marketing multipliers.

Fail-closed fallback

If a peer drops, a receipt expires, or kill-switch is on, work returns local. The first Mac class already exercised expiry and disconnect fallback.

Protocol is not product parity

Darwin, Windows, and Linux probes have test coverage. Real Windows/Linux acceptance and GPU scheduling remain open gates.

Availability

Mac technical gate passed. User alpha is not.

Current proof is narrow: a macOS controller, an authorized Mac peer, and an exact qualified parallel Python class. Everything else is a listed gate, not a shipped feature.

Verified on owned Macs

  • macOS checkout CLI and clean wheel
  • Signed pairing, capacity, qualification, and execution receipts
  • Fail-local and exactly-once safety contracts
  • First Mac workload class, generation 20260901T081436Z

Measured workload

  • Exact python3 xover_par.py class
  • One legacy adopted-auto Mac peer win
  • Broader commands remain local unless independently qualified

Still blocked or unbuilt

  • Windows and Linux real-host parity
  • Consumer installer, updater, and notarized app
  • doctor READY, GPU scheduling, billing, telemetry, GA
Get the bits

Public feed host, no published envelope

Updates are meant to come from the public feed host hbozok-US/tether-updates, asset releases/latest/download/stable.json. This page is a static export: it does not fetch that host at run time and it does not load a CDN script. The row below is a commit-time measurement, not a live probe.

Signed stable.json snapshot

Feed host
hbozok-US/tether-updates
Asset
releases/latest/download/stable.json
Fetched
2026-09-10T10:47Z
HTTP
404
Envelope sha256
unknown

MEASURED: the latest/download alias returned HTTP 404. There is no signed tether.update-feed.v1 envelope to show. A nine-byte “Not Found” body is not a feed sha.

Mac

local-unsigned lane only until Developer ID

Asset on public feed: none

Linux

archive when a signed feed exists

Asset on public feed: none

Windows

not yet

Asset on public feed: none

Use the ENGINEERING PREVIEW from checkout

Build the clean wheel or the local-unsigned Mac app, then pair from Tether Status → Pairing. The public feed host is hbozok-US/tether-updates; signed stable.json sha256 is unknown until a release exists.

How pairing works Read readiness matrix