Validate Eve getting-started contracts

This commit is contained in:
Meta Vens 2026-08-17 23:18:15 +02:00
commit 54e4eacd13
7 changed files with 143 additions and 32 deletions

View file

@ -12,15 +12,20 @@ using var mesh = new CultMeshClient(new CultMeshClientOptions
RendezvousEndpoints = new[] { "rudp://odin.gamecult.net:3076" }
});
using var pilotSurfaceLease = await mesh.LeaseDocumentAsync<EveSurfaceDocument>(
"aetheria.daemon",
"eve:surface:aetheria.pilot",
using var counterLease = await mesh.LeaseDocumentAsync<CounterState>(
"sample.counter-provider",
"counter:main",
cancellationToken);
var pilotSurface = pilotSurfaceLease.Handle;
var counter = counterLease.Handle;
using var surfaceWatch = pilotSurface.Watch().Subscribe(Render);
using var counterWatch = counter.Watch(value =>
Console.WriteLine($"Count: {value.Count}"));
```
`CounterState` is the application document from chapter 1. Eve documents enter
in chapter 3, where the sample installs the renderer-neutral Eve contract
package explicitly. This identity/session API does not depend on a UI runtime.
Keep `mesh` for the application lifetime and dispose each document lease when
the consuming screen or system closes. Leases for the same identity share one
subscription. The document handle is stable while leased: when

View file

@ -35,7 +35,7 @@ Run the same provider and connect at least two lowerers. Both must report the
same provider id, surface id, surface version, and command receipt ids. Native
pixels may differ; provider truth may not.
The package-artifact browser/headless checkpoint is executable from CultLib:
The package-artifact DOM-lowerer/headless checkpoint is executable from CultLib:
```powershell
cd CultLib
@ -43,14 +43,16 @@ powershell -ExecutionPolicy Bypass -File .\scripts\verify-eve-two-runtime-sample
-EveRoot ..\Eve
```
The verifier builds and packs `cultcache-ts`, `cultnet-ts`, `cultmesh-ts`, and
`@gamecult/eve-browser-lowering`, installs the tarballs into an empty temporary
consumer, and runs `samples/eve-two-runtime/sample.mjs`. One provider-owned
counter surface is lowered by a browser runtime and observed by a headless
runtime. A browser command crosses the typed operation boundary, both runtimes
converge on the same state and receipt identity, a duplicate idempotency key is
not applied twice, and the state plus receipt survive reopening the `.ccmp`
store.
The verifier builds and packs `cultcache-ts`, `cultnet-ts`, `cultmesh-ts`,
`@gamecult/eve-contracts`, and `@gamecult/eve-browser-lowering`, installs the
tarballs into an empty temporary consumer, and runs
`samples/eve-two-runtime/sample.mjs`. Eve's generated runtime validators reject
an invalid surface or receipt before either enters the store. One provider-owned
counter surface is lowered into a jsdom DOM host and observed by an independent
headless CultMesh observer. A DOM command crosses the typed operation boundary,
both consumers converge on the same state and canonical receipt identity, a
duplicate idempotency key is not applied twice, and the state plus receipt
survive reopening the `.cc` store.
Current verification for the Unity consumer remains:
@ -59,7 +61,9 @@ cd E:\Projects\EveUnity
powershell -ExecutionPolicy Bypass -File .\scripts\run-release-consumer-tests.ps1
```
This checkpoint proves clean package consumption and two lowering/observation
runtimes. It does not claim an Odin-discovered network hop or cross-language
command execution; those remain separate public Verse conformance gates.
This checkpoint proves clean package consumption, canonical Eve contract
validation, and two independent lowering/observation consumers inside Node. It
does **not** claim a real browser process, an Odin-discovered network hop, or
cross-language command execution. Those are the next public Verse conformance
gates; do not cite this sample as evidence that they exist.

View file

@ -4,6 +4,18 @@ This series builds one typed application state and presents it through multiple
Eve runtimes. It is maintained as an API acceptance test: examples use public
APIs, name the owner of each decision, and include a verification checkpoint.
Run the current clean-consumer checkpoint first:
```powershell
powershell -ExecutionPolicy Bypass -File .\scripts\verify-eve-two-runtime-sample.ps1 `
-EveRoot ..\Eve
```
It installs packed artifacts into an empty temporary project, validates the Eve
surface and receipt, executes one idempotent counter command, proves two local
consumers converge, and reopens the durable `.cc` store. It is deliberately not
called a networked-browser proof; chapter 3 names that remaining boundary.
Follow the chapters in order:
1. [Persist typed application state](01-persist-typed-state.md)