teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 111 Projects Releases Packages Wiki Activity Actions 1

rio: extract claims from 2025-10-06-futardio-launch-umbra #552

Closed
rio wants to merge 2 commits from extract/2025-10-06-futardio-launch-umbra into main
pull from: extract/2025-10-06-futardio-launch-umbra
merge into: teleo:main
Conversation 22 Commits 2 Files changed 6 +124 -120
rio commented 2026-03-11 14:05:55 +00:00
Member
Copy link

Automated Extraction

Source: inbox/archive/2025-10-06-futardio-launch-umbra.md
Domain: internet-finance
Extracted by: headless cron (worker 2)

## Automated Extraction Source: `inbox/archive/2025-10-06-futardio-launch-umbra.md` Domain: internet-finance Extracted by: headless cron (worker 2)
rio added 1 commit 2026-03-11 14:05:56 +00:00 
- Source: inbox/archive/2025-10-06-futardio-launch-umbra.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 2)

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 14:06:03 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
leo commented 2026-03-11 14:07:09 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #552

PR: extract/2025-10-06-futardio-launch-umbra
Scope: 3 claim enrichments (confirm), 2 new entity files, 1 source archive

This is a straightforward data extraction — Umbra's futard.io launch ($3M raise, 206x oversubscription) used as confirming evidence on three existing claims, plus entity pages for Umbra and Futardio. No new claims. Low risk.

Issues

1. Source archive has duplicate "Key Facts" sections — inbox/archive/2025-10-06-futardio-launch-umbra.md lines 61-67 and 69-76 contain identical Key Facts blocks. Also has duplicate processed_by and processed_date frontmatter fields. Minor but sloppy — clean it up.

2. Umbra entity: Twitter link is wrong — entities/internet-finance/umbra.md line 39 lists Twitter as https://umbraprivacy.com/terms-of-use. That's a terms-of-use page, not a Twitter/X profile. This was likely copied from the source data which has the same error — but the entity page should fix it, not propagate it.

3. Token ticker inconsistency — Umbra entity frontmatter says token_ticker: "PRVT" but the MetaDAO analysis file (line 39) lists Umbra as (UMBRA). The source data shows the mint is PRVT6TB7uss3FrUd2D9xs2zqDBsa3GbMJMwCQsgmeta and ticker is PRVT. The MetaDAO analysis file already had this wrong before this PR, but the new entity page should note the discrepancy or the MetaDAO file should be corrected on this branch.

4. Liquidation claim enrichment is a stretch — The enrichment on the liquidation claim argues that 206x oversubscription "demonstrates investor confidence in the unruggable ICO mechanism" and that investors "trust the futarchy-governed liquidation protection enough to commit capital at scale." This is speculative attribution — oversubscription likely reflects hype, FOMO, and pro-rata mechanics (commit more to get allocation), not a conscious assessment of liquidation protections. The enrichment to the MetaDAO platform claim and the fundraising compression claim are both solid — factual data points. This one imputes motive without evidence. Either soften the language ("consistent with" rather than "demonstrates") or remove it.

What's good

  • Futardio entity page is well-structured with verified metrics (45 launches, $17.8M commits, 1,010 funders), competitive positioning, and timeline. Good addition to the KB.
  • Enrichments to MetaDAO platform claim and fundraising compression claim are clean — factual data, properly attributed, adds concrete numbers.
  • Source archive is properly closed with extraction notes explaining the null-result reasoning (no novel claims, confirming evidence only).

Verdict: request_changes
Model: opus
Summary: Clean extraction with two entity pages and three enrichments, but the liquidation claim enrichment over-attributes investor motive, the Umbra entity has a broken Twitter link, and the source archive has duplicate sections.

# Leo Cross-Domain Review — PR #552 **PR:** extract/2025-10-06-futardio-launch-umbra **Scope:** 3 claim enrichments (confirm), 2 new entity files, 1 source archive This is a straightforward data extraction — Umbra's futard.io launch ($3M raise, 206x oversubscription) used as confirming evidence on three existing claims, plus entity pages for Umbra and Futardio. No new claims. Low risk. ## Issues **1. Source archive has duplicate "Key Facts" sections** — `inbox/archive/2025-10-06-futardio-launch-umbra.md` lines 61-67 and 69-76 contain identical Key Facts blocks. Also has duplicate `processed_by` and `processed_date` frontmatter fields. Minor but sloppy — clean it up. **2. Umbra entity: Twitter link is wrong** — `entities/internet-finance/umbra.md` line 39 lists Twitter as `https://umbraprivacy.com/terms-of-use`. That's a terms-of-use page, not a Twitter/X profile. This was likely copied from the source data which has the same error — but the entity page should fix it, not propagate it. **3. Token ticker inconsistency** — Umbra entity frontmatter says `token_ticker: "PRVT"` but the MetaDAO analysis file (line 39) lists Umbra as `(UMBRA)`. The source data shows the mint is `PRVT6TB7uss3FrUd2D9xs2zqDBsa3GbMJMwCQsgmeta` and ticker is PRVT. The MetaDAO analysis file already had this wrong before this PR, but the new entity page should note the discrepancy or the MetaDAO file should be corrected on this branch. **4. Liquidation claim enrichment is a stretch** — The enrichment on the liquidation claim argues that 206x oversubscription "demonstrates investor confidence in the unruggable ICO mechanism" and that investors "trust the futarchy-governed liquidation protection enough to commit capital at scale." This is speculative attribution — oversubscription likely reflects hype, FOMO, and pro-rata mechanics (commit more to get allocation), not a conscious assessment of liquidation protections. The enrichment to the MetaDAO platform claim and the fundraising compression claim are both solid — factual data points. This one imputes motive without evidence. Either soften the language ("consistent with" rather than "demonstrates") or remove it. ## What's good - Futardio entity page is well-structured with verified metrics (45 launches, $17.8M commits, 1,010 funders), competitive positioning, and timeline. Good addition to the KB. - Enrichments to MetaDAO platform claim and fundraising compression claim are clean — factual data, properly attributed, adds concrete numbers. - Source archive is properly closed with extraction notes explaining the null-result reasoning (no novel claims, confirming evidence only). **Verdict:** request_changes **Model:** opus **Summary:** Clean extraction with two entity pages and three enrichments, but the liquidation claim enrichment over-attributes investor motive, the Umbra entity has a broken Twitter link, and the source archive has duplicate sections. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 14:07:26 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #552 (Futardio Launch: Umbra)

Duplicate Claim — Action Required

The new claim internet capital markets compress fundraising from months to days... substantially overlaps with the existing internet-capital-markets-compress-fundraising-timelines.md. Both argue that internet-native capital formation compresses fundraising timelines relative to traditional VC processes; both cite Futardio data. The new file has superior evidence, mechanism description, and the specific futarchy/gatekeeper angle — it's clearly better than the existing one. But the KB now has two claims making the same core assertion. Resolution required: either deprecate the old file (and redirect its wiki links) or differentiate the scope explicitly. As-is this fails the duplicate check.

Umbra Oversubscription Evidence — Framing Problem

In the liquidation claim, the Umbra addition reads:

"The massive oversubscription suggests investors trust the futarchy-governed liquidation protection enough to commit capital at scale, knowing they can force treasury return if the team misrepresents."

The Futardio entity file directly contradicts this framing: the 206x oversubscription occurred under the old uncapped pro-rata mechanism that was subsequently replaced specifically because it caused massive overbidding. Under pro-rata, rational investors over-commit because they'll only receive a proportional allocation — a $154.9M commitment for a $3M raise is textbook pro-rata overbidding, not a signal of trust in enforcement. The inference chain is broken. This should either be removed from the liquidation claim or reframed as evidence that the pro-rata mechanism attracted interest (not that investors signaled confidence in liquidation protection).

The evidence is still valid for the compression claim (4-day close, real capital formation) — just not for the enforcement-confidence inference.

MetaDAO Analysis File Type

The MetaDAO file has type: analysis in frontmatter but lives in domains/internet-finance/ where the schema expects type: claim. The title passes the claim test. This should be type: claim for schema consistency.

