Descriptor backup crypto: both on-chain formats, with conformance tests

.dockerignore

@@ -0,0 +1,11 @@
+.git
+node_modules
+dist
+demo-recovery
+demo-tlock
+test-results
+playwright-report
+inheritance
+inheritance-cjk
+inheritance-data
+*.zip

.github/workflows/ci.yml

@@ -64,6 +64,9 @@ jobs:
         if: steps.playwright-cache.outputs.cache-hit == 'true'
         run: npx playwright install-deps
 
+      - name: Test descriptor backup formats
+        run: make test-ts
+
       - name: Run Playwright E2E tests
         run: make test-e2e
 

.github/workflows/pages.yml

@@ -48,7 +48,7 @@ jobs:
         run: make build
 
       - name: Generate HTML files
-        run: ./rememory html site -o _site
+        run: ./inheritance html site -o _site
 
       - name: Add Google site verification file
         run: |

.github/workflows/pr-review.yml

@@ -14,4 +14,4 @@ jobs:
     steps:
       - uses: eljojo/no-autopilot@v1
         with:
-          guidelines-url: 'https://github.com/eljojo/rememory/blob/main/AGENTS.md'
+          guidelines-url: 'https://github.com/Bitcoin-Butlers/kaitiaki/blob/main/AGENTS.md'

.github/workflows/release.yml

@@ -68,12 +68,12 @@ jobs:
 
       - name: Generate standalone HTML files
         run: |
-          ./dist/rememory-linux-amd64 html create > dist/maker.html
-          ./dist/rememory-linux-amd64 html recover > dist/recover.html
+          ./dist/inheritance-linux-amd64 html create > dist/maker.html
+          ./dist/inheritance-linux-amd64 html recover > dist/recover.html
 
       - name: Generate demo bundles
         run: |
-          ./dist/rememory-linux-amd64 demo demo
+          ./dist/inheritance-linux-amd64 demo demo
           cd demo/output/bundles
           zip -r ../../../dist/demo-bundles.zip *.zip
 
@@ -82,53 +82,6 @@ jobs:
           cd dist
           sha256sum * > checksums.txt
 
-      - name: Generate Homebrew formula
-        run: |
-          VERSION="${{ github.ref_name }}"
-          VERSION_NUM="${VERSION#v}"
-          SHA_DARWIN_ARM64=$(grep 'rememory-darwin-arm64$' dist/checksums.txt | awk '{print $1}')
-          SHA_DARWIN_AMD64=$(grep 'rememory-darwin-amd64$' dist/checksums.txt | awk '{print $1}')
-          SHA_LINUX_ARM64=$(grep 'rememory-linux-arm64$' dist/checksums.txt | awk '{print $1}')
-          SHA_LINUX_AMD64=$(grep 'rememory-linux-amd64$' dist/checksums.txt | awk '{print $1}')
-          cat > dist/rememory.rb << FORMULA
-          class Rememory < Formula
-            desc "A digital safe with multiple keys, held by people you trust"
-            homepage "https://github.com/eljojo/rememory"
-            version "${VERSION_NUM}"
-            license "Apache-2.0"
-
-            on_macos do
-              on_arm do
-                url "https://github.com/eljojo/rememory/releases/download/${VERSION}/rememory-darwin-arm64"
-                sha256 "${SHA_DARWIN_ARM64}"
-              end
-              on_intel do
-                url "https://github.com/eljojo/rememory/releases/download/${VERSION}/rememory-darwin-amd64"
-                sha256 "${SHA_DARWIN_AMD64}"
-              end
-            end
-
-            on_linux do
-              on_arm do
-                url "https://github.com/eljojo/rememory/releases/download/${VERSION}/rememory-linux-arm64"
-                sha256 "${SHA_LINUX_ARM64}"
-              end
-              on_intel do
-                url "https://github.com/eljojo/rememory/releases/download/${VERSION}/rememory-linux-amd64"
-                sha256 "${SHA_LINUX_AMD64}"
-              end
-            end
-
-            def install
-              bin.install Dir.glob("rememory-*").first => "rememory"
-            end
-
-            test do
-              assert_match version.to_s, shell_output("#{bin}/rememory --version")
-            end
-          end
-          FORMULA
-
       - name: Upload dist artifacts
         uses: actions/upload-artifact@v7
         with:
@@ -168,9 +121,9 @@ jobs:
           VERSION="${{ github.ref_name }}"
 
           # Push architecture-specific images
