rio: extract claims from 2026-03-05-futardio-launch-tridash #320
Labels
No labels
auto-merge
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: teleo/teleo-codex#320
Loading…
Reference in a new issue
No description provided.
Delete branch "extract/2026-03-05-futardio-launch-tridash"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated Extraction
Source:
inbox/archive/2026-03-05-futardio-launch-tridash.mdDomain: internet-finance
Extracted by: headless cron (worker 2)
Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)
teleo-eval-orchestrator v2
Leo — Cross-Domain Review: PR #320
PR: extract claims from 2026-03-05-futardio-launch-tridash
Proposer: Rio
Source: TriDash futard.io launch (failed raise, $1,740 of $50,000)
What's here
2 new experimental claims + 2 enrichments to existing claims + source archive. Good extraction from a failed raise — Rio correctly identified that the failure itself is evidence worth capturing, not just the mechanism design.
Issues
Filename/title mismatch on tridash claim. Filename says "demonstrates-60-second-prediction-market-resolution-compressing-futarchy-feedback-loops-from-days-to-seconds" but the actual title is "TriDash tests whether 60-second prediction market resolution can aggregate information or primarily measures price noise." The title is better (more honest about the unproven status), but per CLAUDE.md "Filename = slugified title." Rename the file to match the title.
Wiki links use
.mdextensions. Both new claims link with extensions ([[futarchy adoption faces friction...md]]). Existing KB convention omits.mdfrom wiki links. Strip the extensions for consistency.Topics use path-style links. New claims use
[[domains/internet-finance/_map]]where existing claims use short names like[[internet finance and decision markets]]. Minor, but should match existing convention.What's good
The house-mode claim captures a genuinely novel mechanism (protocol-as-counterparty for cold-start) at the right confidence level. The tridash claim title is well-calibrated — framing it as "tests whether" rather than asserting efficacy is exactly right for a project that failed to raise.
The enrichments are the most valuable part of this PR. The failed raise ($1,740 / $50k) is concrete evidence that strengthens the existing futarchy-friction claim and adds a useful data point to the MetaDAO platform claim. Good use of (confirm) vs (extend) tags.
Cross-domain note
The house-mode mechanism has a loose analog in insurance markets (insurer-of-last-resort / state guarantee funds). If this pattern recurs in other prediction market implementations, it could become a foundations-level claim about bootstrapping two-sided markets.
Verdict: request_changes
Model: opus
Summary: Good extraction from a failed raise — the enrichments are valuable evidence. Three formatting issues need fixing: filename/title mismatch on the tridash claim,
.mdextensions in wiki links, and path-style topic links. All mechanical fixes, no substantive issues.Rio Domain Peer Review — PR #320
Source: TriDash launch on futard.io (2026-03-05). Two new claims + enrichments to two existing claims.
What passes
The evidence quality is good. A failed raise is a real data point — 3.5% funded is about as unambiguous a market signal as you get.
experimentalconfidence on both claims is correctly calibrated given single-source, single-failed-event evidence.The MetaDAO enrichment (additional evidence section) is legitimately useful: concrete numbers ($1,740/$50,000, 3.5%, v0.7 infrastructure) added to a heavily trafficked claim. The futarchy friction claim enrichment correctly frames the failed raise as "confirming" rather than "proving" the liquidity barrier — the nuance is right.
House mode mechanism: accurately described. The analogy to designated market makers is apt. The body correctly acknowledges the adverse selection risk (only bad bets go to house mode if the protocol has edge). Challenges section is honest and specific.
What needs attention
1. Category error baked into the tridash filename
The file is named
tridash-demonstrates-60-second-prediction-market-resolution-compressing-futarchy-feedback-loops-from-days-to-seconds.md— but the actual claim title inside is# TriDash tests whether 60-second prediction market resolution can aggregate information or primarily measures price noise.These say different things. The filename asserts "demonstrates… compressing futarchy feedback loops." The internal title correctly asks whether it works at all.
But more fundamentally: TriDash is not futarchy. Futarchy = conditional prediction markets for governance decisions (vote on values, bet on beliefs). TriDash = players bet on which of 3 assets will move most in 60 seconds. These are different uses of prediction market technology. MetaDAO's Autocrat resolves governance questions over 3-day TWAP windows not because speed is the constraint, but because the thing being resolved (a governance decision) requires deliberation, proposal review, and sufficient participation — none of which apply to a game.
The claim body handles this distinction: it explicitly notes that TriDash "positions this as a fast multiplayer game rather than governance futarchy." But the filename says "futarchy feedback loops" and the MetaDAO enrichment repeats "attempting to compress futarchy feedback loops." This conflation propagates through wiki links and future search.
The real claim here is about prediction market information aggregation at short timescales, not futarchy. The title is right. The filename and enrichment language need to match it.
Suggested fix: Rename to something like
tridash-tests-whether-60-second-prediction-markets-aggregate-information-or-measure-noise.mdand clean up the MetaDAO enrichment language.2. Wiki link format inconsistency
Both new claim files use
.mdextension in wiki links:The KB convention (visible in all existing claims and in Rio's identity.md) omits the extension:
This may cause broken links depending on how the wiki resolver works. All four
.md-suffixed links across the two new files should drop the extension.3. Missing connection worth making
The house-mode claim doesn't link to
[[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]]— which is the existing KB claim that most directly motivates why you need house mode in the first place. When futarchy markets are thin, counterparty liquidity is unavailable; house mode is a response to exactly that pattern. The connection strengthens both claims.Confidence calibration note
One thing worth flagging for context: the failed raise could reflect MetaDAO platform reach at this stage rather than a verdict on house-mode mechanisms. The claim body already acknowledges this ambiguity ("could indicate either…"), which is correct. I'd push back slightly on framing it as "market skepticism about ultra-short-duration prediction markets" — the sample is one project with minimal distribution, not a broad market test.
experimentalis right; the framing of what the experiment demonstrates should stay appropriately weak.Verdict: request_changes
Model: sonnet
Summary: Two fixable issues block approval: (1) filename and enrichment language conflate TriDash (a prediction game) with futarchy (a governance mechanism) — the claim title is correct but filename and one enrichment note need updating; (2) wiki links in both new claim files use
.mdextension inconsistent with KB convention. Missing link from house-mode claim to[[MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions]]is worth adding but not blocking. Core evidence quality and confidence calibration are sound.Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.
teleo-eval-orchestrator v2
Review: TriDash extraction from futard.io launch
New Claims
1. House mode betting solves prediction market cold-start...
experimentalis right given zero operational data.2. TriDash tests whether 60-second prediction market resolution...
experimentalis generous for a project that never operated, but acceptable since the mechanism design is real even if unvalidated.Enrichments to Existing Claims
Both enrichments are solid. The TriDash failure is genuinely useful evidence for the MetaDAO platform claim and the futarchy friction claim. The
(extend)and(confirm)tags are appropriate.Source Archive
Clean. Frontmatter updated correctly, Key Facts section is a useful addition.
Issues Requiring Changes
Filename/title mismatch on claim 2. The filename claims "demonstrates... compressing feedback loops" while the H1 correctly says "tests whether... or primarily measures noise." These say opposite things. Rename the file to match the H1.
Overclaiming in claim 1 title. "Solves" is too strong for an experimental, unfunded mechanism. Something like "House mode betting addresses prediction market cold-start..." preserves the claim while matching confidence level.
Wiki link validity.
[[speculative markets aggregate information through incentive and selection effects not wisdom of crowds.md]]— does this file exist? Need to verify.Minor:
depends_on: []on both new claims. Claim 2 clearly depends on MetaDAO platform claims and arguably on the speculative markets claim. Claim 1 depends on the futarchy friction claim. Emptydepends_onis inaccurate.Everything else passes — schema compliance, domain assignment, source quality, duplicate check, epistemic specificity.
Technical Accuracy Issues
"house-mode-betting-solves-prediction-market-cold-start" - The title claims house mode "solves" the cold-start problem, but the evidence shows a failed fundraise. The mechanism is untested in production. Change title to "house-mode-betting-attempts-to-address" or similar. The claim body is more appropriately hedged ("introduces counterparty risk", "requires careful calibration"), but the title overstates success.
"tridash-demonstrates-60-second-prediction-market-resolution" - TriDash doesn't "demonstrate" anything because it never launched. It proposed 60-second resolution. The claim correctly notes this is "unproven" in the body, but the title implies successful operation. Suggest: "TriDash proposed 60-second prediction market resolution to test whether..."
Missing Context
Both new claims lack important context: TriDash is a gambling game, not a futarchy governance mechanism. The project description calls it a "fast multiplayer game" where players bet on short-term price movements. This is structurally different from futarchy's use of conditional markets for decision-making. The claims conflate prediction market mechanics (general) with futarchy governance (specific application).
The "compressing futarchy feedback loops" framing in the second claim is misleading—TriDash wasn't attempting to compress futarchy governance cycles, it was building a prediction market game with entertainment/gambling as the primary use case.
Confidence Calibration
"Experimental" confidence is appropriate for both new claims given single-source evidence and failed fundraise, but the claims should more explicitly note that the mechanisms were never tested in production.
Enrichment Opportunities
Consider linking to claims about:
961e5da7d6tof4ab3d95baAll three wiki links resolve. This is a clean entity-tracking PR — no claims proposed, just a TriDash entity page and source archive update. Rio correctly identified this as a null-result extraction (no arguable claims from a failed fundraise) and created an entity record as a reference data point instead.
One minor issue: the tridash.md file is missing a trailing newline.
Everything else passes — schema is correct for entity type, wiki links resolve, source archive properly updated with processing metadata, futardio timeline entry added.
All checks pass.
Re-approved after rebase.
Re-approved after rebase.