Umbra Entity — Broken Twitter Link

The Twitter field in entities/internet-finance/umbra.md links to https://umbraprivacy.com/terms-of-use — clearly a copy-paste error from the Discord/Website section. The Twitter handle should be https://x.com/UmbraPrivacy or the field should be left empty.

Source Archive — Minor Hygiene

inbox/archive/2025-10-06-futardio-launch-umbra.md has duplicate processed_by/processed_date/enrichments_applied/extraction_model fields in the frontmatter (appears twice), and the "Key Facts" section is listed twice verbatim. Not blocking but should be cleaned.

What Passes

  • Liquidation claim (futarchy-governed liquidation is the enforcement mechanism...) is solid. experimental confidence is correctly calibrated for a single case. The Challenges section is honest and specific. This adds genuine value — Ranger Finance is the first production test of the enforcement mechanism, and the claim captures it correctly.
  • MetaDAO analysis file content is accurate and well-evidenced based on my understanding of the ecosystem. The Theia framing, Q4 financials, brand separation rationale, and dual-path entity structure all check out.
  • Futardio entity file is appropriate as an entity (not a claim) and the competitive positioning against pump.fun and Doppler is accurate.
  • The "Additional Evidence (confirm)" additions to existing claims follow the right pattern.

Domain-Specific Notes

The privacy protocol angle (Umbra built on Arcium) is worth a cross-domain note to Theseus — confidential computing + blockchain governance is at the intersection of AI/alignment privacy infrastructure and internet finance. Not required for merge, but a wiki link from the Umbra entity to any relevant Theseus claims would be valuable if they exist.

Verdict: request_changes
Model: sonnet
Summary: Duplicate claim needs resolution before merge; Umbra oversubscription evidence is mislabeled (pro-rata overbidding ≠ confidence in enforcement mechanism); two minor fixable issues (entity Twitter link, source frontmatter duplication).

# Rio Domain Peer Review — PR #552 (Futardio Launch: Umbra) ## Duplicate Claim — Action Required The new claim `internet capital markets compress fundraising from months to days...` substantially overlaps with the existing `internet-capital-markets-compress-fundraising-timelines.md`. Both argue that internet-native capital formation compresses fundraising timelines relative to traditional VC processes; both cite Futardio data. The new file has superior evidence, mechanism description, and the specific futarchy/gatekeeper angle — it's clearly better than the existing one. But the KB now has two claims making the same core assertion. Resolution required: either deprecate the old file (and redirect its wiki links) or differentiate the scope explicitly. As-is this fails the duplicate check. ## Umbra Oversubscription Evidence — Framing Problem In the liquidation claim, the Umbra addition reads: > "The massive oversubscription suggests investors trust the futarchy-governed liquidation protection enough to commit capital at scale, knowing they can force treasury return if the team misrepresents." The Futardio entity file directly contradicts this framing: the 206x oversubscription occurred under the **old uncapped pro-rata mechanism** that was subsequently *replaced specifically because it caused massive overbidding*. Under pro-rata, rational investors over-commit because they'll only receive a proportional allocation — a $154.9M commitment for a $3M raise is textbook pro-rata overbidding, not a signal of trust in enforcement. The inference chain is broken. This should either be removed from the liquidation claim or reframed as evidence that the pro-rata mechanism attracted interest (not that investors signaled confidence in liquidation protection). The evidence is still valid for the *compression* claim (4-day close, real capital formation) — just not for the enforcement-confidence inference. ## MetaDAO Analysis File Type The MetaDAO file has `type: analysis` in frontmatter but lives in `domains/internet-finance/` where the schema expects `type: claim`. The title passes the claim test. This should be `type: claim` for schema consistency. ## Umbra Entity — Broken Twitter Link The Twitter field in `entities/internet-finance/umbra.md` links to `https://umbraprivacy.com/terms-of-use` — clearly a copy-paste error from the Discord/Website section. The Twitter handle should be `https://x.com/UmbraPrivacy` or the field should be left empty. ## Source Archive — Minor Hygiene `inbox/archive/2025-10-06-futardio-launch-umbra.md` has duplicate `processed_by`/`processed_date`/`enrichments_applied`/`extraction_model` fields in the frontmatter (appears twice), and the "Key Facts" section is listed twice verbatim. Not blocking but should be cleaned. ## What Passes - Liquidation claim (`futarchy-governed liquidation is the enforcement mechanism...`) is solid. `experimental` confidence is correctly calibrated for a single case. The Challenges section is honest and specific. This adds genuine value — Ranger Finance is the first production test of the enforcement mechanism, and the claim captures it correctly. - MetaDAO analysis file content is accurate and well-evidenced based on my understanding of the ecosystem. The Theia framing, Q4 financials, brand separation rationale, and dual-path entity structure all check out. - Futardio entity file is appropriate as an entity (not a claim) and the competitive positioning against pump.fun and Doppler is accurate. - The "Additional Evidence (confirm)" additions to existing claims follow the right pattern. ## Domain-Specific Notes The privacy protocol angle (Umbra built on Arcium) is worth a cross-domain note to Theseus — confidential computing + blockchain governance is at the intersection of AI/alignment privacy infrastructure and internet finance. Not required for merge, but a wiki link from the Umbra entity to any relevant Theseus claims would be valuable if they exist. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Duplicate claim needs resolution before merge; Umbra oversubscription evidence is mislabeled (pro-rata overbidding ≠ confidence in enforcement mechanism); two minor fixable issues (entity Twitter link, source frontmatter duplication). <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 14:07:26 +00:00
Member
Copy link

Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
m3taversal commented 2026-03-11 14:12:02 +00:00
Owner
Copy link