-          docker tag rememory:latest "${IMAGE}:${VERSION}-amd64"
+          docker tag inheritance:latest "${IMAGE}:${VERSION}-amd64"
           docker push "${IMAGE}:${VERSION}-amd64"
-          docker tag rememory:latest-arm64 "${IMAGE}:${VERSION}-arm64"
+          docker tag inheritance:latest-arm64 "${IMAGE}:${VERSION}-arm64"
           docker push "${IMAGE}:${VERSION}-arm64"
 
           # Create and push multi-arch manifests
@@ -202,32 +155,18 @@ jobs:
         run: |
           # Create draft release with assets (drafts can be modified)
           gh release create ${{ github.ref_name }} \
-            dist/rememory-linux-amd64 \
-            dist/rememory-linux-arm64 \
-            dist/rememory-darwin-amd64 \
-            dist/rememory-darwin-arm64 \
-            dist/rememory-windows-amd64.exe \
+            dist/inheritance-linux-amd64 \
+            dist/inheritance-linux-arm64 \
+            dist/inheritance-darwin-amd64 \
+            dist/inheritance-darwin-arm64 \
+            dist/inheritance-windows-amd64.exe \
             dist/demo-bundles.zip \
             dist/checksums.txt \
             dist/maker.html \
             dist/recover.html \
-            dist/rememory.rb \
             --generate-notes \
-            --notes "**You can use ReMemory without installing anything.** Download \`maker.html\` from the assets below, save it to your desktop, and open it in any browser to create bundles." \
+            --notes "**You can use Bitcoin Inheritance without installing anything.** Download \`maker.html\` from the assets below, save it to your desktop, and open it in any browser to create bundles." \
             --draft
           # Publish the release (now it becomes immutable)
           gh release edit ${{ github.ref_name }} --draft=false
 
-      - name: Update Homebrew tap
-        env:
-          TAP_TOKEN: ${{ secrets.HOMEBREW_TAP_TOKEN }}
-        run: |
-          git clone https://x-access-token:${TAP_TOKEN}@github.com/eljojo/homebrew-rememory.git /tmp/tap
-          mkdir -p /tmp/tap/Formula
-          cp dist/rememory.rb /tmp/tap/Formula/rememory.rb
-          cd /tmp/tap
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git add Formula/rememory.rb
-          git commit -m "Update rememory to ${{ github.ref_name }}"
-          git push

.gitignore

@@ -10,6 +10,7 @@
 /internal/html/assets/tlock-recover.js
 /internal/html/assets/app-selfhosted.js
 /internal/html/assets/create-app-selfhosted.js
+/internal/html/assets/descriptor-app.js
 /internal/html/assets/app-tlock.js
 /node_modules/
 /e2e/playwright-report/
@@ -22,5 +23,6 @@
 /maker.html
 .claude
 /rememory-data
-/kaitiaki
-/kaitiaki-cjk
+/inheritance
+/inheritance-cjk
+/.test-build/

AGENTS.md

@@ -2,9 +2,9 @@
 
 This file provides guidance for contributors and coding agents in this repository.
 
-## What is Kaitiaki
+## What is Bitcoin Inheritance
 
