From 1912f2cb453b6a15d3376a7f490d0faa8ee724d3 Mon Sep 17 00:00:00 2001 From: Julian Matschinske Date: Wed, 7 Oct 2026 23:52:52 +0200 Subject: [PATCH] docs: record the verified hydrated release --- docs/COMPOSITION.md | 16 +++++++++------- hydrated/README.md | 26 +++++++++++++++++++++++++- 2 files changed, 34 insertions(+), 8 deletions(-) diff --git a/docs/COMPOSITION.md b/docs/COMPOSITION.md index 9df7da2..ba6035b 100644 --- a/docs/COMPOSITION.md +++ b/docs/COMPOSITION.md @@ -1,12 +1,14 @@ # Runtime composition plan -**Status, 7 October 2026:** implementation plan. Its exported-Wire facility is -implemented in bitruntime 0.7.0 as the hydrated layer; routing, multiplexing and -the stream carrier remain planned, with no runtime code or API. -The released baseline is bitruntime 0.6.0 with bitwire 0.5.0. The current -[realization record](WIRE-RUNTIME.md) describes that implementation. bitruntime -0.7.0, with bitwire 0.6.0, adds the hydrated layer (`hydrated/{go,ts}`), which -realizes the exported-Wire facility as bitwire decision 0019. The +**Status, 7 October 2026:** the published release is bitruntime 0.7.1 with +bitwire 0.6.0. Its hydrated layer (`hydrated/{go,ts}`) realizes the exported-Wire +facility as bitwire decision 0019. Routing, multiplexing and the stream carrier +remain planned here, with no reusable runtime code or API. +The [baseline realization record](WIRE-RUNTIME.md) describes the earlier +bitruntime 0.6.0 / bitwire 0.5.0 foundation. The hydrated implementation first +landed in 0.7.0; 0.7.1 fixes its release consumer check and supplies the verified +public package. [The hydrated realization](../hydrated/README.md#public-release-evidence) +records the delivered revision and public consumer evidence. The [bitwire composition architecture](https://github.com/Bitspark/bitwire/blob/main/docs/wire/composition.md) owns the target semantics and acceptance obligations; this page owns how bitruntime should realize them. Future protocol records must settle the pending diff --git a/hydrated/README.md b/hydrated/README.md index 3c1f225..9577d70 100644 --- a/hydrated/README.md +++ b/hydrated/README.md @@ -2,7 +2,8 @@ **Status, 7 October 2026:** the realization of bitwire decision 0019, the hydrated wire protocol's first edition, accepted at bitwire `5b1de82`, for bitruntime -0.7.0. It implements bitwire 0.6.0's public hydrated declarations +0.7.1 (first implemented in 0.7.0). It implements bitwire 0.6.0's public hydrated +declarations (`HydratedValue`, `HydratedWire`, `HydratedEndpoint`, `ReceivedContext`) and encodes and decodes through bitwire's shared pure hydrated codec, which owns the grammar and its bounds. No private copy of either remains here. @@ -34,3 +35,26 @@ reply lifetimes, over both carriers. The record's vectors are copied from bitwire `5b1de82` into [testdata](go/testdata/hydrated-vectors.json), pinned by sha256; both languages replay them. + +## Public release evidence + +[bitruntime v0.7.1](https://github.com/Bitspark/bitruntime/releases/tag/v0.7.1) +is published at `583174d1b2e3cc3916c363dee9fb9d1cbbeedf55`, using public +bitwire 0.6.0. [The release run](https://github.com/Bitspark/bitruntime/actions/runs/37691354522) +passed, including the fresh public Go module consumer. Its TypeScript package +is the GitHub release asset `bitspark-bitruntime-0.7.1.tgz`. + +An independent download matched the published `SHA256SUMS` entry: +`78e0ce694162cecc5b6f0ff503df91631dadb12ea97915af2848fd1637db5f0d`. +A fresh consumer installed that asset and public bitwire 0.6.0 and passed the +local-pair, tree, WebSocket and hydrated-reply checks +([receipt](https://github.com/Bitspark/bitruntime/pull/45#issuecomment-6047570121)). +The independent reviewer also ran all 15 composition cases against those actual +public packages ([receipt](https://github.com/Bitspark/bitruntime/pull/45#issuecomment-6047513997)). + +The 0.7.0 tag remains historical: its Go module is public, but its release +consumer check failed before a GitHub release or TypeScript asset was published. +Version 0.7.1 repairs the Linux smoke-program output path; the hydrated library +implementation is unchanged. This evidence establishes the shared hydration +layer over local pairs and WebSocket, including the test router used by its +composition cases. It does not establish a deployed bitnode network.