Repository navigation
feat(debates): derive readiness from claim responses - #2113
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Broadcast confirmed claim responses through geo-chat, refresh the active batched response cache across clients, and keep every visible claim interactive while its debate snapshot hydrates.
This branch was successfully deployed
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
1 participant
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.
Summary
Together with geo-chat PR #34 and geo-sdk PR #110, this replaces client-selected debate sides with positions derived from active on-chain claim responses. Claims use Agree/Disagree when non-factual or unset and Verify/Dispute when factual. Non-claim entities continue to use Upvote/Downvote.
Debate readiness remains backend state. The UI offers readiness only after Gaia indexes an active response, and it never sends a position to geo-chat. All current and historical debate presentation uses semantic response labels; there is no Yes/No fallback or feature-disabled state.
Related
Validation
cd apps/web && bun run test: 200 files and 2064 tests passed.bunx tsc --noEmit: passed.bun run lint: 0 errors; 93 existing warnings remain.git diff --check: passed.bun run builddid not complete locally because the Turbopack build stopped producing output. The webpack fallback cannot run whileexperimental.turbopackRustReactCompileris enabled, so CI remains the production-build gate.Monitoring
After deployment, watch client error telemetry and response-indexing timeouts. Verify that users never see a readiness toggle before an indexed response or a Yes/No position label.