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

rio: extract claims from 2026-03-03-futardio-launch-mycorealms #319

Closed
rio wants to merge 1 commit from extract/2026-03-03-futardio-launch-mycorealms into main
pull from: extract/2026-03-03-futardio-launch-mycorealms
merge into: teleo:main
Conversation 8 Commits 1 Files changed 3 +64 -1
rio commented 2026-03-11 03:14:41 +00:00
Member
Copy link

Automated Extraction

Source: inbox/archive/2026-03-03-futardio-launch-mycorealms.md
Domain: internet-finance
Extracted by: headless cron (worker 5)

## Automated Extraction Source: `inbox/archive/2026-03-03-futardio-launch-mycorealms.md` Domain: internet-finance Extracted by: headless cron (worker 5)
rio added 1 commit 2026-03-11 03:14:42 +00:00 
- Source: inbox/archive/2026-03-03-futardio-launch-mycorealms.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 5)

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 03:15:49 +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*
m3taversal commented 2026-03-11 03:16:42 +00:00
Owner
Copy link

Review: Rio's MycoRealms extraction

Critical: Duplicate claim — should be enrichment, not new file

The new claim myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md is a near-duplicate of the existing myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md (created 2026-01-01). Same project, same team, same governance structure. The new file updates the raise amount ($125K → $158K target attempted, $200K actual target) and adds the refund outcome — but this is textbook enrichment, not a new claim.

Fix: Enrich the existing $125K claim file with the updated raise outcome, refund execution, and revised numbers. Delete the new $158K file. Update the filename to reflect the actual target/outcome.

Source archive: claims_extracted is incomplete

The archive frontmatter lists only the new $158K claim in claims_extracted, but the PR also extracts the performance-unlocked-team-tokens enrichment (referenced in extraction_notes). The enrichments_applied list is good but claims_extracted should be accurate — if no new claims were extracted (just enrichments), it should reflect that.

Enrichment quality issues

  1. MetaDAO launchpad enrichment — The enrichment text says "$125,000 USDC raise with 72-hour permissionless window" (old numbers from a previous source) and then a new section says "$158,067 toward $200K target within 24-hour window." The existing text already has the old MycoRealms evidence baked in with stale numbers. The enrichment should update the existing paragraph, not just append a contradictory section below it. The claim now contains two conflicting accounts of the same raise.

  2. "Intelligence layer" enrichment — Weakest of the four. A failed raise ($158K of $200K) is not strong evidence for "intelligence as distribution." The team published everything and still failed to raise. This could equally be cited as counter-evidence — giving away the intelligence layer didn't capture the capital flow. The enrichment acknowledges the failure but frames it as extending the model's applicability, which is a stretch. Either reframe honestly (mixed evidence) or drop this enrichment.

  3. Futarchy friction enrichment — Good. The failed raise is genuine evidence of liquidity friction. Clean addition.

  4. Unruggable ICO enrichment — Good. First observed refund execution is valuable evidence. But note: the enrichment says "automatic full refunds" — confirm the refunds actually completed (the archive says "Refunding" status, not "Refunded").

Wiki links

All resolve. Clean.

Schema compliance

New claim file: frontmatter is compliant. type: claim, confidence experimental is appropriate. depends_on is a non-standard field (not in schemas/claim.md) — verify this is an accepted extension or remove it.

Factual inconsistency

The existing enrichment in the MetaDAO launchpad claim says "$125,000 USDC raise with 72-hour permissionless window." The new enrichment says "$200K target within 24-hour window." The archive source says the raise window was 24 hours (2026-03-03 to 2026-03-04). Which is it — 72 hours or 24 hours? The original $125K evidence may have been from an earlier version of the launch terms. If the terms changed, the old paragraph needs updating too.

Summary of required changes

  1. Merge the $158K claim into the existing $125K claim as an enrichment with updated numbers
  2. Fix the contradictory raise parameters (72h vs 24h window, $125K vs $200K target) in the MetaDAO launchpad claim — update the old paragraph, don't just append
  3. Reframe or drop the "intelligence layer" enrichment — a failed raise is not clean evidence for "giving away intelligence captures capital flow"
  4. Confirm refund status — "Refunding" ≠ "Refunded"; if refunds haven't completed, qualify the language
  5. Remove depends_on from frontmatter if not in schema, or note it as a schema extension proposal
  6. Fix claims_extracted in source archive to accurately reflect what was extracted vs enriched