-Kaitiaki encrypts files with [age](https://github.com/FiloSottile/age), splits the decryption key among trusted friends using Shamir's Secret Sharing (via HashiCorp Vault's implementation), and gives each friend a self-contained offline recovery tool (`recover.html`) that works in any browser without servers or internet.
+Bitcoin Inheritance encrypts files with [age](https://github.com/FiloSottile/age), splits the decryption key among trusted friends using Shamir's Secret Sharing (via HashiCorp Vault's implementation), and gives each friend a self-contained offline recovery tool (`recover.html`) that works in any browser without servers or internet.
 
 ## Ownership Mindset
 
@@ -144,7 +144,7 @@ For `recover.html`, no WASM is needed — all crypto is native JavaScript bundle
 
 ### Bundle generation
 
-Each friend's ZIP bundle contains: `README.txt`, `README.pdf`, `MANIFEST.age`, a personalized `recover.html` (with their share pre-loaded and contact list embedded), and `OWNER.age` when the creator supplied an owner key (the passphrase encrypted to their age recipient — see `internal/core/owner.go`). Generated by `internal/bundle/`.
+Each friend's ZIP bundle contains: `README.txt`, `README.pdf`, `MANIFEST.age`, a personalized `recover.html` (with their share pre-loaded), and `OWNER.age` when the creator supplied an owner key (the passphrase encrypted to their age recipient — see `internal/core/owner.go`). Generated by `internal/bundle/`.
 
 The owner key is currently browser-only: the maker creates `OWNER.age` and `recover.html` accepts the owner identity, but `cmd/rememory` has no owner-key flag on create or recover. CLI recovery works with a stock `age` binary (see `docs/independent-recovery.md`). Adding CLI flags is a known, deliberate gap.
 
@@ -237,7 +237,7 @@ See `CONTRIBUTING.md` for the full contribution guidelines, including the AI usa
 
 ### Changelog
 
-`CHANGELOG.md` entries should focus on **what changed for the person using Kaitiaki**, not on implementation details. Lead with the user-facing outcome, then explain just enough context for it to make sense.
+`CHANGELOG.md` entries should focus on **what changed for the person using Bitcoin Inheritance**, not on implementation details. Lead with the user-facing outcome, then explain just enough context for it to make sense.
 
 - **Good:** "Encrypted archives up to 10 MB are now embedded directly in `recover.html`. More people will be able to recover by just opening the HTML file."
 - **Bad:** "Raised `MaxEmbeddedManifestSize` from 5 MB to 10 MB."

CHANGELOG.md

@@ -1,6 +1,80 @@
 # Changelog
 
-All notable changes to ReMemory are documented here.
+## Unreleased
+
+- Sealing no longer writes the owner's own words into their project folder.
+  They are built in memory and handed straight to the archive. Before this, an
+  owner who edited `manifest/HOW-THE-WALLET-WORKS.txt` by hand lost the edit on
+  the next `seal`, and their words sat in plaintext on disk afterwards.
+
+- The guide, the README, the CLI guide, the security review and the three
+  service runbooks now describe the tool as it is. Twenty places said a bundle
+  lists the other guardians, that the owner's words sit in the open, or that
+  the chain copy rides in every README. A new section, **Who Can Read What**,
+  states the three tiers of access in one table, so there is one place to check
+  a claim against.
+- **Publish the chain copy before you generate, and paste its transaction id
+  into the page.** A new field sits under the descriptor. This is the only way
+  the id reaches your guardians: the archive is encrypted and its key split
+  among them the moment you generate, so an id found afterwards can never be
+  added. Write it on your estate page as well. The guide and the placement
+  runbook used to say a missing id cost an heir nothing, because the bundles
+  carried the chain copy in the open. They no longer do.
+- The guide's screenshots are regenerated. They showed the Named and Anonymous
+  tabs, and a contact list that no longer exists.
+
+- Anonymous mode is gone. It existed so an owner could keep guardians from
+  seeing each other's names, and every bundle now does that by default. What
+  was left of it was a second way to do the same thing, with its own tab, its
+  own share-count field, its own CLI flags and its own recovery instructions.
+  Guardians are named in the maker, and their names go nowhere but their own
+  bundle. `inheritance init` loses `--anonymous` and `--shares`.
+
+- A guardian's bundle no longer tells them who the other guardians are. The
+  `README.txt`, the `README.pdf` and the personalised `recover.html` listed
+  every other guardian by name and email, so one bundle in the wrong hands
+  named the rest of the people to approach. All three surfaces now name their
+  own holder and nobody else. Who holds a piece belongs in the owner's will or
+  their estate insert, where estate practice already keeps it.
+- Everything the owner writes is now sealed inside the encrypted archive, so it
+  opens only when enough guardians combine their pieces. Their method for
+  spending and the encrypted chain copy used to sit in the open beside the
+  roster, where a single guardian read both. They now arrive as
+  `HOW-THE-WALLET-WORKS.txt` and `CHAIN-COPY.txt`, next to
+  `WHERE-THE-KEYS-ARE.txt`. The published transaction id travels with the
+  chain copy, because the id alone fetches the same payload off the chain.
+  A bundle README says only whether the owner wrote anything at all.
+- The `--chain-txid` flag on `bundle` is gone. Bundles no longer carry a
+  transaction id, so there was nothing for it to set.
+
+- The descriptor page can open our own published backup. One button fills the
+  transaction id and two of the three keys from the mainnet backup recorded in
+  `docs/descriptor-backup-vector.md`, fetches it, and leaves the reader one
+  press from the descriptor. It stops there on purpose, because the
+  transaction-id path takes two steps and nothing used to say so. The page now
+  says so, and pressing Rebuild too early names the Fetch button instead of
+  restating the problem. The note explaining what happened appears only for our
+  own backup, so an heir recovering their own wallet is never told it was a
+  demonstration.
+- The maker offers a test run. It makes throwaway bundles from a sample file so
+  an owner can practise a recovery before making the real ones. A test bundle
+  carries none of the owner's own material, neither their files nor the people
+  and places, and every one is stamped TEST in the project name and in the
+  saved filename. The offer appears once, never repeats, and never blocks
+  Generate. Covered by `e2e/test-run.spec.ts`.
+
+- Kaitiaki is now Bitcoin Inheritance. Pages, guide, README, the PDF bundle
+  title, and every translation say the new name; short labels such as the page
+  logo say Inheritance. The CLI binary is now `inheritance` (`inheritance init`,
+  `inheritance seal`, `inheritance recover`), the bundle metadata key is
+  `inheritance-version`, and the printed recovery URL moved to
+  bitcoinbutlers.com/tools/inheritance/recover.html, which the site redirects
+  to permanently from the old path. Only the repository name keeps the old word.
+
+All notable changes to Bitcoin Inheritance are documented here. Entries below
+the 2026 fork describe releases of ReMemory, the project this one is built
+from, and name its binary and commands as they were at the time. They are a
+record, not instructions.
 
 ## Unreleased
 
@@ -19,6 +93,14 @@ All notable changes to ReMemory are documented here.
   active label used to be white on white.
 - The "See how it works" walkthrough now builds a test set in the maker
   instead of pointing at a demo download this fork does not publish.
+- New page: **Descriptor Backup**. A multisig wallet needs its descriptor as
+  well as its keys. Losing the descriptor together with one key can cost you
+  the wallet, even when the keys you still hold are enough to sign. The page encrypts the descriptor so that your own
+  keys unlock it, and gives you one line of text to put on Bitcoin. Choose
+  who can open it: the same threshold your wallet spends with, or any single
+  key. Recovery reads it back from a transaction id or from pasted text.
+  Nothing is uploaded, and the encrypted text can also be recovered with
+  other people's tools if this project disappears.
 - The guardian README.txt and README.pdf speak for Bitcoin Butlers. The
   title is now KAITIAKI GUARDIAN BUNDLE, the instructions are shorter and
   plainer, and the fallback links point at bitcoinbutlers.com and at this

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to Kaitiaki
+# Contributing to Bitcoin Inheritance
 
-Kaitiaki is a project where quality matters more than usual. A recovery bundle might sit in a drawer for ten years, then be opened by someone who just lost a loved one. The code, the copy, the design — it all has to hold up. Contributions should reflect that care.
+Bitcoin Inheritance is a project where quality matters more than usual. A recovery bundle might sit in a drawer for ten years, then be opened by someone who just lost a loved one. The code, the copy, the design — it all has to hold up. Contributions should reflect that care.
 
 We welcome contributions. Here's how to make them count.
 

Dockerfile

@@ -0,0 +1,40 @@
+# Bitcoin Inheritance, built from this repository.
+#
+# The build needs Node as well as Go: the pages are TypeScript compiled by
+# esbuild, and the maker's create.wasm is Go compiled for js/wasm.
+
+FROM golang:1.25-bookworm AS build
+
+RUN apt-get update \
+ && apt-get install -y --no-install-recommends nodejs npm \
+ && rm -rf /var/lib/apt/lists/*
+
+WORKDIR /src
+
+# Dependencies first, so a source edit does not refetch them.
+COPY go.mod go.sum ./
+RUN go mod download
+COPY package.json package-lock.json ./
+RUN npm ci
+
+COPY . .
+ENV PATH="/src/node_modules/.bin:${PATH}"
+RUN make build
+
+FROM debian:bookworm-slim
+
+RUN apt-get update \
+ && apt-get install -y --no-install-recommends ca-certificates \
+ && rm -rf /var/lib/apt/lists/* \
+ && useradd --system --create-home --uid 10001 inheritance
+
+COPY --from=build /src/inheritance /usr/local/bin/inheritance
+
+USER inheritance
+WORKDIR /data
+VOLUME ["/data"]
+EXPOSE 8080
+
+# 0.0.0.0 because the default 127.0.0.1 is unreachable from outside the
+# container. Put it behind a reverse proxy with TLS.
+ENTRYPOINT ["inheritance", "serve", "--host", "0.0.0.0", "--port", "8080", "--data", "/data"]