docs: mark samples/eve-browser-network as needing a sibling Eve checkout #23

Merged
libby merged 1 commit from libby/docs-eve-sample-sibling into main 2026-11-07 11:40:51 +00:00
4 changed files with 10 additions and 4 deletions

View file

@ -98,7 +98,8 @@ start with the maintained
series. Its first executable package-consumer checkpoint is
[`samples/eve-two-runtime`](samples/eve-two-runtime/README.md).
The real-process browser continuation is
[`samples/eve-browser-network`](samples/eve-browser-network/README.md).
[`samples/eve-browser-network`](samples/eve-browser-network/README.md); it
needs a sibling Eve checkout (`--eve-root`) and is not in `CultLib.sln`.
One documented command runs both layers:
```powershell

View file

@ -12,7 +12,9 @@ over binary loopback CultNet WebSocket routes under an explicit
`local-development` trust policy. It proves one canonical
command effect, idempotent retry, shared observation, provider restart on a new
physical route, browser rediscovery, retained lease resubscription, and a second
canonical command after reconnection.
canonical command after reconnection. Running the sample needs a sibling Eve
checkout (`--eve-root`); it is not part of `CultLib.sln` and does not build
standalone.
The current substrate has a browser client boundary and local live proof, but
not a complete public Verse proof:

View file

@ -135,7 +135,9 @@ does **not** prove the network layer; the second program owns that evidence.
The network program is
[`samples/eve-browser-network`](../../../../samples/eve-browser-network/README.md).
Run it separately only while diagnosing that layer. A smoke against the
Running it needs a sibling Eve checkout (`--eve-root`); it is not part of
`CultLib.sln` and does not build standalone. Run it separately only while
diagnosing that layer. A smoke against the
deployed Odin daemon remains a separate infrastructure gate. Its owner map
and full acceptance contract are recorded in
[`browser-verse-transport.md`](../browser-verse-transport.md).

View file

@ -58,7 +58,8 @@ source-tree fallbacks into application code.
The process harness lives in
[`samples/eve-browser-network`](../../../../samples/eve-browser-network/README.md).
Application code should copy the typed state, operation, and Eve composition
Running it needs a sibling Eve checkout (`--eve-root`); it does not build
standalone. Application code should copy the typed state, operation, and Eve composition
shape—not its benchmark flags or fixture orchestration.
For a TypeScript provider daemon, continue with the