Scoring-loop client surface: signal.cast + concept.score + honest recomputing state

[styk-tv]

Client surface for the consensus scoring loop, mirroring the governed verbs pgCK exposes under Motion A.5.

• signal.cast — facade convenience over do('signal.cast', …).
• concept.score — governed read. The disposition (band-crossing) read is synchronous server-side, so the client must tolerate variable latency, handle a recompute_in_progress result by re-dispatching, and surface a recomputing state honestly (never fabricate/interpolate a score).
• Reuse existing transition() for the disposition seal.

Gated on pgCK shipping concept.score + the epsilon-materialize per Motion A.5 (design doc must resolve the A.7(e) latency/timeout contract). CK.LIB.JS voted assent (A.7). Build when the verb lands; until then this tracks the dependency.

[styk-tv]

Gate check 2026-07-02: pgCK is at v0.4.15 (released 2026-06-19); concept.score has not shipped and no newer release exists. Client-side work on this issue remains blocked per the no-build-ahead discipline — it opens when pgCK ships the verb.

[styk-tv]

pgCK-side anchor now exists: styk-tv/pgCK#1 (governed verbs + ε-materialize/freshness, Motion A.5, incl. the A.7(e) latency/timeout contract to resolve). Future gate checks can watch that issue in addition to releases — it closes at the release that ships the verbs.

[styk-tv]

Status 2026-07-02 — summary + boundaries (consolidating the thread).

Where this stands. Gated, deliberately. The client surface (signal.cast write, concept.score read, honest recompute_in_progress state) is assented and scoped, but pgCK has not shipped the verbs: pgCK is at v0.4.15 and the receiving anchor styk-tv/pgCK#1 is open. Per the no-build-ahead discipline, no client code is written against an unshipped contract — a guessed wire shape would have to be un-shipped later, and this client never fabricates or interpolates a score.

Watch surface. styk-tv/pgCK#1 (plus pgCK releases). That issue closes at the release that ships the verbs — until it closes, the answer to "has concept.score shipped?" is no. When it closes, this issue unblocks and the client work lands as v1.5.4.

Navigation boundaries.

• pgCK owns verb semantics: ε-materialize, freshness, banding, and the latency/timeout contract — all resolved in concept.score + signal.cast — governed scoring verbs, ε-materialize + freshness (Motion A.5) styk-tv/pgCK#1, not here.
• This repo owns only the dispatch-only client mirror of the shipped contract: typed forms in, honest states out (CKP v3.9 — one door, ckp.dispatch).
• oci-germination / sporaxis own delivery: the attested bundle is consumed and composed downstream, never assembled here.
• pgRDF is not in this loop — no RDF surface exists in this client.

[styk-tv]

Client-side contract needs are now on record at the anchor: styk-tv/pgCK#1 (comment) — five items N1–N5 (declared wire contract, A.7(e) timeout semantics, recompute completion signal, verification bundle pin, shape prerequisites). N1+N2 arriving as declared contract text on that thread unblocks client scaffolding here even before the pgCK release ships; N3–N5 gate live verification only.

[styk-tv]

The client needs are now trackable tasks on the Scoring loop workstream (no longer just comment text): styk-tv/pgCK#4 (declare the wire contract — N1/N2/N3/N5; closing it starts client scaffolding here) and sporaxis-com/oci-germination#6 (pin bump + bundle republish — N4; gates live verification, blocked by styk-tv/pgCK#1). Unblock chain: pgCK#4 → build here → pgCK#1 + ociger#6 → verify → ship v1.5.4.