docs: publish the Tandem protocol dossier and enable the public site

.github/CODEOWNERS

@@ -1,6 +1,6 @@
 * @migberto
 
-# Canonical public contract changes require explicit maintainer review.
+# Public contract changes require explicit maintainer review.
 /tandem.md @migberto
 /release/ @migberto
 /schemas/ @migberto

CODE_OF_CONDUCT.md

@@ -14,6 +14,6 @@ This standard applies in repository discussions, reviews, issue threads, communi
 
 ## Reporting conduct concerns
 
-Report conduct concerns privately through [GitHub private vulnerability reporting](https://github.com/bitcoinuniverse/tandem/security/advisories/new). Begin the title with `Conduct report:` so maintainers can route it correctly. Security vulnerabilities must use the same private reporting route and should begin with `Security report:`.
+Report conduct concerns privately through [GitHub private vulnerability reporting](https://github.com/bitcoinuniverseio/tandem/security/advisories/new). Begin the title with `Conduct report:` so maintainers can route it correctly. Security vulnerabilities must use the same private reporting route and should begin with `Security report:`.
 
 Maintainers may remove content, restrict participation, or take other proportionate action to protect the community. Reports will be handled with care for privacy and due process.

README.md

@@ -4,6 +4,8 @@ Tandem is one Bitcoin-native object controlled by two people. A pair can create
 
 This repository is the public home of Tandem. It contains the product experience, user and integration documentation, and the exact public protocol artifacts needed for independent inspection.
 
+The published site is <https://bitcoinuniverseio.github.io/tandem/>.
+
 > Mainnet is not active. The protocol is finalized, but activation remains closed until independent verification, recovery, security, signer, and operational gates are complete.
 
 Public-boundary verification runs on the shared capacity-routed runner pool, so qualified self-hosted workers are used first and overflow is absorbed on ephemeral cloud capacity. Fork pull requests remain excluded from private self-hosted execution.
@@ -27,6 +29,21 @@ Then visit `http://127.0.0.1:4173`.
 
 The interactive object journey is explanatory. It does not create, sign, or broadcast Bitcoin transactions.
 
+## Protocol dossier
+
+The dossier is the technical layer: the specification restated as numbered, citable rules, worked examples that use the published vectors, and an in-browser pairing verifier.
+
+- [Dossier overview](docs/protocol.html)
+- [Normative specification as numbered rules](docs/specification.html)
+- [Guide and worked examples](docs/guide.html)
+- [Pair check tool](docs/pair-check.html)
+- [Indexer semantics](docs/indexing.html)
+- [JSON Schema reference](docs/schemas.html)
+- [Test vectors](docs/vectors.html)
+- [Independent verifier](docs/verifier.html)
+- [Conformance and implementation checklist](docs/conformance.html)
+- [Security, limitations, and changelog](docs/considerations.html)
+
 ## Start with the right guide
 
 - [What is Tandem?](docs/what-is-tandem.md)
@@ -46,7 +63,7 @@ The exact public contract is indexed in [protocol/README.md](protocol/README.md)
 
 Product copy, accessibility, public documentation, examples, and safe public integrations are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) and [REPOSITORY_BOUNDARY.md](REPOSITORY_BOUNDARY.md) before opening a change.
 
-Report security concerns privately through [GitHub private vulnerability reporting](https://github.com/bitcoinuniverse/tandem/security/advisories/new). Do not place sensitive details in a public issue.
+Report security concerns privately through [GitHub private vulnerability reporting](https://github.com/bitcoinuniverseio/tandem/security/advisories/new). Do not place sensitive details in a public issue.
 
 ## License
 

SECURITY.md

@@ -4,7 +4,7 @@ Tandem involves Bitcoin transactions, shared control, recovery paths, and indepe
 
 ## Report privately
 
-Use [GitHub private vulnerability reporting](https://github.com/bitcoinuniverse/tandem/security/advisories/new) for suspected vulnerabilities.
+Use [GitHub private vulnerability reporting](https://github.com/bitcoinuniverseio/tandem/security/advisories/new) for suspected vulnerabilities.
 
 Do not open a public issue for a suspected vulnerability. Do not include seed phrases, private keys, wallet backups, production credentials, access tokens, personally identifying wallet data, or unrelated transaction history in any report.