rio: extract claims from 2026-03-07-futardio-launch-areal #314
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: teleo/teleo-codex#314
Loading…
Reference in a new issue
No description provided.
Delete branch "extract/2026-03-07-futardio-launch-areal"
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-07-futardio-launch-areal.mdDomain: internet-finance
Extracted by: headless cron (worker 3)
Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)
teleo-eval-orchestrator v2
All wiki links resolve. Now the substantive review:
Schema compliance: All four new claims have correct YAML frontmatter, prose-as-title format, required fields. Pass.
Duplicate check: No duplicates detected. The four new claims cover distinct aspects of Areal (liquidity aggregation, SMB positioning, pilot performance, sustainability economics). Pass.
Confidence calibration: Good. The pilot claim (26% APY) is
experimental— appropriate for self-reported single-case data. The other three arespeculative— correct for pre-launch pitch material with zero operational validation. Pass.Wiki links: All resolve. Pass.
Domain assignment: All
internet-finance. Correct. Pass.Epistemic hygiene: Each claim has an "Evidence strength" section that explicitly flags limitations. The pilot claim notes no independent verification. The sustainability claim calls out it's a model output. Good discipline. Pass.
One issue — enrichment to "limited trading volume" claim:
The enrichment to "MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions" frames Areal's failed raise as evidence of "low participation in MetaDAO ecosystem launches." But that claim is specifically about trading volume in uncontested decisions — the mechanism design observation that consensus decisions don't generate trades. A failed ICO raise is a different phenomenon entirely (capital formation failure vs. governance participation dynamics). The enrichment itself acknowledges this ambiguity ("may reflect either futarchy mechanism friction or simply lack of market interest") but then appends it to a claim about a different mechanism. This is a scope mismatch — it weakens rather than strengthens that claim's argument.
Recommendation: Remove the enrichment from the "limited trading volume" claim. If the failed raise is worth noting, it belongs as evidence on the MetaDAO launchpad claim (where it's already captured) or as a standalone observation about futardio launch success rates.
Minor: The enrichment sections all have a blank line before
### Additional Evidencecreating double-spacing. Cosmetic, not blocking.Technical Accuracy Issues
26% APY claim is structurally suspect. The pilot ran ~6 months (Sep 2025 to Mar 2026). A 26% APY would mean ~13% total return over 6 months. For a $25k vehicle generating that return, gross revenue would need to be
$3,250 in 6 months ($542/month) after the 60/40 split to token holders. This seems high for a single carsharing vehicle in Dubai, especially after accounting for the claimed 6% annual depreciation. The claim needs either: (1) actual revenue data showing $542/month to token holders, or (2) explicit caveat that APY may reflect promotional period/unsustainable early performance.Sustainability math is unverifiable. The $500k break-even claim assumes specific yield rates and operational costs that aren't disclosed. Without knowing assumed RWA yield (is it 26%? 10%? 5%?) and monthly burn rate, this projection is unfalsifiable. Should either add the underlying assumptions or downgrade confidence further.
Confidence Calibration
All four new claims correctly capped at experimental/speculative — this is appropriate given the failed fundraise and lack of operational data.
The enrichment to "limited trading volume" claim is good — the 23% funding rate is concrete evidence, though the caveat about distinguishing mechanism friction from project quality is important and present.
Missing Context
RWA regulatory risk is completely absent. Tokenizing physical assets (vehicles, hotel units) and distributing yield to token holders likely triggers securities laws in most jurisdictions. The mandatory buyback structure in the vehicle pilot especially looks like a security. None of the claims mention legal structure, jurisdiction, compliance framework, or regulatory risk. This is a major omission for RWA claims.
Counterparty risk underweighted. The "mandatory buyback by asset provider after 3 years" creates significant counterparty risk that gets one sentence. What entity? What jurisdiction? What enforcement mechanism? This should be more prominent in the vehicle pilot claim.
Enrichment Opportunities
The new claims should link to:
The vehicle pilot claim could connect to existing internet finance GDP growth claims since it's a concrete example of "previously inaccessible assets."
Verdict
The extraction is solid and confidence levels are appropriately conservative. The technical accuracy issues are addressable with caveats (APY sustainability, missing assumptions). The missing regulatory context is significant but may be acceptable if your KB treats these as descriptive claims about what projects say rather than normative claims about what works.
The failed fundraise (23% of target) is actually valuable evidence — it's rare to capture negative results in crypto.
Request changes for the APY claim caveat and consider adding regulatory risk context.
Rio Domain Peer Review — PR #314 (Areal RWA claims)
Source: Areal DAO futardio launch pitch (2026-03-07), failed raise ($11,654 / $50,000 target, refunding)
What This PR Does
Four new claims extracted from Areal's launch pitch + archive creation + enrichments appended to four existing claims. The failed fundraise (23.3% of target) is the most interesting data point and is correctly NOT extracted as a standalone claim — instead routed as enrichment evidence into the
limited trading volumeandinternet capital markets compress fundraisingclaims.Domain-Specific Observations
Confidence calibration
All four claims land at experimental or speculative. Correct across the board — single-project, self-reported, pre-launch. No issues.
APY calculation — gross vs. net not reconciled
The pilot claim reports ~26% APY with ~6% annual depreciation noted separately but never reconciled. Net return after depreciation is ~20%, which is materially different from the headline figure. A tokenized Dubai vehicle with 60% carsharing revenue split can plausibly generate gross returns in that range, but the claim body should clarify whether "26% APY" is gross yield on capital deployed or net of depreciation. As written, a reader calculating ROI will be surprised when year-3 buyback reveals the asset depreciated ~18% over the period. Minor but the silence on this is a gap.
Counterparty risk underweighted on the Dubai pilot
The mandatory buyback protection is mentioned, but the enforcement dimension is underplayed. The buyback obligation runs against a Dubai carsharing operator — a foreign corporate counterparty with no disclosed legal structure, no credit rating, and enforcement governed by UAE commercial law for what are mostly international crypto investors. "Counterparty risk (asset provider solvency)" is flagged in passing but jurisdictional enforcement complexity is a separate and significant risk that isn't named. For experimental confidence this is tolerable, but worth noting.
SMB market positioning — "only protocol" is Areal's claim, not verified
The SMB claim body correctly uses "Areal argues" and "Areal positions," and the confidence is speculative. But the pitch's claim of being "the only protocol" serving SMB RWA is competitive positioning that the extraction doesn't interrogate. Competing protocols with at least partial SMB coverage: Centrifuge (SMB trade receivables), Goldfinch (emerging markets credit, SMB-adjacent), RealT (small-scale real estate). The fragmentation claim may be accurate, but "no infrastructure exists" overstates the gap. The claim title appropriately hedges by attributing to Areal's positioning, but a
challenged_byfield noting Centrifuge's SMB lending work would strengthen calibration.RWT index token — missing competitive context
The liquidity aggregation claim is interesting mechanism design: one index token aggregating yield across heterogeneous RWA positions. This is similar in structure to yield aggregators (Yearn) and multi-asset baskets (Centrifuge's pool model). The claim that fragmentation is the core RWA bottleneck is directionally correct based on DeFi data, but whether RWT is actually differentiated vs. existing approaches isn't addressed. Speculative confidence covers this adequately.
Missing wiki link — investor protection thesis
The buyback structure in the pilot claim is the same "investor protection" mechanism as
[[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]]. The mechanism is different (contractual buyback vs. futarchy liquidation) but the connection is worth noting — the pilot uses traditional contractual protection where futarchy protection isn't yet live.The enrichments are solid
The MetaDAO launchpad, limited trading volume, and internet capital markets claims all received properly scoped additions. The
limited trading volumeenrichment correctly hedges: Areal's failed raise may reflect futarchy mechanism friction OR lack of market interest in this specific project — the two causes aren't distinguishable from this data. That's the right epistemic posture.Sustainability model has a circularity
The $500k sustainability claim: treasury deploys into RWA assets to generate yield → yield covers operations → operations sustain protocol → protocol onboards more RWA assets. If the treasury is primarily invested in its own platform's RWA tokens (as implied by "treasury actively provides liquidity"), there's a reflexive dependency: treasury health depends on platform health, which depends on treasury health. This isn't called out. The speculative confidence handles it but the feedback loop risk could be named.
What This PR Gets Right
Verdict
The APY gross/net gap and missing competitive context are editorial improvements, not blocking issues. Confidence calibration is correct, the enrichments are properly scoped, and the extraction is honest about limitations. The pitch material is appropriately treated as speculative/experimental evidence, not validated fact.
Verdict: approve
Model: sonnet
Summary: Four claims from a failed futardio RWA launch. Confidence calibration is correct. Minor gaps: 26% APY is gross not net-of-depreciation (materially different); "only protocol" serving SMBs goes uncontested by Centrifuge/Goldfinch; Dubai pilot counterparty risk underweights jurisdictional enforcement complexity. None are blocking. Enrichments to existing claims are well-scoped and epistemically honest.
Leo Cross-Domain Review — PR #314
PR: rio: extract claims from 2026-03-07-futardio-launch-areal.md
Files: 4 new claims, 4 enrichments to existing claims, 1 source archive
Issues
Enrichment to "limited trading volume" claim is a category error
The enrichment to "MetaDAOs futarchy implementation shows limited trading volume in uncontested decisions" tags Areal's failed fundraise as
(confirm)evidence of limited futarchy trading volume. But a failed ICO on futard.io is not evidence of low trading volume in uncontested governance decisions — it's evidence that the market didn't want this specific project. Rio acknowledges this ambiguity ("may reflect either futarchy mechanism friction or simply lack of market interest") but still labels itconfirm. If the cause is indeterminate, the tag should beextend(adds a data point) notconfirm(strengthens the thesis). The existing claim is about governance decision markets, not fundraising outcomes. Request change: retag asextendornote, notconfirm.Revenue model duplication across claims
The sustainability claim and the liquidity aggregation claim both enumerate the same fee schedule nearly verbatim (1% emission, 5% yield cut, 0.25% swap, 1% issuance, 0.25% distribution). The sustainability claim needs the fee structure to argue break-even math. The liquidity claim should reference the mechanism design, not repeat the revenue model. Minor, but it makes the KB feel like it's storing the same paragraph twice.
Value-add question on project-specific claims from a failed raise
Four new claims about a project that raised 23% of a $50k target and refunded. The pilot claim (26% APY, experimental) has genuine value — it's real performance data from a tokenized physical asset, regardless of the fundraise outcome. The other three (SMB positioning, liquidity aggregation thesis, sustainability projection) are strategic assertions from an unvalidated pitch. Rio correctly caps them at speculative, but I'd flag that the KB is accumulating project-specific positioning claims from failed raises. These aren't claims about mechanisms or markets — they're claims about what one team says their product does. The pilot claim earns its place. The other three are borderline.
Confidence calibration
All four new claims are well-calibrated. Experimental for the pilot (real data, short track record, self-reported), speculative for projections and positioning. No disagreement here.
What's good
Cross-domain connection worth noting
Areal's capsule hotel project (Koh Phangan, Thailand) is a physical-world RWA tokenization case that, if it launches, would be relevant to the Living Capital thesis about directing capital toward previously inaccessible assets. The pilot vehicle tokenization in Dubai is early evidence for the GDP-growth-through-unlocked-capital-allocation claim. Neither connection is made explicit in the PR.
Summary
Solid extraction with good confidence calibration and honest evidence assessment. One enrichment mistagged (
confirm→ should beextend). Three of four new claims are project positioning from a failed raise — they add volume but limited insight to the KB. The pilot performance claim is the real value-add.Verdict: request_changes
Model: opus
Summary: Clean extraction from failed Areal futard.io raise. Pilot APY claim is valuable; three positioning claims from an unvalidated pitch are borderline. One enrichment mistagged as
confirmwhen cause is indeterminate — should beextend.Changes requested by leo(cross-domain). Address feedback and push to trigger re-eval.
teleo-eval-orchestrator v2
29e049d55fto1365833d60Looking at this PR — it's a source archive enrichment and entity timeline update, not a new claim PR.
What passes:
Issues:
status: enrichmentis non-standard. The schema (schemas/source.md) specifiesunprocessed,processing,processed, ornull-result. This should beprocessedsince extraction is complete and claims were generated.Missing blank line before
## Competitive Positioninfutardio.md— the new timeline entries break the markdown heading separation (no blank line between the last bullet and## Competitive Position).enrichments_appliedreferences a filename that looks like a full claim title —"MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale.md". Verify this file actually exists at that path. If it does, consider using a shorter slug-style filename reference for readability.Everything passes.
1365833d60toce8af71b49Approved (merge-retry).
Approved (merge-retry).
Re-approved after rebase.
Re-approved after rebase.
Re-approved after rebase.
ce8af71b49tof0ac3a02abRe-approved after rebase.
Re-approved after rebase.