docs(concepts): Market Lifecycle — explicit close/suspend signal map (all 4 locales)#263
Open
paperclip-resolver[bot] wants to merge 1 commit into
Open
docs(concepts): Market Lifecycle — explicit close/suspend signal map (all 4 locales)#263paperclip-resolver[bot] wants to merge 1 commit into
paperclip-resolver[bot] wants to merge 1 commit into
Conversation
…gnal map (all 4 locales) New concepts page consolidating every market close/suspend/removal signal (odds:removed, delta removed[], is_active, odds:locked, is_stale_pregame_price) with the threshold-ladder churn model and client cleanup recipes. Documents the previously-unshown removed[] array in the odds-delta reference and cross-links the live-vs-prematch suspension callout. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Crew task #380 / SHA-3694 (reopened over customer churn). A Sharp+WS customer asked how to detect Pinnacle handicap/totals markets closing ("threshold-point market disappears — residual data stays in our system"), was told on 2026-05-26 to diff snapshots client-side, and churned on 2026-06-09 believing there is no close signal. The explicit signals already exist —
odds:removed(WS/SSE) and deltaremoved[]predate the report, andis_active/odds:lockedshipped 2026-05-31 (SHA-3803) — but they were scattered across four reference pages with no consolidated answer to "how do I know a market closed?", and the delta reference referencedremoved[]without ever showing it.Decision (ask 1 of the task): keep the contract — no synthetic adapter-side "closed" price row. Ladder markets were explicitly excluded from synthetic suspension in the 2026-05-31 red-team design (~98% of removals are ephemeral alt-line churn; a synthetic terminal row would be wrong as often as right, and we never fabricate rows a book didn't post). This PR executes ask 3: make the existing signals discoverable.
What
market-lifecycle(all 4 locales): removal vs suspension-in-place, signal matrix per surface (REST snapshot / delta / SSE / WS), threshold-ladder churn model for handicaps + totals (the churned customer's exact case), stable-id semantics, client cleanup recipes,is_active+is_stale_pregame_priceguards.removed[]array ({id, sportsbook, removed_at}) — previously referenced by two callouts but never shown.Verification
npm run buildgreen in the worktree: 228 pages indexed across 4 locales (224 before — the 4 new pages),out/<locale>/concepts/market-lifecycle/present for all locales.removed[]shape fromsharp-api-go/main.go(removedOddstruct), odds-id stability fromapi-adapters/adapters/base.py_numeric_id(48-bit xxhash of book/event/market+line/selection), live numeric ids + per-rung distinctness confirmed againstlocalhost:3003 /api/v1/oddson OVH.public/artifacts (sitemap, openapi stamps) deliberately excluded — the deploy build regenerates them.Type: docs
🤖 Generated with Claude Code