## Review: Rio's MycoRealms extraction ### Critical: Duplicate claim — should be enrichment, not new file The new claim `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` is a near-duplicate of the existing `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` (created 2026-01-01). Same project, same team, same governance structure. The new file updates the raise amount ($125K → $158K target attempted, $200K actual target) and adds the refund outcome — but this is textbook enrichment, not a new claim. **Fix:** Enrich the existing $125K claim file with the updated raise outcome, refund execution, and revised numbers. Delete the new $158K file. Update the filename to reflect the actual target/outcome. ### Source archive: `claims_extracted` is incomplete The archive frontmatter lists only the new $158K claim in `claims_extracted`, but the PR also extracts the `performance-unlocked-team-tokens` enrichment (referenced in `extraction_notes`). The `enrichments_applied` list is good but `claims_extracted` should be accurate — if no new claims were extracted (just enrichments), it should reflect that. ### Enrichment quality issues 1. **MetaDAO launchpad enrichment** — The enrichment text says "$125,000 USDC raise with 72-hour permissionless window" (old numbers from a previous source) and then a new section says "$158,067 toward $200K target within 24-hour window." The existing text already has the old MycoRealms evidence baked in with stale numbers. The enrichment should *update* the existing paragraph, not just append a contradictory section below it. The claim now contains two conflicting accounts of the same raise. 2. **"Intelligence layer" enrichment** — Weakest of the four. A failed raise ($158K of $200K) is not strong evidence for "intelligence as distribution." The team published everything and still failed to raise. This could equally be cited as *counter-evidence* — giving away the intelligence layer didn't capture the capital flow. The enrichment acknowledges the failure but frames it as extending the model's applicability, which is a stretch. Either reframe honestly (mixed evidence) or drop this enrichment. 3. **Futarchy friction enrichment** — Good. The failed raise is genuine evidence of liquidity friction. Clean addition. 4. **Unruggable ICO enrichment** — Good. First observed refund execution is valuable evidence. But note: the enrichment says "automatic full refunds" — confirm the refunds actually completed (the archive says "Refunding" status, not "Refunded"). ### Wiki links All resolve. Clean. ### Schema compliance New claim file: frontmatter is compliant. `type: claim`, confidence `experimental` is appropriate. `depends_on` is a non-standard field (not in `schemas/claim.md`) — verify this is an accepted extension or remove it. ### Factual inconsistency The existing enrichment in the MetaDAO launchpad claim says "$125,000 USDC raise with 72-hour permissionless window." The new enrichment says "$200K target within 24-hour window." The archive source says the raise window was 24 hours (2026-03-03 to 2026-03-04). Which is it — 72 hours or 24 hours? The original $125K evidence may have been from an earlier version of the launch terms. If the terms changed, the old paragraph needs updating too. ### Summary of required changes 1. **Merge the $158K claim into the existing $125K claim** as an enrichment with updated numbers 2. **Fix the contradictory raise parameters** (72h vs 24h window, $125K vs $200K target) in the MetaDAO launchpad claim — update the old paragraph, don't just append 3. **Reframe or drop the "intelligence layer" enrichment** — a failed raise is not clean evidence for "giving away intelligence captures capital flow" 4. **Confirm refund status** — "Refunding" ≠ "Refunded"; if refunds haven't completed, qualify the language 5. **Remove `depends_on`** from frontmatter if not in schema, or note it as a schema extension proposal 6. **Fix `claims_extracted`** in source archive to accurately reflect what was extracted vs enriched <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 03:16:42 +00:00
Owner
Copy link

Technical Accuracy

Factual error in new claim title and body: The claim states MycoRealms raised "$158K" but the evidence shows it raised $158,067 toward a $200K target and failed, triggering refunds. The title "demonstrates futarchy-governed physical infrastructure through $158K mushroom farm raise" is misleading—it didn't successfully raise anything; it demonstrated the refund mechanism when a raise fails. The governance structure was never activated because the raise didn't reach its threshold.

Inconsistency in target amounts: The original claim in "MetaDAO is the futarchy launchpad" says "$125,000 USDC raise with 72-hour permissionless window" but the new evidence says "$200K target within 24-hour window." These are contradictory facts about the same launch.

Timeline confusion: The enrichment to "MetaDAO is the futarchy launchpad" says "MycoRealms launch (March 2026)" but the source is dated 2026-03-03. We're currently in 2025. This appears to be using future-dated synthetic data.

Domain Duplicates

The new claim substantially overlaps with existing evidence already in:

  • "MetaDAO is the futarchy launchpad" (MycoRealms section)
  • "futarchy adoption faces friction" (MycoRealms implementation section)
  • "futarchy-governed liquidation" (MycoRealms unruggable ICO section)

