The box is coming. The software is here.

The shortest honest path. It builds the Core and the dashboard from a checkout, keeps data in a folder you can delete, keeps the household key in that folder rather than your Keychain, and runs in the foreground until you press Ctrl-C. Nothing is installed system-wide and no login service is created.

git clone https://github.com/tars16775/woven.git
cd woven
packaging/try.sh --seed

Then open http://localhost:4002. With --seed there is a demo household to look around; without it you make your own house in about a minute: a name, your name, a passkey with Touch ID, and recovery codes to write down.

When you want it to stay running: this fetches Node and the newest release into a folder of its own, installs a login service, and opens the setup page. Your data goes to ~/Library/Application Support/Woven unless you point it elsewhere.

curl -fsSL https://raw.githubusercontent.com/tars16775/woven/main/packaging/install.sh | bash

The installer verifies the release signature before it uses anything from it, and woven update keeps the previous release and rolls back on its own if a new one does not start.¹⁶ Until the first signed release is published this path needs a checkout; the section above works today.

Every line here is built, tested and checkable on your own machine.

• Passkeys, per-person spaces and roles⁴
• Nightly snapshots, a second copy, and a restore you can rehearse⁸
• Search your files, memory and routines on the box⁹
• Search photos by what is in them, on the box⁵
• Nothing leaves without a crossing you approved, and every crossing is recorded¹
• Every consequential action leaves a receipt in a ledger that cannot be edited quietly²
• Everything on the drive is encrypted at rest³
• Reach your house from anywhere with no open ports⁶
• One switch stops everything⁷

None of this is in the software yet, and the dashboard says so on the screen where you would expect to find it rather than showing you a picture of it.

• Matter, Thread and Zigbee radios, with devices answering in under a second¹⁰
• Cameras with detection on the box and clips that never leave¹¹
• The router runs on its own processor that cannot see inside¹²
• Tandem answers from the household's own files, calendar and home¹³
• Speech and the wake word are processed on the box¹⁴
• Agents run sandboxed, as themselves, with scoped credentials¹⁵

When the box arrives the household moves with a snapshot: same core, same data, same receipts.

Any other Mac in the house can back folders up to your Core with a small client and a token you make under Settings, Backup devices. It hashes what changed and sends only bytes the box does not already hold, over the household certificate.

curl -fsSL https://raw.githubusercontent.com/tars16775/woven/main/packaging/install.sh | bash -s -- --client
woven-backup connect https://woven.local:4000 <token from Settings>
woven-backup run ~/Documents --watch     # --into and --namespace choose where

Your Mac keeps no open ports. Set a relay address and the Core holds one outbound connection to it; a browser you paired at home reaches the house from anywhere, with every frame encrypted end to end under a key only that browser and the Core hold. The relay carries ciphertext and keeps nothing.⁶ Pairing happens at home only, and any paired device can be revoked.

# in woven config, then: woven restart
WOVEN_RELAY="wss://your-relay.example.com"

woven status      # running, where, how much space
woven logs        # follow the core
woven stop        # and start, restart
woven config      # data folder, ports, the second backup location, the relay
woven update      # the newest signed release; rolls back on its own if it does not start
woven rollback    # back to the release that ran before
woven uninstall   # removes the program; your data stays

There is also a switch in the dashboard.⁷ Off closes the Gate, drops the relay, stops every scheduled job and refuses every request but the switch itself, and it stays off across a restart.