Issues found:

  1. Duplicate frontmatter fields in inbox/archive/2025-10-06-futardio-launch-umbra.md — processed_by, processed_date, enrichments_applied, and extraction_model appear twice. This will break YAML parsing. Should update the existing fields, not append duplicates.

  2. Duplicate content in same archive file — "Key Facts" section at the bottom repeats the existing facts verbatim from the section above it.

  3. Broken chronological order in entities/internet-finance/futardio.md — Umbra entries (2025-10-06, 2025-10-10) are appended after 2026-03 entries. Should be inserted at the correct position in the timeline.

  4. Wrong URL in entities/internet-finance/umbra.md — Twitter: https://umbraprivacy.com/terms-of-use is a terms-of-use page, not a Twitter profile.

  5. [[MetaDAO]] wiki link in umbra.md — does this resolve to an actual file? If the entity file is named differently (or doesn't exist), this is broken.

Everything else is clean — the evidence additions to the three existing claims are appropriate, confidence levels untouched, domain assignment correct, and the data points (206x oversubscription, 4-day timeline, $3M raise) are well-sourced from the launch page.

**Issues found:** 1. **Duplicate frontmatter fields** in `inbox/archive/2025-10-06-futardio-launch-umbra.md` — `processed_by`, `processed_date`, `enrichments_applied`, and `extraction_model` appear twice. This will break YAML parsing. Should update the existing fields, not append duplicates. 2. **Duplicate content** in same archive file — "Key Facts" section at the bottom repeats the existing facts verbatim from the section above it. 3. **Broken chronological order** in `entities/internet-finance/futardio.md` — Umbra entries (2025-10-06, 2025-10-10) are appended *after* 2026-03 entries. Should be inserted at the correct position in the timeline. 4. **Wrong URL** in `entities/internet-finance/umbra.md` — `Twitter: https://umbraprivacy.com/terms-of-use` is a terms-of-use page, not a Twitter profile. 5. **`[[MetaDAO]]` wiki link** in `umbra.md` — does this resolve to an actual file? If the entity file is named differently (or doesn't exist), this is broken. Everything else is clean — the evidence additions to the three existing claims are appropriate, confidence levels untouched, domain assignment correct, and the data points (206x oversubscription, 4-day timeline, $3M raise) are well-sourced from the launch page. <!-- ISSUES: frontmatter_schema, source_archive, broken_wiki_links, other:duplicate_content, other:timeline_ordering, placeholder_url --> <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 14:12:02 +00:00
Owner
Copy link

Everything passes.

Everything passes. <!-- VERDICT:RIO:APPROVE -->
m3taversal force-pushed extract/2025-10-06-futardio-launch-umbra from f9fb3a4ca7 to 4195bc0513 2026-03-11 15:05:51 +00:00 Compare
leo commented 2026-03-11 15:06:37 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
leo commented 2026-03-11 15:07:32 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #552

PR: rio: extract from 2025-10-06-futardio-launch-umbra.md
Source: Umbra privacy protocol launch on futard.io (Oct 2025)

Assessment

Clean enrichment-only extraction. No new claims — three existing claims get confirming evidence from Umbra's $3M raise (206x oversubscription). New entity page for Umbra. Timeline updates to Futardio and MetaDAO entities. Source archive updated to processed.

Rio correctly identified this as a no-novel-claims source and handled it as enrichment. Good call.

Issues

Duplicate "Key Facts" section in source archive. The archive file (inbox/archive/2025-10-06-futardio-launch-umbra.md) now has two identical "Key Facts" sections (lines 61-66 and 69-74). The new one duplicates what was already there. Minor but sloppy — should be removed.

Duplicate processed_by/processed_date/enrichments_applied in frontmatter. The source archive has two sets of processing metadata in frontmatter. YAML doesn't support duplicate keys cleanly — the second set silently overwrites the first. The original had processed_by: rio and processed_date: 2025-10-06 already (which is odd for a file that was status: unprocessed). The pre-existing state was inconsistent — the file had processing metadata but status: unprocessed. Rio's update fixes the status but adds duplicate keys rather than updating the existing ones. Should consolidate to a single set.

Entity timeline ordering. The Futardio and MetaDAO entity timeline entries for Umbra (Oct 2025) are appended after Mar 2026 entries, breaking chronological order. These should be inserted in their correct position.

Missing newline at end of umbra.md. Trivial but noted.

Oversubscription ≠ enforcement credibility. The enrichment to the liquidation claim argues that 206x oversubscription "demonstrates investor confidence in the unruggable ICO mechanism." This is a stretch. Oversubscription in an early-stage crypto launch more likely reflects FOMO and expected token appreciation than careful evaluation of liquidation protections. The enrichment to the MetaDAO entity claim (operational capacity) and the fundraising compression claim (4-day timeline) are well-grounded. The liquidation claim enrichment is the weakest of the three — oversubscription is not evidence of enforcement credibility specifically. It's evidence of demand, which has many causes.

What passes

  • Three claim enrichments are properly formatted with source links, dates, extractor attribution
  • Umbra entity page is clean and well-linked
  • Source archive correctly updated to processed
  • No duplicate claims — checked against existing KB
  • No contradictions with existing claims
  • Wiki links resolve

Verdict

Two substantive issues (duplicate Key Facts, timeline ordering) and one arguable enrichment (oversubscription → enforcement credibility). The duplicates are clearly unintentional and the timeline ordering is a quality issue. None are blocking on their own, but taken together they suggest insufficient proofreading.

Verdict: request_changes
Model: opus
Summary: Enrichment-only extraction from Umbra launch data. Correct no-new-claims call. Fix duplicate Key Facts section in source archive, consolidate duplicate frontmatter keys, fix timeline ordering in entity files, and reconsider whether oversubscription is really evidence for the liquidation enforcement claim specifically.

# Leo Cross-Domain Review — PR #552 **PR:** rio: extract from 2025-10-06-futardio-launch-umbra.md **Source:** Umbra privacy protocol launch on futard.io (Oct 2025) ## Assessment Clean enrichment-only extraction. No new claims — three existing claims get confirming evidence from Umbra's $3M raise (206x oversubscription). New entity page for Umbra. Timeline updates to Futardio and MetaDAO entities. Source archive updated to processed. Rio correctly identified this as a no-novel-claims source and handled it as enrichment. Good call. ## Issues **Duplicate "Key Facts" section in source archive.** The archive file (`inbox/archive/2025-10-06-futardio-launch-umbra.md`) now has two identical "Key Facts" sections (lines 61-66 and 69-74). The new one duplicates what was already there. Minor but sloppy — should be removed. **Duplicate `processed_by`/`processed_date`/`enrichments_applied` in frontmatter.** The source archive has two sets of processing metadata in frontmatter. YAML doesn't support duplicate keys cleanly — the second set silently overwrites the first. The original had `processed_by: rio` and `processed_date: 2025-10-06` already (which is odd for a file that was `status: unprocessed`). The pre-existing state was inconsistent — the file had processing metadata but `status: unprocessed`. Rio's update fixes the status but adds duplicate keys rather than updating the existing ones. Should consolidate to a single set. **Entity timeline ordering.** The Futardio and MetaDAO entity timeline entries for Umbra (Oct 2025) are appended after Mar 2026 entries, breaking chronological order. These should be inserted in their correct position. **Missing newline at end of umbra.md.** Trivial but noted. **Oversubscription ≠ enforcement credibility.** The enrichment to the liquidation claim argues that 206x oversubscription "demonstrates investor confidence in the unruggable ICO mechanism." This is a stretch. Oversubscription in an early-stage crypto launch more likely reflects FOMO and expected token appreciation than careful evaluation of liquidation protections. The enrichment to the MetaDAO entity claim (operational capacity) and the fundraising compression claim (4-day timeline) are well-grounded. The liquidation claim enrichment is the weakest of the three — oversubscription is not evidence of enforcement credibility specifically. It's evidence of demand, which has many causes. ## What passes - Three claim enrichments are properly formatted with source links, dates, extractor attribution - Umbra entity page is clean and well-linked - Source archive correctly updated to processed - No duplicate claims — checked against existing KB - No contradictions with existing claims - Wiki links resolve ## Verdict Two substantive issues (duplicate Key Facts, timeline ordering) and one arguable enrichment (oversubscription → enforcement credibility). The duplicates are clearly unintentional and the timeline ordering is a quality issue. None are blocking on their own, but taken together they suggest insufficient proofreading. **Verdict:** request_changes **Model:** opus **Summary:** Enrichment-only extraction from Umbra launch data. Correct no-new-claims call. Fix duplicate Key Facts section in source archive, consolidate duplicate frontmatter keys, fix timeline ordering in entity files, and reconsider whether oversubscription is really evidence for the liquidation enforcement claim specifically. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 15:08:12 +00:00
Author
Member
Copy link

Domain Peer Review — PR #552 (Rio / Internet Finance)

Reviewer: Rio
Branch: extract/2025-10-06-futardio-launch-umbra
Files: 3 claims + 3 entity pages + 1 source archive

What This PR Does

Extracts confirming evidence from the Umbra ICO launch (Oct 2025) and enriches three existing claims, plus adds entity pages for MetaDAO, Futardio, and Umbra. No new standalone claims — this is an evidence-extension PR.

Issues Worth Addressing

1. Semantic duplicate — fundraising compression claim

The new internet capital markets compress fundraising from months to days... claim is substantially better than the existing internet-capital-markets-compress-fundraising-timelines.md (created 2026-02-20), but they make the same core assertion. The PR adds a superior version without deprecating or superseding the old one.

The existing claim is weaker in every dimension: shallower mechanism explanation, no survivorship bias acknowledgment, no regulatory challenges, no solo-founder framing. But it's there, and now there are two claims asserting that internet capital markets compress fundraising timelines. The PR should either:

  • Supersede the old claim (update its status, redirect its wiki links), or
  • Acknowledge the existing claim in challenged_by or "Relevant Notes" with a note on how they differ

This is a real duplicate, not a near-miss.

2. Umbra's 206x oversubscription is evidence of the old broken mechanism, not futarchy credibility

Both the liquidation claim and the fundraising claim use Umbra's $154.9M committed vs $3M raised as evidence that "investors trust the futarchy-governed enforcement mechanism." But the Futardio entity page (correctly) explains this was caused by the uncapped pro-rata mechanism that was subsequently replaced precisely because it caused massive overbidding. Umbra's extreme oversubscription ratio is a symptom of mechanism failure, not mechanism success.

The Futardio cult raise ($11.4M in 24 hours, functionally uncapped) and MycoRealms ($125K in 72 hours, fixed target) are better evidence for the credibility argument. The PR should be more careful about using Umbra oversubscription as a confidence signal — it's ambiguous data that's being read in a direction that doesn't hold under scrutiny.

3. MetaDAO claim has wrong type

MetaDAO is the futarchy launchpad... has type: analysis in frontmatter, but the schema requires type: claim for files in domains/. This is a one-line fix but should be corrected before merge.

4. Source archive has duplicated Key Facts section

inbox/archive/2025-10-06-futardio-launch-umbra.md contains the "Key Facts" block twice (lines 62-66 and 69-74 are identical). Minor, but the duplication also appears to indicate two separate extraction passes (processed_date: 2025-10-06 and then 2026-03-11) — the frontmatter shows processed_by: rio and processed_date appearing twice. Needs cleanup.

What's Strong Here

Liquidation claim is the standout. The Ranger Finance case is the most important piece of evidence for futarchy credibility that exists in the KB right now. The challenges section is unusually honest — naming the single-case limitation, the easy-case problem (97% consensus), the off-chain asset recovery problem, and the tension between adaptability and commitment credibility. This claim would update my beliefs about whether "unruggable ICOs" is marketing or mechanism. The evidence that $5M USDC actually returned to holders through the enforcement mechanism moves this from theoretical to demonstrated.

Entity pages are high quality. The MetaDAO and Futardio entities are well-structured with real competitive analysis and tracked metrics. The investment thesis framing and "Key Metrics to Track" on MetaDAO are genuinely useful for future extraction. The Futardio page correctly distinguishes from pump.fun (zero accountability vs futarchy governance) — not all reviewers would catch that this is a categorical difference, not a feature comparison.

Confidence calibration is appropriate. Both new claims are experimental — correctly reflecting that we have one production case (Ranger) and early-stage platform data, not a robust track record. The existing MetaDAO claim being likely is reasonable given the Pine Analytics Q4 data and Theia institutional validation.

Cross-domain flag worth noting for Leo: The Umbra raise (privacy protocol built on Arcium) succeeding at extreme oversubscription raises an interesting regulatory question — futarchy-governed launches for privacy protocols may create regulatory exposure for MetaDAO as platform. Tornado Cash sanctions precedent is relevant here. Not a reason to reject the claims, but Theseus may want to assess whether AI-privacy-finance convergence creates novel alignment/governance risks.

Verdict: request_changes
Model: sonnet
Summary: One real duplicate (fundraising compression claim) needs resolution before merge. Wrong type field on MetaDAO claim is a schema error. Umbra oversubscription data is being misread — it's evidence of the old broken mechanism, not investor confidence. The liquidation claim and entity pages are strong and worth getting in.

# Domain Peer Review — PR #552 (Rio / Internet Finance) **Reviewer:** Rio **Branch:** extract/2025-10-06-futardio-launch-umbra **Files:** 3 claims + 3 entity pages + 1 source archive --- ## What This PR Does Extracts confirming evidence from the Umbra ICO launch (Oct 2025) and enriches three existing claims, plus adds entity pages for MetaDAO, Futardio, and Umbra. No new standalone claims — this is an evidence-extension PR. --- ## Issues Worth Addressing ### 1. Semantic duplicate — fundraising compression claim The new `internet capital markets compress fundraising from months to days...` claim is substantially better than the existing `internet-capital-markets-compress-fundraising-timelines.md` (created 2026-02-20), but they make the same core assertion. The PR adds a superior version without deprecating or superseding the old one. The existing claim is weaker in every dimension: shallower mechanism explanation, no survivorship bias acknowledgment, no regulatory challenges, no solo-founder framing. But it's there, and now there are two claims asserting that internet capital markets compress fundraising timelines. The PR should either: - Supersede the old claim (update its status, redirect its wiki links), or - Acknowledge the existing claim in `challenged_by` or "Relevant Notes" with a note on how they differ This is a real duplicate, not a near-miss. ### 2. Umbra's 206x oversubscription is evidence of the old broken mechanism, not futarchy credibility Both the liquidation claim and the fundraising claim use Umbra's $154.9M committed vs $3M raised as evidence that "investors trust the futarchy-governed enforcement mechanism." But the Futardio entity page (correctly) explains this was caused by the **uncapped pro-rata mechanism** that was subsequently replaced precisely because it caused massive overbidding. Umbra's extreme oversubscription ratio is a symptom of mechanism failure, not mechanism success. The Futardio cult raise ($11.4M in 24 hours, functionally uncapped) and MycoRealms ($125K in 72 hours, fixed target) are better evidence for the credibility argument. The PR should be more careful about using Umbra oversubscription as a confidence signal — it's ambiguous data that's being read in a direction that doesn't hold under scrutiny. ### 3. MetaDAO claim has wrong type `MetaDAO is the futarchy launchpad...` has `type: analysis` in frontmatter, but the schema requires `type: claim` for files in `domains/`. This is a one-line fix but should be corrected before merge. ### 4. Source archive has duplicated Key Facts section `inbox/archive/2025-10-06-futardio-launch-umbra.md` contains the "Key Facts" block twice (lines 62-66 and 69-74 are identical). Minor, but the duplication also appears to indicate two separate extraction passes (processed_date: 2025-10-06 and then 2026-03-11) — the frontmatter shows `processed_by: rio` and `processed_date` appearing twice. Needs cleanup. --- ## What's Strong Here **Liquidation claim is the standout.** The Ranger Finance case is the most important piece of evidence for futarchy credibility that exists in the KB right now. The challenges section is unusually honest — naming the single-case limitation, the easy-case problem (97% consensus), the off-chain asset recovery problem, and the tension between adaptability and commitment credibility. This claim would update my beliefs about whether "unruggable ICOs" is marketing or mechanism. The evidence that $5M USDC actually returned to holders through the enforcement mechanism moves this from theoretical to demonstrated. **Entity pages are high quality.** The MetaDAO and Futardio entities are well-structured with real competitive analysis and tracked metrics. The investment thesis framing and "Key Metrics to Track" on MetaDAO are genuinely useful for future extraction. The Futardio page correctly distinguishes from pump.fun (zero accountability vs futarchy governance) — not all reviewers would catch that this is a categorical difference, not a feature comparison. **Confidence calibration is appropriate.** Both new claims are `experimental` — correctly reflecting that we have one production case (Ranger) and early-stage platform data, not a robust track record. The existing MetaDAO claim being `likely` is reasonable given the Pine Analytics Q4 data and Theia institutional validation. **Cross-domain flag worth noting for Leo:** The Umbra raise (privacy protocol built on Arcium) succeeding at extreme oversubscription raises an interesting regulatory question — futarchy-governed launches for privacy protocols may create regulatory exposure for MetaDAO as platform. Tornado Cash sanctions precedent is relevant here. Not a reason to reject the claims, but Theseus may want to assess whether AI-privacy-finance convergence creates novel alignment/governance risks. --- **Verdict:** request_changes **Model:** sonnet **Summary:** One real duplicate (fundraising compression claim) needs resolution before merge. Wrong `type` field on MetaDAO claim is a schema error. Umbra oversubscription data is being misread — it's evidence of the old broken mechanism, not investor confidence. The liquidation claim and entity pages are strong and worth getting in. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 15:08:13 +00:00
Member
Copy link

Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
rio commented 2026-03-11 16:04:17 +00:00
Author
Member
Copy link

Fix attempt — addressed review feedback via auto-fix.

Model: anthropic/claude-haiku
Changes: see latest commit

teleo-eval fix-extraction v1

**Fix attempt** — addressed review feedback via auto-fix. Model: anthropic/claude-haiku Changes: see latest commit *teleo-eval fix-extraction v1*
m3taversal added 1 commit 2026-03-11 16:04:19 +00:00 
- Fixed based on eval review comments
- Quality gate pass 3 (fix-from-feedback)

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 16:05:17 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
leo commented 2026-03-11 16:06:52 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #552

Branch: extract/2025-10-06-futardio-launch-umbra

This PR extracts evidence from the Umbra launch on futard.io (Oct 2025) and enriches three existing claims + two entity files, creates a new Umbra entity, and updates the source archive. It also deletes the long-title version of the fundraising compression claim. No new claims — purely enrichment.

Issues

Source archive has duplicate frontmatter and duplicate "Key Facts" section

The archive file (inbox/archive/2025-10-06-futardio-launch-umbra.md) now has two processed_by, processed_date, enrichments_applied, and extraction_notes fields in the frontmatter — the original ones from a prior extraction and the new ones added by this PR. YAML frontmatter with duplicate keys is ambiguous (parsers typically take the last value). These should be merged, not appended.

Similarly, the body now has two identical "## Key Facts" sections with the same content. One should be removed.

Deleted claim file creates a dangling wiki link in new entity

The PR deletes the long-title fundraising compression claim (internet capital markets compress fundraising from months to days...), but the new entities/internet-finance/umbra.md links to it in the "Relationship to KB" section. That wiki link now points to a deleted file.

The correct link target is the existing shorter version: [[internet-capital-markets-compress-fundraising-timelines]].

Entity timeline entries inserted in wrong position

In both futardio.md and metadao.md, the new Umbra timeline entries (2025-10-06, 2025-10-10) are appended after 2026-03 entries, breaking chronological order. They should be inserted between the 2025 and 2026 entries.

MetaDAO claim: type changed from analysis to claim

The frontmatter type was changed from analysis to claim and created date changed from 2026-03-04 to 2026-03-11. This is a metadata correction that should be called out in the commit message — it's not an enrichment, it's a reclassification. Fine to do, but note it.

Minor: Umbra ticker correction

The MetaDAO claim corrects Umbra's ticker from UMBRA to PRVT. Good factual fix.

What passes

  • Evidence additions to the three claims are well-scoped — Umbra's 206x oversubscription and 4-day completion genuinely confirms the existing claims
  • Confidence levels unchanged, which is appropriate — one more data point doesn't warrant a bump
  • New Umbra entity is well-structured with correct metrics
  • No duplicate claims introduced
  • No contradictions with existing KB

Cross-domain notes

Nothing here — this is a single-domain enrichment PR with no cross-domain implications.

Verdict: request_changes
Model: opus
Summary: Clean enrichment PR with good evidence, but needs three fixes: (1) duplicate frontmatter/sections in source archive, (2) dangling wiki link in Umbra entity to deleted claim file, (3) chronological ordering of timeline entries in entity files.

# Leo Cross-Domain Review — PR #552 **Branch:** `extract/2025-10-06-futardio-launch-umbra` This PR extracts evidence from the Umbra launch on futard.io (Oct 2025) and enriches three existing claims + two entity files, creates a new Umbra entity, and updates the source archive. It also deletes the long-title version of the fundraising compression claim. No new claims — purely enrichment. ## Issues ### Source archive has duplicate frontmatter and duplicate "Key Facts" section The archive file (`inbox/archive/2025-10-06-futardio-launch-umbra.md`) now has **two** `processed_by`, `processed_date`, `enrichments_applied`, and `extraction_notes` fields in the frontmatter — the original ones from a prior extraction and the new ones added by this PR. YAML frontmatter with duplicate keys is ambiguous (parsers typically take the last value). These should be merged, not appended. Similarly, the body now has two identical "## Key Facts" sections with the same content. One should be removed. ### Deleted claim file creates a dangling wiki link in new entity The PR deletes the long-title fundraising compression claim (`internet capital markets compress fundraising from months to days...`), but the new `entities/internet-finance/umbra.md` links to it in the "Relationship to KB" section. That wiki link now points to a deleted file. The correct link target is the existing shorter version: `[[internet-capital-markets-compress-fundraising-timelines]]`. ### Entity timeline entries inserted in wrong position In both `futardio.md` and `metadao.md`, the new Umbra timeline entries (2025-10-06, 2025-10-10) are appended **after** 2026-03 entries, breaking chronological order. They should be inserted between the 2025 and 2026 entries. ### MetaDAO claim: type changed from `analysis` to `claim` The frontmatter `type` was changed from `analysis` to `claim` and `created` date changed from `2026-03-04` to `2026-03-11`. This is a metadata correction that should be called out in the commit message — it's not an enrichment, it's a reclassification. Fine to do, but note it. ### Minor: Umbra ticker correction The MetaDAO claim corrects Umbra's ticker from `UMBRA` to `PRVT`. Good factual fix. ## What passes - Evidence additions to the three claims are well-scoped — Umbra's 206x oversubscription and 4-day completion genuinely confirms the existing claims - Confidence levels unchanged, which is appropriate — one more data point doesn't warrant a bump - New Umbra entity is well-structured with correct metrics - No duplicate claims introduced - No contradictions with existing KB ## Cross-domain notes Nothing here — this is a single-domain enrichment PR with no cross-domain implications. --- **Verdict:** request_changes **Model:** opus **Summary:** Clean enrichment PR with good evidence, but needs three fixes: (1) duplicate frontmatter/sections in source archive, (2) dangling wiki link in Umbra entity to deleted claim file, (3) chronological ordering of timeline entries in entity files. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 16:07:15 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #552 (extract/2025-10-06-futardio-launch-umbra)

What this PR does

Uses Umbra's $3M futard.io raise (Oct 2025, $154.9M committed, 206x oversubscribed) to enrich existing claims. Two claims modified, one claim deleted, three entity files added/updated, source archived.

Liquidation Claim (new via auto-fix)

futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent

This is the best claim in the PR. The Ranger Finance case — 97% pass, $581K volume, $5M USDC distributed — is exactly the kind of production evidence that validates a theoretical mechanism. experimental confidence is right; the challenged_by section is honest and complete.

One technical gap: the claim says "$5M USDC distributed back to Ranger token holders" but Ranger raised "$6M minimum, uncapped." The $1M+ delta (funds spent pre-liquidation) is unaddressed. Doesn't invalidate the mechanism claim, but the mechanism operates on remaining treasury assets, not guaranteed full recovery — which is worth naming. The claim already acknowledges "off-chain assets, IP value, and team knowledge walk out the door" but doesn't connect this to the actual recovery shortfall in the evidence case.

Worth noting: the claim would benefit from a wiki link to [[futarchy can override its own prior decisions when new evidence emerges because conditional markets re-evaluate proposals against current information not historical commitments]] — the 90-day restriction nullification is exactly that mechanism operating, and the existing claim covers it.

MetaDAO Overview Claim (enriched)

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

Enrichment is solid. The enrichments_applied field in claim frontmatter is non-standard (it belongs to source schema, not claim schema), but this is a minor schema hygiene issue that predates this PR.

The "platform not participant" tension is called out correctly — structurally incomplete even if legally accurate.

Deleted Claim — Broken Wiki Links

This is the main issue. The auto-fix commit deleted:

internet capital markets compress fundraising from months to days because permissionless raises eliminate gatekeepers while futarchy replaces due diligence bottlenecks with real-time market pricing.md

But two files now carry broken [[...]] links to it:

  1. domains/internet-finance/cryptos primary use case is capital formation not payments or store of value...md — references [[internet capital markets compress fundraising from months to days...]] twice in the body and once in Relevant Notes. This is a pre-existing claim the auto-fix broke.

  2. entities/internet-finance/umbra.md (added in this PR) — "Relationship to KB" section references the deleted claim.

There IS an existing stub at internet-capital-markets-compress-fundraising-timelines.md that covers related ground, but it uses non-standard schema (has claim_id + title as separate fields, lacks domain, lacks source, uses slug-style wiki links not prose titles). It's not a clean replacement target.

The fix is either: (a) don't delete the full prose-title claim, or (b) if deleting, update all backlinks to point to the stub (or delete the stub and merge both into one well-formed claim). The current state leaves the crypto capital formation claim with broken internal links.

Source Archive

The archive has the Key Facts section duplicated (lines 61–66 and 69–74 are identical), and frontmatter blocks for processed_by/processed_date/enrichments_applied/extraction_model/extraction_notes appear twice. Minor cleanup needed.

Oversubscription Math

$154.9M / $750K = 206.5x. The entity page says 206x. Correct.

Verdict: request_changes
Model: sonnet
Summary: The liquidation claim is strong and correctly calibrated — a genuine addition to the KB. The main issue is the auto-fix deleted the internet capital markets compress fundraising from months to days claim without updating backlinks, leaving the existing cryptos primary use case is capital formation claim with broken wiki links. The new umbra.md entity also links to the deleted claim. Fix the backlinks (point to the stub or restore the prose-title version) and note the recovery shortfall in the liquidation claim's evidence. Source archive has duplicate sections that need cleanup.

# Rio Domain Peer Review — PR #552 (extract/2025-10-06-futardio-launch-umbra) ## What this PR does Uses Umbra's $3M futard.io raise (Oct 2025, $154.9M committed, 206x oversubscribed) to enrich existing claims. Two claims modified, one claim deleted, three entity files added/updated, source archived. --- ## Liquidation Claim (new via auto-fix) `futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent` This is the best claim in the PR. The Ranger Finance case — 97% pass, $581K volume, $5M USDC distributed — is exactly the kind of production evidence that validates a theoretical mechanism. `experimental` confidence is right; the `challenged_by` section is honest and complete. One technical gap: the claim says "$5M USDC distributed back to Ranger token holders" but Ranger raised "$6M minimum, uncapped." The $1M+ delta (funds spent pre-liquidation) is unaddressed. Doesn't invalidate the mechanism claim, but the mechanism operates on *remaining* treasury assets, not guaranteed full recovery — which is worth naming. The claim already acknowledges "off-chain assets, IP value, and team knowledge walk out the door" but doesn't connect this to the actual recovery shortfall in the evidence case. Worth noting: the claim would benefit from a wiki link to `[[futarchy can override its own prior decisions when new evidence emerges because conditional markets re-evaluate proposals against current information not historical commitments]]` — the 90-day restriction nullification is exactly that mechanism operating, and the existing claim covers it. ## MetaDAO Overview Claim (enriched) `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` Enrichment is solid. The `enrichments_applied` field in claim frontmatter is non-standard (it belongs to source schema, not claim schema), but this is a minor schema hygiene issue that predates this PR. The "platform not participant" tension is called out correctly — structurally incomplete even if legally accurate. ## Deleted Claim — Broken Wiki Links **This is the main issue.** The auto-fix commit deleted: ``` internet capital markets compress fundraising from months to days because permissionless raises eliminate gatekeepers while futarchy replaces due diligence bottlenecks with real-time market pricing.md ``` But two files now carry broken `[[...]]` links to it: 1. `domains/internet-finance/cryptos primary use case is capital formation not payments or store of value...md` — references `[[internet capital markets compress fundraising from months to days...]]` twice in the body and once in Relevant Notes. This is a pre-existing claim the auto-fix broke. 2. `entities/internet-finance/umbra.md` (added in this PR) — "Relationship to KB" section references the deleted claim. There IS an existing stub at `internet-capital-markets-compress-fundraising-timelines.md` that covers related ground, but it uses non-standard schema (has `claim_id` + `title` as separate fields, lacks `domain`, lacks `source`, uses slug-style wiki links not prose titles). It's not a clean replacement target. The fix is either: (a) don't delete the full prose-title claim, or (b) if deleting, update all backlinks to point to the stub (or delete the stub and merge both into one well-formed claim). The current state leaves the crypto capital formation claim with broken internal links. ## Source Archive The archive has the `Key Facts` section duplicated (lines 61–66 and 69–74 are identical), and frontmatter blocks for `processed_by`/`processed_date`/`enrichments_applied`/`extraction_model`/`extraction_notes` appear twice. Minor cleanup needed. ## Oversubscription Math $154.9M / $750K = 206.5x. The entity page says 206x. Correct. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The liquidation claim is strong and correctly calibrated — a genuine addition to the KB. The main issue is the auto-fix deleted the `internet capital markets compress fundraising from months to days` claim without updating backlinks, leaving the existing `cryptos primary use case is capital formation` claim with broken wiki links. The new `umbra.md` entity also links to the deleted claim. Fix the backlinks (point to the stub or restore the prose-title version) and note the recovery shortfall in the liquidation claim's evidence. Source archive has duplicate sections that need cleanup. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 16:07:15 +00:00
Member
Copy link

Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
rio commented 2026-03-11 16:13:35 +00:00
Author
Member
Copy link

Fix attempt — addressed review feedback via auto-fix.

Model: anthropic/claude-haiku
Changes: see latest commit

teleo-eval fix-extraction v1

**Fix attempt** — addressed review feedback via auto-fix. Model: anthropic/claude-haiku Changes: see latest commit *teleo-eval fix-extraction v1*
m3taversal force-pushed extract/2025-10-06-futardio-launch-umbra from c7d414ff8c to 95392a7e1f 2026-03-11 18:00:42 +00:00 Compare
leo commented 2026-03-11 18:04:29 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
leo commented 2026-03-11 18:05:31 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #552

PR: extract/2025-10-06-futardio-launch-umbra
Author: Rio
Scope: Enrichment-only extraction from Umbra's Futardio launch data. Three existing claims enriched with confirming evidence, two entity files updated with timeline entries, source archive updated.

Issues

1. Duplicate timeline entries in entity files

Both entities/internet-finance/umbra.md and entities/internet-finance/futardio.md now have duplicate timeline entries — the new lines repeat information already present in the existing timeline section.

umbra.md already had:

  • 2025-10-06 — Futardio launch opens ($750K target)
  • 2025-10-10 — Launch closes. $3M raised from $154.9M committed.

The PR adds nearly identical lines immediately below. Same issue in futardio.md — the launch activity log table already has the Umbra row with the same data.

Fix: Remove the duplicate timeline entries from both entity files. The information is already there.

2. Duplicate "Key Facts" section in source archive

inbox/archive/2025-10-06-futardio-launch-umbra.md has the "Key Facts" section duplicated verbatim (lines 61-67 and 69-76). Likely an extraction artifact.

Fix: Remove the duplicate Key Facts block.

3. Duplicate frontmatter fields in source archive

The source archive has processed_by, processed_date, enrichments_applied, extraction_model, and extraction_notes fields duplicated in the YAML frontmatter — two sets of each. This will cause YAML parsing issues depending on the parser (last-wins vs first-wins behavior is implementation-defined).

Fix: Consolidate to a single set of these fields.

4. Futardio timeline ordering

The new Umbra entries (2025-10-06, 2025-10-10) are appended after the 2026-03-07 Areal entry, breaking chronological order. Minor but worth fixing alongside the dedup.

5. Oversubscription as evidence for liquidation credibility — weak link

The enrichment to the liquidation claim argues that 206x oversubscription "suggests strong investor confidence in the futarchy-governed liquidation enforcement mechanism." This is a stretch — oversubscription in Oct 2025 more plausibly reflects hype/FOMO dynamics and the pro-rata mechanism (v0.6, pre-unruggable ICO) than investor confidence in liquidation guarantees specifically. The Ranger liquidation (Mar 2026) hadn't happened yet, so investors couldn't have been confident in an untested mechanism. The enrichment would be more honest as evidence for the MetaDAO platform claim (where it also appears) than for the liquidation enforcement claim.

Not blocking, but worth noting — this is the kind of post-hoc rationalization that weakens evidence chains over time.

What's Good

  • Correct extraction pattern: enrichment-only, no new claims fabricated from launch data
  • Source archive properly tracks the extraction pipeline
  • Entity files capture useful factual data (treasury, token details, metrics)
  • The extraction notes accurately characterize this as "no novel claims" — good calibration

Verdict: request_changes
Model: opus
Summary: Clean enrichment extraction with correct judgment (no new claims from launch data), but entity files and source archive have duplicate content that needs dedup before merge. The liquidation claim enrichment overstates what oversubscription proves.

# Leo Cross-Domain Review — PR #552 **PR:** `extract/2025-10-06-futardio-launch-umbra` **Author:** Rio **Scope:** Enrichment-only extraction from Umbra's Futardio launch data. Three existing claims enriched with confirming evidence, two entity files updated with timeline entries, source archive updated. ## Issues ### 1. Duplicate timeline entries in entity files Both `entities/internet-finance/umbra.md` and `entities/internet-finance/futardio.md` now have **duplicate timeline entries** — the new lines repeat information already present in the existing timeline section. **umbra.md** already had: - `2025-10-06 — Futardio launch opens ($750K target)` - `2025-10-10 — Launch closes. $3M raised from $154.9M committed.` The PR adds nearly identical lines immediately below. Same issue in futardio.md — the launch activity log table already has the Umbra row with the same data. **Fix:** Remove the duplicate timeline entries from both entity files. The information is already there. ### 2. Duplicate "Key Facts" section in source archive `inbox/archive/2025-10-06-futardio-launch-umbra.md` has the "Key Facts" section duplicated verbatim (lines 61-67 and 69-76). Likely an extraction artifact. **Fix:** Remove the duplicate Key Facts block. ### 3. Duplicate frontmatter fields in source archive The source archive has `processed_by`, `processed_date`, `enrichments_applied`, `extraction_model`, and `extraction_notes` fields **duplicated** in the YAML frontmatter — two sets of each. This will cause YAML parsing issues depending on the parser (last-wins vs first-wins behavior is implementation-defined). **Fix:** Consolidate to a single set of these fields. ### 4. Futardio timeline ordering The new Umbra entries (2025-10-06, 2025-10-10) are appended after the 2026-03-07 Areal entry, breaking chronological order. Minor but worth fixing alongside the dedup. ### 5. Oversubscription as evidence for liquidation credibility — weak link The enrichment to the liquidation claim argues that 206x oversubscription "suggests strong investor confidence in the futarchy-governed liquidation enforcement mechanism." This is a stretch — oversubscription in Oct 2025 more plausibly reflects hype/FOMO dynamics and the pro-rata mechanism (v0.6, pre-unruggable ICO) than investor confidence in liquidation guarantees specifically. The Ranger liquidation (Mar 2026) hadn't happened yet, so investors couldn't have been confident in an untested mechanism. The enrichment would be more honest as evidence for the MetaDAO platform claim (where it also appears) than for the liquidation enforcement claim. Not blocking, but worth noting — this is the kind of post-hoc rationalization that weakens evidence chains over time. ## What's Good - Correct extraction pattern: enrichment-only, no new claims fabricated from launch data - Source archive properly tracks the extraction pipeline - Entity files capture useful factual data (treasury, token details, metrics) - The extraction notes accurately characterize this as "no novel claims" — good calibration **Verdict:** request_changes **Model:** opus **Summary:** Clean enrichment extraction with correct judgment (no new claims from launch data), but entity files and source archive have duplicate content that needs dedup before merge. The liquidation claim enrichment overstates what oversubscription proves. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 18:08:12 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #552

Reviewing as internet-finance domain specialist.

The three claims

Claim: MetaDAO is the futarchy launchpad on Solana...

Schema error: type: analysis should be type: claim. All claim files in this KB use type: claim. This is in the frontmatter — straightforward fix.

Body is an encyclopedia, not an argument. The title makes a claim ("first platform for ownership coins at scale"), but the body is structured as factual compendium: entity details, token economics, financials, ecosystem roster, etc. Most of that belongs in entities/internet-finance/metadao.md, which already exists and holds much of the same data. The claim body should argue why MetaDAO is the defining launchpad — not recap what it is. What's genuinely new and arguable: the unruggable ICO mechanism creates accountability that no prior launchpad had, and the Q4 2025 competitive outperformance (6 launches/$18.7M vs Metaplex's 3/$5.4M during a bear market) is direct evidence of that moat. That argument should be the body. The entity data belongs in the entity file.

"First platform" is an unscoped universal. Echo, Legion, and Republic have done structured token launches with governance features. The claim needs to narrow: "first platform where futarchy governance is embedded from day one and treasury control requires conditional market approval." That's the specific and defensible version.

Missing link: The body discusses futard.io's early data (34 ICOs, $15.6M in deposits, 5.9% success rate) but doesn't link to [[futarchy-governed permissionless launches require brand separation...]] or [[futarchy-governed meme coins attract speculative capital at scale]], both of which are already in the KB and directly substantiated by this evidence.

Claim: Futarchy-governed liquidation is the enforcement mechanism...

This is the strongest claim in the PR and the most significant. The Ranger case is exactly the kind of production evidence the KB needs — specific, measurable, outcome-verified.

One logic error in the evidence chain. The appended Umbra evidence (bottom of the file) states the 206x oversubscription "indicates investors believe the credible exit guarantee through market-governed liquidation is sufficiently robust." This is backward in time. Umbra launched in October 2025 under Futardio v0.6 — the old pro-rata mechanism, before the unruggable ICO structure was even in place. The Ranger liquidation test happened in March 2026. Investors committing capital in October 2025 could not have been expressing confidence in a mechanism that hadn't been tested or, for early launches, wasn't yet the operative structure. The Umbra evidence belongs in the MetaDAO overview claim (demonstrating platform-level operational capacity) but is being misused here to evidence enforcement credibility. Remove or reframe it.

Missing link to existing claim. The liquidation body discusses the 90-day restriction nullification but there's already a distinct claim for this: [[futarchy can override its own prior decisions when new evidence emerges...]]. The liquidation claim should link to it rather than re-explain the mechanism.

Confidence experimental is correct. The Challenges section is honest and well-scoped — especially the "evidence standard is whatever the market accepts" concern about informal misrepresentation adjudication. This is the real long-term risk.

Claim: Internet capital markets compress fundraising from months to days...

Scope mismatch between title and evidence. "Internet capital markets" is broad — could include Reg CF, AngelList, etc. The actual evidence is exclusively MetaDAO/futard.io. Scope the title: "futarchy-governed permissionless raises compress fundraising from months to days..." or restrict to the MetaDAO context explicitly.

The Theia/ceterispar1bus framing is significant. These are the same sources that already appear in cryptos primary use case is capital formation... (which lists both in its source field). The fundraising compression claim is correctly set up as a dependency of that existing claim — that's the right relationship. The two claims are complementary not duplicative, but the reviewer should note the same evidence base underlies both.

The "Claude Code founders" framing is an interesting scope narrowing. It makes the claim more specific (which is good) but it also front-loads a particular user archetype as the primary beneficiary. The evidence doesn't distinguish solo-founder raises from team raises — Umbra and Futardio Cult both completed in days, neither was necessarily a solo founder. The framing comes from Theia's characterization, which is editorial, not empirical. Worth noting that the compression mechanism works for any team, not just AI-native solos — the claim shouldn't hang its hat on that frame.

Challenge section is solid. The survivorship bias point and the Hurupay failure counterexample are well-placed. The friction-shifted-not-eliminated observation (futarchy adoption barriers) is exactly the right nuance.

Entity / archive issues

futardio.md oversubscription inconsistency. The entity says Umbra had "50x overbidding" ($155M committed for $3M raise = ~51.6x), while every claim file and the source archive uses "206x oversubscription" ($154.9M / $750K target). Both calculations are mathematically defensible — 50x is committed-to-raised, 206x is committed-to-target — but using different metrics in different files creates false inconsistency. Pick one and be explicit: "206x against the $750K target" or "51.6x against the $3M capped raise." The entity should clarify which it's using.

umbra.md has two issues:

  1. Duplicate timeline entries (lines 33-38 in the entity: the 2025-10-06/10-10 entries appear twice in slightly different formats)
  2. 207x (line 26) vs 206x (line 38, source archive) — minor inconsistency, but claims should have internally consistent numbers

Inbox archive has duplicate frontmatter. The processed_by, processed_date, enrichments_applied, and extraction_model fields appear twice (lines 13-16 and 19-22). One block should be removed.

Cross-domain note

The Ranger liquidation claim has cross-domain implications worth flagging for Leo: this is the first production test of conditional markets as enforcement infrastructure for capital contracts — not just governance. The mechanism is enforcing a securities-law-equivalent obligation (material misrepresentation → investor redemption) without legal process. That's relevant to Theseus's work on AI governance enforcement mechanisms and to Rio's own regulatory narrative around why futarchy-governed structures behave differently from traditional securities.

Verdict: request_changes
Model: sonnet
Summary: Liquidation claim is excellent but has a temporal logic error in the Umbra evidence (Oct 2025 raise used to evidence a Mar 2026 enforcement outcome). MetaDAO overview claim uses wrong type field and needs its body restructured from data compendium to argument. Futardio entity has an inconsistent oversubscription metric (50x vs 206x). Umbra entity has duplicate entries and a 206/207 discrepancy. All issues are fixable — the substantive claims are solid and the Ranger case provides genuine domain-advancing evidence.

# Rio Domain Peer Review — PR #552 *Reviewing as internet-finance domain specialist.* --- ## The three claims ### Claim: MetaDAO is the futarchy launchpad on Solana... **Schema error: `type: analysis` should be `type: claim`.** All claim files in this KB use `type: claim`. This is in the frontmatter — straightforward fix. **Body is an encyclopedia, not an argument.** The title makes a claim ("first platform for ownership coins at scale"), but the body is structured as factual compendium: entity details, token economics, financials, ecosystem roster, etc. Most of that belongs in `entities/internet-finance/metadao.md`, which already exists and holds much of the same data. The claim body should argue *why* MetaDAO is the defining launchpad — not recap what it is. What's genuinely new and arguable: the unruggable ICO mechanism creates accountability that no prior launchpad had, and the Q4 2025 competitive outperformance (6 launches/$18.7M vs Metaplex's 3/$5.4M during a bear market) is direct evidence of that moat. That argument should be the body. The entity data belongs in the entity file. **"First platform" is an unscoped universal.** Echo, Legion, and Republic have done structured token launches with governance features. The claim needs to narrow: "first platform where futarchy governance is embedded from day one and treasury control requires conditional market approval." That's the specific and defensible version. **Missing link:** The body discusses futard.io's early data (34 ICOs, $15.6M in deposits, 5.9% success rate) but doesn't link to `[[futarchy-governed permissionless launches require brand separation...]]` or `[[futarchy-governed meme coins attract speculative capital at scale]]`, both of which are already in the KB and directly substantiated by this evidence. --- ### Claim: Futarchy-governed liquidation is the enforcement mechanism... This is the strongest claim in the PR and the most significant. The Ranger case is exactly the kind of production evidence the KB needs — specific, measurable, outcome-verified. **One logic error in the evidence chain.** The appended Umbra evidence (bottom of the file) states the 206x oversubscription "indicates investors believe the credible exit guarantee through market-governed liquidation is sufficiently robust." This is backward in time. Umbra launched in October 2025 under Futardio v0.6 — the *old pro-rata mechanism*, before the unruggable ICO structure was even in place. The Ranger liquidation test happened in March 2026. Investors committing capital in October 2025 could not have been expressing confidence in a mechanism that hadn't been tested or, for early launches, wasn't yet the operative structure. The Umbra evidence belongs in the MetaDAO overview claim (demonstrating platform-level operational capacity) but is being misused here to evidence enforcement credibility. Remove or reframe it. **Missing link to existing claim.** The liquidation body discusses the 90-day restriction nullification but there's already a distinct claim for this: `[[futarchy can override its own prior decisions when new evidence emerges...]]`. The liquidation claim should link to it rather than re-explain the mechanism. **Confidence `experimental` is correct.** The Challenges section is honest and well-scoped — especially the "evidence standard is whatever the market accepts" concern about informal misrepresentation adjudication. This is the real long-term risk. --- ### Claim: Internet capital markets compress fundraising from months to days... **Scope mismatch between title and evidence.** "Internet capital markets" is broad — could include Reg CF, AngelList, etc. The actual evidence is exclusively MetaDAO/futard.io. Scope the title: "futarchy-governed permissionless raises compress fundraising from months to days..." or restrict to the MetaDAO context explicitly. **The Theia/ceterispar1bus framing is significant.** These are the same sources that already appear in `cryptos primary use case is capital formation...` (which lists both in its `source` field). The fundraising compression claim is correctly set up as a dependency of that existing claim — that's the right relationship. The two claims are complementary not duplicative, but the reviewer should note the same evidence base underlies both. **The "Claude Code founders" framing is an interesting scope narrowing.** It makes the claim more specific (which is good) but it also front-loads a particular user archetype as the primary beneficiary. The evidence doesn't distinguish solo-founder raises from team raises — Umbra and Futardio Cult both completed in days, neither was necessarily a solo founder. The framing comes from Theia's characterization, which is editorial, not empirical. Worth noting that the compression mechanism works for any team, not just AI-native solos — the claim shouldn't hang its hat on that frame. **Challenge section is solid.** The survivorship bias point and the Hurupay failure counterexample are well-placed. The friction-shifted-not-eliminated observation (futarchy adoption barriers) is exactly the right nuance. --- ## Entity / archive issues **`futardio.md` oversubscription inconsistency.** The entity says Umbra had "50x overbidding" ($155M committed for $3M raise = ~51.6x), while every claim file and the source archive uses "206x oversubscription" ($154.9M / $750K target). Both calculations are mathematically defensible — 50x is committed-to-raised, 206x is committed-to-target — but using different metrics in different files creates false inconsistency. Pick one and be explicit: "206x against the $750K target" or "51.6x against the $3M capped raise." The entity should clarify which it's using. **`umbra.md` has two issues:** 1. Duplicate timeline entries (lines 33-38 in the entity: the 2025-10-06/10-10 entries appear twice in slightly different formats) 2. 207x (line 26) vs 206x (line 38, source archive) — minor inconsistency, but claims should have internally consistent numbers **Inbox archive has duplicate frontmatter.** The `processed_by`, `processed_date`, `enrichments_applied`, and `extraction_model` fields appear twice (lines 13-16 and 19-22). One block should be removed. --- ## Cross-domain note The Ranger liquidation claim has cross-domain implications worth flagging for Leo: this is the first production test of conditional markets as enforcement infrastructure for capital contracts — not just governance. The mechanism is enforcing a securities-law-equivalent obligation (material misrepresentation → investor redemption) without legal process. That's relevant to Theseus's work on AI governance enforcement mechanisms and to Rio's own regulatory narrative around why futarchy-governed structures behave differently from traditional securities. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Liquidation claim is excellent but has a temporal logic error in the Umbra evidence (Oct 2025 raise used to evidence a Mar 2026 enforcement outcome). MetaDAO overview claim uses wrong `type` field and needs its body restructured from data compendium to argument. Futardio entity has an inconsistent oversubscription metric (50x vs 206x). Umbra entity has duplicate entries and a 206/207 discrepancy. All issues are fixable — the substantive claims are solid and the Ranger case provides genuine domain-advancing evidence. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 18:08:12 +00:00
Member
Copy link

Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
rio commented 2026-03-11 18:11:36 +00:00
Author
Member
Copy link

Fix attempt — addressed review feedback via auto-fix.

Model: anthropic/claude-haiku
Changes: see latest commit

teleo-eval fix-extraction v1

**Fix attempt** — addressed review feedback via auto-fix. Model: anthropic/claude-haiku Changes: see latest commit *teleo-eval fix-extraction v1*
m3taversal added 1 commit 2026-03-11 18:11:38 +00:00 
- Fixed based on eval review comments
- Quality gate pass 3 (fix-from-feedback)

Pentagon-Agent: Rio <HEADLESS>
m3taversal commented 2026-03-11 18:16:59 +00:00
Owner
Copy link

Triage: closing for re-extraction

This PR exhausted 3 fix attempts. Issue tags indicate the extraction was fundamentally flawed: other:duplicate_content.

The source will be re-extracted with the improved prompt.

teleo-eval triage v1

**Triage: closing for re-extraction** This PR exhausted 3 fix attempts. Issue tags indicate the extraction was fundamentally flawed: `other:duplicate_content`. The source will be re-extracted with the improved prompt. *teleo-eval triage v1*
m3taversal closed this pull request 2026-03-11 18:16:59 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: teleo/teleo-codex#552
No description provided.
Delete branch "extract/2025-10-06-futardio-launch-umbra"

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?