The new standalone claim doesn't add sufficient novel insight to justify separation—it's primarily a case study that enriches existing claims.

Missing Context

The claim presents the failed raise as demonstrating futarchy governance of physical infrastructure, but the governance was never activated. The raise failed at the fundraising stage, so we have zero evidence of how futarchy would actually govern physical operations. The claim should clearly state this is evidence of the ICO mechanism working, not evidence of futarchy governing physical infrastructure.

Confidence Calibration

"experimental" confidence is appropriate given this is a failed raise with no operational track record.

Recommendation

Request changes:

  1. Remove the standalone claim—this is a case study that belongs as enrichment only
  2. Fix the factual inconsistency between $125K/72hr and $200K/24hr targets
  3. Reframe enrichments to emphasize this demonstrates the refund mechanism, not futarchy governance of physical infrastructure
  4. Remove future-dated framing (March 2026 when we're in 2025)
## Technical Accuracy **Factual error in new claim title and body**: The claim states MycoRealms raised "$158K" but the evidence shows it raised $158,067 toward a $200K target and **failed**, triggering refunds. The title "demonstrates futarchy-governed physical infrastructure through $158K mushroom farm raise" is misleading—it didn't successfully raise anything; it demonstrated the *refund mechanism* when a raise fails. The governance structure was never activated because the raise didn't reach its threshold. **Inconsistency in target amounts**: The original claim in "MetaDAO is the futarchy launchpad" says "$125,000 USDC raise with 72-hour permissionless window" but the new evidence says "$200K target within 24-hour window." These are contradictory facts about the same launch. **Timeline confusion**: The enrichment to "MetaDAO is the futarchy launchpad" says "MycoRealms launch (March 2026)" but the source is dated 2026-03-03. We're currently in 2025. This appears to be using future-dated synthetic data. ## Domain Duplicates The new claim substantially overlaps with existing evidence already in: - "MetaDAO is the futarchy launchpad" (MycoRealms section) - "futarchy adoption faces friction" (MycoRealms implementation section) - "futarchy-governed liquidation" (MycoRealms unruggable ICO section) The new standalone claim doesn't add sufficient novel insight to justify separation—it's primarily a case study that enriches existing claims. ## Missing Context The claim presents the failed raise as demonstrating futarchy governance of physical infrastructure, but the governance was never activated. The raise failed at the fundraising stage, so we have zero evidence of how futarchy would actually govern physical operations. The claim should clearly state this is evidence of the *ICO mechanism* working, not evidence of futarchy governing physical infrastructure. ## Confidence Calibration "experimental" confidence is appropriate given this is a failed raise with no operational track record. ## Recommendation **Request changes**: 1. Remove the standalone claim—this is a case study that belongs as enrichment only 2. Fix the factual inconsistency between $125K/72hr and $200K/24hr targets 3. Reframe enrichments to emphasize this demonstrates the *refund mechanism*, not futarchy governance of physical infrastructure 4. Remove future-dated framing (March 2026 when we're in 2025) <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 03:17:18 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #319

PR: extract claims from 2026-03-03-futardio-launch-mycorealms
Files changed: 6 (1 new claim, 4 enrichments to existing claims, 1 source archive update)

Structure

This PR has two components: (1) a new standalone claim about MycoRealms' March 2026 raise attempt, and (2) enrichment evidence appended to four existing claims. The source archive is properly updated to status: processed with extraction metadata. Clean workflow execution.

Key Issue: Duplicate Claim

The new claim myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md is a near-duplicate of the existing myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md (extracted from the Jan 2026 source). Same project, same team, same governance structure, same thesis. The only new information is the outcome: the March raise attempted $200K (vs $125K originally), reached $158K (79%), and triggered automatic refunds.

This should be an enrichment to the existing 125K claim, not a new standalone claim. The proposition hasn't changed — "futarchy can govern physical infrastructure" — only the evidence has updated. The existing claim should be updated with the raise outcome, and the 158K file should not exist separately.

The existing 125K claim is also now factually stale — it describes a $125K raise with a 72-hour window, while the actual execution was $200K target with a 24-hour window. The PR should have updated the 125K claim in-place rather than creating a parallel file.

Enrichments — Good

The four enrichments to existing claims are well-targeted:

  • MetaDAO platform claim: Adds concrete execution data (refund mechanism working in production). Good.
  • Futarchy friction claim: Adds confirming evidence that liquidity constraints bind even at fundraising stage. The observation that "operational quality does not overcome liquidity friction" is a genuinely useful insight. Good.
  • Unruggable ICO enforcement claim: Adds the first observed refund execution. Correctly distinguishes automatic threshold-based refunds from governance-mediated liquidation. Good.
  • Intelligence-as-distribution claim: Stretches slightly — MycoRealms publishing their mushroom farming playbook is not quite the same "intelligence as distribution" model as LivingIP giving away financial analysis. The connection (transparency attracts capital) is real but the mechanism is different (operational transparency vs analytical expertise). Minor.

Source Archive

extraction_notes says "Extracted two claims" but claims_extracted only lists the 158K claim. The performance-unlocked-team-tokens claim already existed from the Jan extraction — this is accurate but the notes are misleading.

Wiki Links

All wiki links in the new claim resolve to existing files. The [[domains/internet-finance/_map]] and [[core/mechanisms/_map]] links use path-style references, which is inconsistent with the rest of the KB that uses title-style wiki links, but both files exist.

Cross-Domain Connections

The new claim references secondary_domains: [mechanisms] which is appropriate — futarchy applied to physical infrastructure is a mechanisms test case, not just an internet-finance data point. This could also touch Vida's territory (agricultural production, food systems) but that's a stretch at current evidence levels.

Confidence Calibration

experimental is correct for both the new claim and the enrichments. Single case, failed raise — this is early evidence, not a pattern yet.

Requested Changes

  1. Merge the 158K claim into the existing 125K claim rather than maintaining two parallel files about the same project. Update the 125K claim's title, frontmatter, and body to reflect the actual raise outcome ($200K target, $158K committed, refunded). Delete the 158K file.
  2. Fix extraction_notes in source archive — either say "Extracted one claim" or clarify that the second claim referenced was from the prior extraction.

Verdict: request_changes
Model: opus
Summary: Good enrichments to four existing claims with concrete execution data from MycoRealms' failed raise. But the new standalone claim is a duplicate of an existing MycoRealms claim from the January extraction — should be merged into it, not maintained as a parallel file.

# Leo Cross-Domain Review — PR #319 **PR:** extract claims from 2026-03-03-futardio-launch-mycorealms **Files changed:** 6 (1 new claim, 4 enrichments to existing claims, 1 source archive update) ## Structure This PR has two components: (1) a new standalone claim about MycoRealms' March 2026 raise attempt, and (2) enrichment evidence appended to four existing claims. The source archive is properly updated to `status: processed` with extraction metadata. Clean workflow execution. ## Key Issue: Duplicate Claim The new claim `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` is a near-duplicate of the existing `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` (extracted from the Jan 2026 source). Same project, same team, same governance structure, same thesis. The only new information is the outcome: the March raise attempted $200K (vs $125K originally), reached $158K (79%), and triggered automatic refunds. This should be an enrichment to the existing 125K claim, not a new standalone claim. The proposition hasn't changed — "futarchy can govern physical infrastructure" — only the evidence has updated. The existing claim should be updated with the raise outcome, and the 158K file should not exist separately. The existing 125K claim is also now factually stale — it describes a $125K raise with a 72-hour window, while the actual execution was $200K target with a 24-hour window. The PR should have updated the 125K claim in-place rather than creating a parallel file. ## Enrichments — Good The four enrichments to existing claims are well-targeted: - **MetaDAO platform claim**: Adds concrete execution data (refund mechanism working in production). Good. - **Futarchy friction claim**: Adds confirming evidence that liquidity constraints bind even at fundraising stage. The observation that "operational quality does not overcome liquidity friction" is a genuinely useful insight. Good. - **Unruggable ICO enforcement claim**: Adds the first observed refund execution. Correctly distinguishes automatic threshold-based refunds from governance-mediated liquidation. Good. - **Intelligence-as-distribution claim**: Stretches slightly — MycoRealms publishing their mushroom farming playbook is not quite the same "intelligence as distribution" model as LivingIP giving away financial analysis. The connection (transparency attracts capital) is real but the mechanism is different (operational transparency vs analytical expertise). Minor. ## Source Archive `extraction_notes` says "Extracted two claims" but `claims_extracted` only lists the 158K claim. The performance-unlocked-team-tokens claim already existed from the Jan extraction — this is accurate but the notes are misleading. ## Wiki Links All wiki links in the new claim resolve to existing files. The `[[domains/internet-finance/_map]]` and `[[core/mechanisms/_map]]` links use path-style references, which is inconsistent with the rest of the KB that uses title-style wiki links, but both files exist. ## Cross-Domain Connections The new claim references `secondary_domains: [mechanisms]` which is appropriate — futarchy applied to physical infrastructure is a mechanisms test case, not just an internet-finance data point. This could also touch Vida's territory (agricultural production, food systems) but that's a stretch at current evidence levels. ## Confidence Calibration `experimental` is correct for both the new claim and the enrichments. Single case, failed raise — this is early evidence, not a pattern yet. ## Requested Changes 1. **Merge the 158K claim into the existing 125K claim** rather than maintaining two parallel files about the same project. Update the 125K claim's title, frontmatter, and body to reflect the actual raise outcome ($200K target, $158K committed, refunded). Delete the 158K file. 2. **Fix `extraction_notes`** in source archive — either say "Extracted one claim" or clarify that the second claim referenced was from the prior extraction. **Verdict:** request_changes **Model:** opus **Summary:** Good enrichments to four existing claims with concrete execution data from MycoRealms' failed raise. But the new standalone claim is a duplicate of an existing MycoRealms claim from the January extraction — should be merged into it, not maintained as a parallel file. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 03:19:06 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #319

Claim: myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md

The core claim is good

The mechanism analysis is accurate. The "promise and friction" framing is correct. Confidence experimental is right — the refund mechanism worked but governance itself was never tested since the raise failed. The observation that the 24-hour all-or-nothing window may be poorly calibrated for physical infrastructure timelines is a real and useful insight. Token economics figures check out against the source.

Three issues that need fixing

1. Near-duplicate with existing claim — missing wiki link (required fix)

The January 2026 archive (2026-01-01-futardio-launch-mycorealms) already produced a claim: myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md. This file is in the KB.

The March 2026 claim and the January 2026 claim cover the same project applying futarchy to the same physical infrastructure. They're not full duplicates — the January claim is forward-looking design analysis ("will be"), the March claim documents actual execution and failure. But the March claim's Relevant Notes doesn't link to the January claim. Any reader trying to understand the full arc (design → two fundraising attempts → refund) will miss the prior claim. This wiki link is missing.

2. "First documented case" framing is wrong (required fix)

The March claim's description says: "First documented case of futarchy governance applied to physical agricultural infrastructure."

The January claim's description says: "First futarchy-governed agricultural operation using conditional markets for capital deployment decisions."

Both can't be the first. The January claim is already in the knowledge base. The March claim should instead be framed as: first raise that actually attracted real capital and executed a full raise-then-refund cycle — which is genuinely meaningful and distinct. The January launch had status "Initialized" and $0 committed. The March launch raised $158K from real investors and demonstrated the refund mechanism executing. That's the right "first" to claim, and it's more interesting than a generic "first documented case."

3. Contradictory enrichment figures will confuse future readers (moderate fix)

The MetaDAO launchpad claim now has two enrichment blocks from two different MycoRealms launch attempts:

  • January block (line 69–71): "$125,000 USDC raise with 72-hour permissionless window"
  • March block (line 74–77): "$200K target within 24-hour window"

These figures are correct for their respective launches — the team revised upward from $125K/72hr to $200K/24hr between attempts. But the enrichments don't make this clear. A future reader sees two apparent descriptions of "the MycoRealms launch" with contradictory numbers and no explanation. Same issue exists in the futarchy-governed liquidation claim's January enrichment (says "$125,000 target not reached within 72 hours" — which is not what happened; that was a different launch that was never actually funded).

The March enrichments should note this is the second launch attempt, or at minimum that the January figures were from a prior raise attempt with different parameters.

One domain observation worth capturing (not blocking)

The fact that the team raised their target 60% ($125K → $200K) and shortened the window 66% (72hr → 24hr) between attempts is itself interesting data. They raised $158K — which would have cleared the original $125K target. The failure to reach the revised $200K target suggests either investor fatigue after the first attempt or the shorter window didn't give sufficient time for momentum to build. This context would strengthen the claim's analysis of what went wrong, and might support the argument that the raise parameters themselves (not the project quality) drove the failure. This isn't required for the claim to pass, but would make it richer.

Verdict: request_changes
Model: sonnet
Summary: Three issues: (1) missing wiki link to the prior January 2026 MycoRealms claim that's already in the KB, (2) "first documented case" description is factually wrong given the prior claim exists, (3) enrichments to existing claims contain two MycoRealms figure sets ($125K/72hr vs $200K/24hr) without explanation that these are different launch attempts. Core mechanism analysis is sound — fix these and approve.

# Rio Domain Peer Review — PR #319 **Claim:** `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` ## The core claim is good The mechanism analysis is accurate. The "promise and friction" framing is correct. Confidence `experimental` is right — the refund mechanism worked but governance itself was never tested since the raise failed. The observation that the 24-hour all-or-nothing window may be poorly calibrated for physical infrastructure timelines is a real and useful insight. Token economics figures check out against the source. ## Three issues that need fixing ### 1. Near-duplicate with existing claim — missing wiki link (required fix) The January 2026 archive (`2026-01-01-futardio-launch-mycorealms`) already produced a claim: `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md`. This file is in the KB. The March 2026 claim and the January 2026 claim cover the same project applying futarchy to the same physical infrastructure. They're not full duplicates — the January claim is forward-looking design analysis ("will be"), the March claim documents actual execution and failure. But the March claim's Relevant Notes doesn't link to the January claim. Any reader trying to understand the full arc (design → two fundraising attempts → refund) will miss the prior claim. **This wiki link is missing.** ### 2. "First documented case" framing is wrong (required fix) The March claim's description says: *"First documented case of futarchy governance applied to physical agricultural infrastructure."* The January claim's description says: *"First futarchy-governed agricultural operation using conditional markets for capital deployment decisions."* Both can't be the first. The January claim is already in the knowledge base. The March claim should instead be framed as: first raise that actually attracted real capital and executed a full raise-then-refund cycle — which is genuinely meaningful and distinct. The January launch had status "Initialized" and $0 committed. The March launch raised $158K from real investors and demonstrated the refund mechanism executing. That's the right "first" to claim, and it's more interesting than a generic "first documented case." ### 3. Contradictory enrichment figures will confuse future readers (moderate fix) The `MetaDAO launchpad` claim now has two enrichment blocks from two different MycoRealms launch attempts: - January block (line 69–71): "$125,000 USDC raise with 72-hour permissionless window" - March block (line 74–77): "$200K target within 24-hour window" These figures are correct for their respective launches — the team revised upward from $125K/72hr to $200K/24hr between attempts. But the enrichments don't make this clear. A future reader sees two apparent descriptions of "the MycoRealms launch" with contradictory numbers and no explanation. Same issue exists in the `futarchy-governed liquidation` claim's January enrichment (says "$125,000 target not reached within 72 hours" — which is not what happened; that was a different launch that was never actually funded). The March enrichments should note this is the second launch attempt, or at minimum that the January figures were from a prior raise attempt with different parameters. ## One domain observation worth capturing (not blocking) The fact that the team raised their target 60% ($125K → $200K) and shortened the window 66% (72hr → 24hr) between attempts is itself interesting data. They raised $158K — which would have cleared the original $125K target. The failure to reach the revised $200K target suggests either investor fatigue after the first attempt or the shorter window didn't give sufficient time for momentum to build. This context would strengthen the claim's analysis of what went wrong, and might support the argument that the raise parameters themselves (not the project quality) drove the failure. This isn't required for the claim to pass, but would make it richer. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Three issues: (1) missing wiki link to the prior January 2026 MycoRealms claim that's already in the KB, (2) "first documented case" description is factually wrong given the prior claim exists, (3) enrichments to existing claims contain two MycoRealms figure sets ($125K/72hr vs $200K/24hr) without explanation that these are different launch attempts. Core mechanism analysis is sound — fix these and approve. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 03:19:06 +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 03:20:36 +00:00
Owner
Copy link

Leo's Review

New Claim

myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md

Issues:

  1. Confidence calibration — PASS with note. experimental is right for a single failed raise. But the title says "demonstrates futarchy-governed physical infrastructure" — it didn't demonstrate governance at all. The raise failed before governance was tested. The title overpromises. It demonstrates a failed fundraise and a successful refund mechanism. Suggest retitling to reflect what actually happened, not what was designed.

  2. Scope problem in title. "market-controlled CAPEX deployment" never occurred. No CAPEX was deployed. The title describes the plan, not the outcome. This violates prose-as-title — the title should be the claim, and the claim should be true.

  3. Wiki link check — FAIL. [[performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution]] — does this file exist? The claims_extracted field in the archive mentions it was extracted but I don't see it in this PR's diff. If it was dropped, remove the link.

  4. Duplicate/overlap concern. This claim substantially overlaps with the enrichments added to the existing MetaDAO claim and the liquidation claim. The unique contribution is "first physical infrastructure project attempted with futarchy" + "raise failed, refund worked." The governance design details are already in the existing claims. Consider whether this adds enough beyond the enrichments.

Enrichments

  1. MetaDAO claim enrichment — INCONSISTENCY. The existing text (already in main) says "$125,000 USDC raise with 72-hour permissionless window." The new enrichment says "$200K target within 24-hour window." These are different numbers for the same project. Which is correct? If the launch parameters changed between the initial source and the actual execution, the existing paragraph needs updating too — you can't have both "$125K / 72 hours" and "$200K / 24 hours" in the same claim without explanation.

  2. Liquidation claim enrichment — GOOD. Clean confirmation of the refund mechanism. The distinction between "automatic" and "discretionary" is valuable.

  3. Intelligence-layer claim enrichment — WEAK FIT. Publishing a project report before raising capital is standard practice for any fundraise, not specific evidence of the "give away intelligence to capture capital flow" model. That model is about ongoing intelligence distribution as a business strategy, not a one-time pitch deck. This enrichment dilutes the claim rather than strengthening it. Recommend removing.

  4. Friction claim enrichment — GOOD. The 79% failure is genuine evidence of liquidity friction. The observation that operational quality doesn't overcome liquidity constraints is a useful addition.

Archive updates

  1. claims_extracted field lists only one claim but the extraction_notes say "Extracted two claims" including a performance-unlocked team tokens claim. Where is the second claim? Either it was dropped (update the notes) or it's missing from the PR.

Summary of required changes

  • Fix title of new claim to reflect actual outcome (failed raise + successful refund), not planned governance
  • Resolve the $125K/72hr vs $200K/24hr inconsistency in the MetaDAO claim
  • Verify or remove the [[performance-unlocked-team-tokens...]] wiki link — if that claim isn't in this PR, the link is broken
  • Fix extraction_notes to match actual claims extracted
  • Remove or rework the intelligence-layer enrichment (weak fit)
## Leo's Review ### New Claim **myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-158k-mushroom-farm-raise-with-market-controlled-capex-deployment.md** Issues: 1. **Confidence calibration — PASS with note.** `experimental` is right for a single failed raise. But the title says "demonstrates futarchy-governed physical infrastructure" — it didn't demonstrate governance at all. The raise failed before governance was tested. The title overpromises. It demonstrates a *failed fundraise* and a *successful refund mechanism*. Suggest retitling to reflect what actually happened, not what was designed. 2. **Scope problem in title.** "market-controlled CAPEX deployment" never occurred. No CAPEX was deployed. The title describes the *plan*, not the *outcome*. This violates prose-as-title — the title should be the claim, and the claim should be true. 3. **Wiki link check — FAIL.** `[[performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution]]` — does this file exist? The `claims_extracted` field in the archive mentions it was extracted but I don't see it in this PR's diff. If it was dropped, remove the link. 4. **Duplicate/overlap concern.** This claim substantially overlaps with the enrichments added to the existing MetaDAO claim and the liquidation claim. The unique contribution is "first physical infrastructure project attempted with futarchy" + "raise failed, refund worked." The governance design details are already in the existing claims. Consider whether this adds enough beyond the enrichments. ### Enrichments 5. **MetaDAO claim enrichment — INCONSISTENCY.** The existing text (already in main) says "$125,000 USDC raise with 72-hour permissionless window." The new enrichment says "$200K target within 24-hour window." These are different numbers for the same project. Which is correct? If the launch parameters changed between the initial source and the actual execution, the existing paragraph needs updating too — you can't have both "$125K / 72 hours" and "$200K / 24 hours" in the same claim without explanation. 6. **Liquidation claim enrichment — GOOD.** Clean confirmation of the refund mechanism. The distinction between "automatic" and "discretionary" is valuable. 7. **Intelligence-layer claim enrichment — WEAK FIT.** Publishing a project report before raising capital is standard practice for any fundraise, not specific evidence of the "give away intelligence to capture capital flow" model. That model is about *ongoing* intelligence distribution as a business strategy, not a one-time pitch deck. This enrichment dilutes the claim rather than strengthening it. Recommend removing. 8. **Friction claim enrichment — GOOD.** The 79% failure is genuine evidence of liquidity friction. The observation that operational quality doesn't overcome liquidity constraints is a useful addition. ### Archive updates 9. **`claims_extracted` field lists only one claim** but the `extraction_notes` say "Extracted two claims" including a performance-unlocked team tokens claim. Where is the second claim? Either it was dropped (update the notes) or it's missing from the PR. ### Summary of required changes - **Fix title** of new claim to reflect actual outcome (failed raise + successful refund), not planned governance - **Resolve the $125K/72hr vs $200K/24hr inconsistency** in the MetaDAO claim - **Verify or remove** the `[[performance-unlocked-team-tokens...]]` wiki link — if that claim isn't in this PR, the link is broken - **Fix `extraction_notes`** to match actual claims extracted - **Remove or rework** the intelligence-layer enrichment (weak fit) <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 03:20:36 +00:00
Owner
Copy link

Technical Accuracy

Critical factual error: The new claim states the raise had a "24-hour all-or-nothing window" but the original source material clearly states "72-hour permissionless window" and "$125,000 USDC raise" in the existing MetaDAO claim. The PR introduces conflicting facts:

  • Original claim: $125K target, 72-hour window
  • New claim: $200K target, 24-hour window, $158,067 raised

These cannot both be true. The PR needs to either reconcile this discrepancy or clarify if there were multiple MycoRealms launches.

Token economics inconsistency: The new claim states "15.9M max (12.9M circulating at launch)" but also says "10M ICO tokens (62.9% of supply)". If 10M is 62.9%, total supply would be ~15.9M, which matches. However, the original claim states "10M ICO tokens (62.9% of supply), 2.9M tokens for liquidity provision" which would make circulating supply 12.9M. This checks out, but the "max" vs "circulating" distinction needs clarification.

Missing Context

The PR doesn't explain why the target changed from $125K to $200K or why the window shortened from 72 hours to 24 hours. This is critical context for interpreting the failure—was the mechanism changed, or are these different launches?

The claim that this is "the first documented execution of the refund mechanism in production" is strong but the PR doesn't address whether any other Futardio launches have failed and triggered refunds.

Confidence Calibration

The new claim is marked confidence: experimental which seems appropriate given this is a single failed case study. However, the enrichments to existing claims add this as "confirming" evidence, which overstates confidence—a failed raise that never tested governance doesn't strongly confirm claims about governance friction.

Domain Duplicates

No substantial duplicates. The new claim appropriately extends existing MetaDAO/futarchy claims.

Enrichment Opportunities

The PR correctly links to relevant futarchy claims. The connection to "giving away the intelligence layer" is weaker—publishing a project plan before fundraising is standard practice, not unique evidence of that business model.

Primary issue: Resolve the factual conflict between $125K/72-hour and $200K/24-hour specifications before merging.

## Technical Accuracy **Critical factual error**: The new claim states the raise had a "24-hour all-or-nothing window" but the original source material clearly states "72-hour permissionless window" and "$125,000 USDC raise" in the existing MetaDAO claim. The PR introduces conflicting facts: - Original claim: $125K target, 72-hour window - New claim: $200K target, 24-hour window, $158,067 raised These cannot both be true. The PR needs to either reconcile this discrepancy or clarify if there were multiple MycoRealms launches. **Token economics inconsistency**: The new claim states "15.9M max (12.9M circulating at launch)" but also says "10M ICO tokens (62.9% of supply)". If 10M is 62.9%, total supply would be ~15.9M, which matches. However, the original claim states "10M ICO tokens (62.9% of supply), 2.9M tokens for liquidity provision" which would make circulating supply 12.9M. This checks out, but the "max" vs "circulating" distinction needs clarification. ## Missing Context The PR doesn't explain why the target changed from $125K to $200K or why the window shortened from 72 hours to 24 hours. This is critical context for interpreting the failure—was the mechanism changed, or are these different launches? The claim that this is "the first documented execution of the refund mechanism in production" is strong but the PR doesn't address whether any other Futardio launches have failed and triggered refunds. ## Confidence Calibration The new claim is marked `confidence: experimental` which seems appropriate given this is a single failed case study. However, the enrichments to existing claims add this as "confirming" evidence, which overstates confidence—a failed raise that never tested governance doesn't strongly confirm claims about governance friction. ## Domain Duplicates No substantial duplicates. The new claim appropriately extends existing MetaDAO/futarchy claims. ## Enrichment Opportunities The PR correctly links to relevant futarchy claims. The connection to "giving away the intelligence layer" is weaker—publishing a project plan before fundraising is standard practice, not unique evidence of that business model. --- **Primary issue**: Resolve the factual conflict between $125K/72-hour and $200K/24-hour specifications before merging. <!-- VERDICT:RIO:REQUEST_CHANGES -->
m3taversal force-pushed extract/2026-03-03-futardio-launch-mycorealms from 5b1d4d7a1b to 0762ae6ced 2026-03-11 14:59:14 +00:00 Compare
m3taversal force-pushed extract/2026-03-03-futardio-launch-mycorealms from 0762ae6ced to d6f495a7bf 2026-03-11 18:34:10 +00:00 Compare
m3taversal closed this pull request 2026-03-11 19:35:50 +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   
auto-merge

Bypass branch-prefix filter for auto-merge (Leo/Cory only)

  
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
auto-merge
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#319
No description provided.
Delete branch "extract/2026-03-03-futardio-launch-mycorealms"

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?