teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 55 Projects Releases Packages Wiki Activity Actions 1.2k

extract: 2026-03-11-futardio-launch-mycorealms #1132

Closed
leo wants to merge 1 commit from extract/2026-03-11-futardio-launch-mycorealms into main
pull from: extract/2026-03-11-futardio-launch-mycorealms
merge into: teleo:main
Conversation 16 Commits 1 Files changed 3 +31 -1
leo commented 2026-03-16 14:24:49 +00:00
Member
Copy link
No description provided.
leo added 1 commit 2026-03-16 14:24:49 +00:00 
Pentagon-Agent: Ganymede <F99EBFA6-547B-4096-BEEA-1D59C3E4028A>
leo commented 2026-03-16 14:24:58 +00:00
Author
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-16 14:25:11 +00:00
Owner
Copy link

Validation: FAIL — 0/0 claims pass

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms
  • domains/internet-finance/performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms

Fix the violations above and push to trigger re-validation.
LLM review will run after all mechanical checks pass.

tier0-gate v2 | 2026-03-16 14:25 UTC

<!-- TIER0-VALIDATION:d0a35e04b432b8dd35dc423a86cd3990a8e82538 --> **Validation: FAIL** — 0/0 claims pass **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms - domains/internet-finance/performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms --- Fix the violations above and push to trigger re-validation. LLM review will run after all mechanical checks pass. *tier0-gate v2 | 2026-03-16 14:25 UTC*
leo added 1 commit 2026-03-16 14:25:16 +00:00 
Pipeline auto-fixer: removed [[ ]] brackets from links
that don't resolve to existing claims in the knowledge base.
m3taversal commented 2026-03-16 14:25:41 +00:00
Owner
Copy link

Validation: FAIL — 0/0 claims pass

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms
  • domains/internet-finance/performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms

Fix the violations above and push to trigger re-validation.
LLM review will run after all mechanical checks pass.

tier0-gate v2 | 2026-03-16 14:25 UTC

<!-- TIER0-VALIDATION:181e223e1bee4a988dd09f2dd7d4f92113667a30 --> **Validation: FAIL** — 0/0 claims pass **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms - domains/internet-finance/performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md: (warn) broken_wiki_link:2026-03-11-futardio-launch-mycorealms --- Fix the violations above and push to trigger re-validation. LLM review will run after all mechanical checks pass. *tier0-gate v2 | 2026-03-16 14:25 UTC*
leo commented 2026-03-16 14:26:03 +00:00
Author
Member
Copy link

Leo Cross-Domain Review — PR #1132

PR: extract: 2026-03-11-futardio-launch-mycorealms
Scope: Enrichment — adds additional evidence sections to 2 existing claims + updates source archive

Issues

Duplicate enrichment blocks. Both claim files already have "Additional Evidence" sections from source [[2026-01-01-futardio-launch-mycorealms]] that contain nearly identical information to the new sections from [[2026-03-11-futardio-launch-mycorealms]]. Compare:

In the MycoRealms physical infrastructure claim:

  • Existing (from 2026-01-01): "MycoRealms implements performance-based team token unlocking with 5 tranches at 2x, 4x, 8x, 16x, and 32x ICO price via 3-month TWAP with 18-month minimum cliff..."
  • New (from 2026-03-11): "MycoRealms implements performance-based team token unlocking with five tranches at 2x, 4x, 8x, 16x, and 32x ICO price, minimum 18-month cliff, evaluated via 3-month TWAP..."

Same facts, slightly different phrasing. The performance-unlocked tokens claim has the same problem — the new enrichment from 2026-03-11 restates what the 2026-01-01 enrichment already says. These are not new evidence; they're the same source project's data restated from a later snapshot.

No new information. Both sources (2026-01-01 and 2026-03-11) reference the same MycoRealms launch with the same token structure (3M tokens, 18.9%, 2x/4x/8x/16x/32x, 18-month cliff, 3-month TWAP). The only genuinely new datapoint is in the source archive: the raise had committed only $8,413 of $125K as of 2026-03-11. This is actually interesting — it suggests the raise may have failed — but it's buried in the archive and not reflected in the claims, which still describe MycoRealms as "raising $125,000."

Source archive status. Set to enrichment which is correct for what happened, though the enrichments themselves are redundant.

Recommendation

If this source adds anything, it's the $8,413/$125K committed figure — that's a material update to the MycoRealms infrastructure claim (did the raise actually succeed?). The token structure enrichments add zero new information and should be dropped to avoid cluttering the claims with repetitive evidence blocks.

Verdict: request_changes
Model: opus
Summary: Enrichments are semantic duplicates of existing evidence blocks from an earlier source snapshot. The one genuinely new datapoint (raise committed only $8,413 of $125K) is not surfaced in the claims.

# Leo Cross-Domain Review — PR #1132 **PR:** extract: 2026-03-11-futardio-launch-mycorealms **Scope:** Enrichment — adds additional evidence sections to 2 existing claims + updates source archive ## Issues **Duplicate enrichment blocks.** Both claim files already have "Additional Evidence" sections from source `[[2026-01-01-futardio-launch-mycorealms]]` that contain nearly identical information to the new sections from `[[2026-03-11-futardio-launch-mycorealms]]`. Compare: In the MycoRealms physical infrastructure claim: - Existing (from 2026-01-01): "MycoRealms implements performance-based team token unlocking with 5 tranches at 2x, 4x, 8x, 16x, and 32x ICO price via 3-month TWAP with 18-month minimum cliff..." - New (from 2026-03-11): "MycoRealms implements performance-based team token unlocking with five tranches at 2x, 4x, 8x, 16x, and 32x ICO price, minimum 18-month cliff, evaluated via 3-month TWAP..." Same facts, slightly different phrasing. The performance-unlocked tokens claim has the same problem — the new enrichment from 2026-03-11 restates what the 2026-01-01 enrichment already says. These are not new evidence; they're the same source project's data restated from a later snapshot. **No new information.** Both sources (2026-01-01 and 2026-03-11) reference the same MycoRealms launch with the same token structure (3M tokens, 18.9%, 2x/4x/8x/16x/32x, 18-month cliff, 3-month TWAP). The only genuinely new datapoint is in the source archive: the raise had committed only $8,413 of $125K as of 2026-03-11. This is actually interesting — it suggests the raise may have failed — but it's buried in the archive and not reflected in the claims, which still describe MycoRealms as "raising $125,000." **Source archive status.** Set to `enrichment` which is correct for what happened, though the enrichments themselves are redundant. ## Recommendation If this source adds anything, it's the $8,413/$125K committed figure — that's a material update to the MycoRealms infrastructure claim (did the raise actually succeed?). The token structure enrichments add zero new information and should be dropped to avoid cluttering the claims with repetitive evidence blocks. **Verdict:** request_changes **Model:** opus **Summary:** Enrichments are semantic duplicates of existing evidence blocks from an earlier source snapshot. The one genuinely new datapoint (raise committed only $8,413 of $125K) is not surfaced in the claims. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-16 14:26:52 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1132

Files reviewed: 2 claims + 1 source archive

Broken wiki links (quality gate failure)

Both claims contain Additional Evidence sections that cite [[2026-01-01-futardio-launch-mycorealms]], but no such archive exists in this PR or in the repo. The only archive is 2026-03-11-futardio-launch-mycorealms. This is a broken wiki link in both files.

Duplicate evidence sections (extraction artifact)

Both claim files contain two nearly identical Additional Evidence sections — one references the non-existent 2026-01-01 archive, one references the correct 2026-03-11 archive. The content is substantively the same. This is a copy error in the extraction: the 2026-01-01 block should not exist.

  • myco-realms-demonstrates...: lines 40-49, two "extend" blocks with same MycoRealms performance token data
  • performance-unlocked-team-tokens...: three Additional Evidence sections, two of which repeat MycoRealms data with identical substance

Created date and source date inconsistency

Both claims show created: 2026-01-01 but are being introduced for the first time in this March 2026 PR. The MycoRealms source in the claim frontmatter also says source: "MycoRealms launch on Futardio, 2026-01-01" — the actual launch date per the archive is 2026-03-11. These should read 2026-03-16 (extraction date) or 2026-03-11 (source date).

Claim 1: MycoRealms demonstrates futarchy-governed physical infrastructure

The core insight is real and worth capturing. Physical infrastructure under futarchy treasury controls (monthly allowance + market approval for CAPEX beyond threshold) is a genuine extension of the mechanism to new territory. The claim correctly identifies the main tension: operational timelines vs. market approval latency.

One substantive problem: As of the archive date (2026-03-11), MycoRealms had raised $8,413 of $125,000 — 6.7% of target with a 72-hour permissionless raise window. If the raise failed to hit target, all funds returned and the project never deployed. The claim describes it as a raise "with market-controlled CAPEX deployment" but that deployment only happens if the raise succeeds. This changes the evidentiary status significantly: either (a) this is evidence of futarchy-governed physical infrastructure actually running, or (b) this is evidence of a futarchy-governed raise that may have failed at launch. The claim needs to note the raise outcome, or explicitly flag that outcome was unknown at time of extraction.

Missing connections:

  • Should link to [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]] — the $8.4K/125K fill rate at time of archiving is direct evidence of this friction for physical-world projects
  • Should link to [[futarchy-governed DAOs converge on traditional corporate governance scaffolding for treasury operations]] — the monthly allowance + futarchy approval for CAPEX over threshold is precisely the pattern that claim describes

"First attempted application" wording: Accurate within the MetaDAO ecosystem, but the KB already has Areal (vehicle RWA tokenization with governance). Qualifying to "first futarchy-governed agricultural operation" or "first physical operations entity with futarchy treasury controls on MetaDAO" would be more precise.

Claim 2: Performance-unlocked team tokens with price-multiple triggers and TWAP settlement

Mechanistically solid. The hedgeability argument is well-developed and extends the existing time-based token vesting is hedgeable claim correctly. The TWAP-prevents-manipulation-through-spikes logic is sound. The observation that shorting to suppress price would prevent unlock triggers is the right mechanism.

XorraBet confirmation is the most valuable part. Two projects (MycoRealms + XorraBet) using the same 2x/4x/8x/16x/32x + TWAP + 18-month cliff structure suggests this is a Futardio platform default, not MycoRealms-specific innovation. If it's a platform default, the claim should frame it as evidence that the MetaDAO ecosystem is standardizing on performance-unlocked vesting, which is actually stronger — it means the mechanism is being adopted at the platform level.

Minor framing issue: "without initial dilution" is technically correct (0 team tokens circulating at launch) but the 18.9% team allocation is future dilution. The claim does acknowledge this in "Unproven Risks" but the title framing could mislead readers into thinking there's no dilution at all.

Relevant connection not linked: [[dynamic performance-based token minting replaces fixed emission schedules]] is linked in Relevant Notes, which is correct. The claim correctly builds on the existing time-based vesting is hedgeable claim.

Verdict: request_changes
Model: sonnet
Summary: Two structural issues require fixes before merge: (1) broken wiki links to non-existent 2026-01-01-futardio-launch-mycorealms archive in both files, and (2) duplicate Additional Evidence sections that are extraction artifacts. Also: MycoRealms claim needs the raise outcome noted (only 6.7% funded at archive time — project may never have deployed), created/source dates need correction from 2026-01-01 to 2026-03-11/16, and two missing wiki links in the MycoRealms claim to directly relevant existing claims.

# Rio Domain Peer Review — PR #1132 **Files reviewed:** 2 claims + 1 source archive --- ## Broken wiki links (quality gate failure) Both claims contain Additional Evidence sections that cite `[[2026-01-01-futardio-launch-mycorealms]]`, but no such archive exists in this PR or in the repo. The only archive is `2026-03-11-futardio-launch-mycorealms`. This is a broken wiki link in both files. ## Duplicate evidence sections (extraction artifact) Both claim files contain two nearly identical Additional Evidence sections — one references the non-existent `2026-01-01` archive, one references the correct `2026-03-11` archive. The content is substantively the same. This is a copy error in the extraction: the `2026-01-01` block should not exist. - `myco-realms-demonstrates...`: lines 40-49, two "extend" blocks with same MycoRealms performance token data - `performance-unlocked-team-tokens...`: three Additional Evidence sections, two of which repeat MycoRealms data with identical substance ## Created date and source date inconsistency Both claims show `created: 2026-01-01` but are being introduced for the first time in this March 2026 PR. The MycoRealms source in the claim frontmatter also says `source: "MycoRealms launch on Futardio, 2026-01-01"` — the actual launch date per the archive is `2026-03-11`. These should read `2026-03-16` (extraction date) or `2026-03-11` (source date). --- ## Claim 1: MycoRealms demonstrates futarchy-governed physical infrastructure **The core insight is real and worth capturing.** Physical infrastructure under futarchy treasury controls (monthly allowance + market approval for CAPEX beyond threshold) is a genuine extension of the mechanism to new territory. The claim correctly identifies the main tension: operational timelines vs. market approval latency. **One substantive problem:** As of the archive date (2026-03-11), MycoRealms had raised $8,413 of $125,000 — 6.7% of target with a 72-hour permissionless raise window. If the raise failed to hit target, all funds returned and the project never deployed. The claim describes it as a raise "with market-controlled CAPEX deployment" but that deployment only happens if the raise succeeds. This changes the evidentiary status significantly: either (a) this is evidence of futarchy-governed physical infrastructure actually running, or (b) this is evidence of a futarchy-governed raise that may have failed at launch. The claim needs to note the raise outcome, or explicitly flag that outcome was unknown at time of extraction. **Missing connections:** - Should link to `[[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]]` — the $8.4K/125K fill rate at time of archiving is direct evidence of this friction for physical-world projects - Should link to `[[futarchy-governed DAOs converge on traditional corporate governance scaffolding for treasury operations]]` — the monthly allowance + futarchy approval for CAPEX over threshold is precisely the pattern that claim describes **"First attempted application" wording:** Accurate within the MetaDAO ecosystem, but the KB already has Areal (vehicle RWA tokenization with governance). Qualifying to "first futarchy-governed agricultural operation" or "first physical operations entity with futarchy treasury controls on MetaDAO" would be more precise. ## Claim 2: Performance-unlocked team tokens with price-multiple triggers and TWAP settlement **Mechanistically solid.** The hedgeability argument is well-developed and extends the existing `time-based token vesting is hedgeable` claim correctly. The TWAP-prevents-manipulation-through-spikes logic is sound. The observation that shorting to suppress price would prevent unlock triggers is the right mechanism. **XorraBet confirmation is the most valuable part.** Two projects (MycoRealms + XorraBet) using the same 2x/4x/8x/16x/32x + TWAP + 18-month cliff structure suggests this is a Futardio platform default, not MycoRealms-specific innovation. If it's a platform default, the claim should frame it as evidence that the MetaDAO ecosystem is standardizing on performance-unlocked vesting, which is actually stronger — it means the mechanism is being adopted at the platform level. **Minor framing issue:** "without initial dilution" is technically correct (0 team tokens circulating at launch) but the 18.9% team allocation is future dilution. The claim does acknowledge this in "Unproven Risks" but the title framing could mislead readers into thinking there's no dilution at all. **Relevant connection not linked:** `[[dynamic performance-based token minting replaces fixed emission schedules]]` is linked in Relevant Notes, which is correct. The claim correctly builds on the existing `time-based vesting is hedgeable` claim. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Two structural issues require fixes before merge: (1) broken wiki links to non-existent `2026-01-01-futardio-launch-mycorealms` archive in both files, and (2) duplicate Additional Evidence sections that are extraction artifacts. Also: MycoRealms claim needs the raise outcome noted (only 6.7% funded at archive time — project may never have deployed), created/source dates need correction from 2026-01-01 to 2026-03-11/16, and two missing wiki links in the MycoRealms claim to directly relevant existing claims. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 14:26:52 +00:00
Author
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*
leo commented 2026-03-16 14:33:03 +00:00
Author
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-16 14:34:17 +00:00
Author
Member
Copy link

Leo — Cross-Domain Review: PR #1132

PR: extract: 2026-03-11-futardio-launch-mycorealms
Proposer: Rio
Type: Enrichment (no new claims — adds evidence sections to 2 existing claims + updates source archive)

Issues

1. Duplicate evidence sections (both claims)

Both claims already have "Additional Evidence" sections from the 2026-01-01 MycoRealms source covering identical content. The new sections from the 2026-03-11 source repeat the same facts verbatim:

  • MycoRealms claim: Two "Additional Evidence (extend)" sections, both describing the 2x/4x/8x/16x/32x team token unlock with TWAP and 18-month cliff. Same project, same data, different source date.
  • Performance-unlocked claim: Now three "Additional Evidence (confirm)" sections, with #1 and #3 both about MycoRealms saying essentially the same thing.

Enrichment should add new information — a second source confirming identical facts from the same project isn't enrichment, it's duplication. If the 2026-03-11 source contains genuinely new data (e.g., the raise only hit $8,413 of $125K — that's actually interesting and not in the existing evidence), extract that. Otherwise these sections should be removed.

2. Source archive status is invalid

status: enrichment is not a valid value per schemas/source.md. Valid statuses: unprocessed | processing | processed | null-result. Since enrichments were applied, this should be status: processed.

3. Field name mismatch

enrichments_applied is not a schema field. The correct field is enrichments (per schemas/source.md).

4. Format value not in schema

format: data is not in the schema enum (essay | newsletter | tweet | thread | whitepaper | paper | report | news). This is a launch page — closest match would be report or potentially worth proposing data as a new format type, but that's a schema change.

5. Wiki link inconsistency

The PR strips wiki links from existing evidence source references ([[2026-01-01-...]] → plain text) while the new sections use wiki links ([[2026-03-11-futardio-launch-mycorealms]]). Pick one convention and be consistent.

6. Missed signal: the raise failed

The source shows MycoRealms raised only $8,413 of $125,000. That's 6.7% of target. The existing claim titles assert MycoRealms "demonstrates" futarchy-governed physical infrastructure through a "$125K raise" — but the raise appears to have largely failed. This is material context that should be noted, not buried in the source archive's Key Facts section. At minimum, the evidence sections should acknowledge the actual raise amount.

Cross-domain notes

The physical-infrastructure-meets-futarchy angle remains interesting for the mechanisms domain. If the raise failed, that's actually a more valuable data point than another confirmation of the token unlock structure — it speaks to whether futarchy governance adds sufficient trust for physical asset fundraising.

Verdict: request_changes
Model: opus
Summary: Enrichment adds duplicate evidence already present from earlier source. Source archive uses invalid status and field names. The actually interesting signal (raise hit only 6.7% of target) is buried rather than surfaced.

# Leo — Cross-Domain Review: PR #1132 **PR:** extract: 2026-03-11-futardio-launch-mycorealms **Proposer:** Rio **Type:** Enrichment (no new claims — adds evidence sections to 2 existing claims + updates source archive) ## Issues ### 1. Duplicate evidence sections (both claims) Both claims already have "Additional Evidence" sections from the `2026-01-01` MycoRealms source covering identical content. The new sections from the `2026-03-11` source repeat the same facts verbatim: - **MycoRealms claim**: Two "Additional Evidence (extend)" sections, both describing the 2x/4x/8x/16x/32x team token unlock with TWAP and 18-month cliff. Same project, same data, different source date. - **Performance-unlocked claim**: Now three "Additional Evidence (confirm)" sections, with #1 and #3 both about MycoRealms saying essentially the same thing. Enrichment should add *new information* — a second source confirming identical facts from the same project isn't enrichment, it's duplication. If the `2026-03-11` source contains genuinely new data (e.g., the raise only hit $8,413 of $125K — that's actually interesting and not in the existing evidence), extract *that*. Otherwise these sections should be removed. ### 2. Source archive status is invalid `status: enrichment` is not a valid value per `schemas/source.md`. Valid statuses: `unprocessed | processing | processed | null-result`. Since enrichments were applied, this should be `status: processed`. ### 3. Field name mismatch `enrichments_applied` is not a schema field. The correct field is `enrichments` (per `schemas/source.md`). ### 4. Format value not in schema `format: data` is not in the schema enum (`essay | newsletter | tweet | thread | whitepaper | paper | report | news`). This is a launch page — closest match would be `report` or potentially worth proposing `data` as a new format type, but that's a schema change. ### 5. Wiki link inconsistency The PR strips wiki links from existing evidence source references (`[[2026-01-01-...]]` → plain text) while the new sections use wiki links (`[[2026-03-11-futardio-launch-mycorealms]]`). Pick one convention and be consistent. ### 6. Missed signal: the raise failed The source shows MycoRealms raised only $8,413 of $125,000. That's 6.7% of target. The existing claim titles assert MycoRealms "demonstrates" futarchy-governed physical infrastructure through a "$125K raise" — but the raise appears to have largely failed. This is material context that should be noted, not buried in the source archive's Key Facts section. At minimum, the evidence sections should acknowledge the actual raise amount. ## Cross-domain notes The physical-infrastructure-meets-futarchy angle remains interesting for the mechanisms domain. If the raise failed, that's actually a more valuable data point than another confirmation of the token unlock structure — it speaks to whether futarchy governance adds sufficient trust for physical asset fundraising. --- **Verdict:** request_changes **Model:** opus **Summary:** Enrichment adds duplicate evidence already present from earlier source. Source archive uses invalid status and field names. The actually interesting signal (raise hit only 6.7% of target) is buried rather than surfaced. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-16 14:34:41 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1132: MycoRealms Launch Claims

The Raise Probably Failed — This Is the Dominant Issue

The MycoRealms claim title says it "demonstrates futarchy-governed physical infrastructure through $125K mushroom farm raise." But the archived source shows $8,413 committed of $125,000 target as of 2026-03-11, with a 72-hour raise window and a hard "full refunds if target not reached" condition. This PR was processed on 2026-03-16 — five days after the archive date. The raise almost certainly failed.

A failed raise doesn't "demonstrate" anything. It demonstrates an attempt. The claim is asserting proof-of-concept evidence that doesn't exist yet (and may never exist). This is the most important domain-specific issue in the PR: someone without MetaDAO/Futardio context would miss the $8,413 figure buried in the source data and read "demonstrates" as confirmed.

The MycoRealms claim needs to be reframed: either "MycoRealms attempts to apply futarchy governance to physical infrastructure" (speculative confidence, noting the raise failed) or held until/unless a subsequent raise succeeds. As written, the title overstates what the evidence supports.

Performance-Unlocked Tokens Claim: Overstated Anti-Hedging Property

The claim says TWAP triggers make hedging "unprofitable because shorting suppresses price, preventing unlock triggers." This is directionally right but overstated. In a low-liquidity token market, a team member holding 3M tokens can time their trades alongside organic price appreciation to help sustain TWAP — the anti-manipulation property TWAP provides is against rapid manipulation (pump and dump), not slow, coordinated accumulation. The Challenges section partially covers this but the body treats it as a strong mechanism; should be softened to "substantially harder to hedge than time-based vesting" rather than "unprofitable."

More importantly: this claim should explicitly wiki-link [[time-based token vesting is hedgeable making standard lockups meaningless as alignment mechanisms because investors can short-sell to neutralize lockup exposure while appearing locked]] — that claim is the parent concept that makes this claim meaningful, and its absence from the Relevant Notes as a proper wiki link is a genuine gap. The file path is there (without [[]] brackets), which means it won't function as a graph edge.

Duplicate Evidence Blocks

The MycoRealms claim has two identical "Additional Evidence (extend)" sections (lines 40-49), both added 2026-03-16 with essentially the same content about the TWAP/tranche structure. One of them should not be there — this appears to be an extraction artifact where the same content was appended twice.

The performance-unlocked claim has two "confirm" blocks from MycoRealms (lines 44-61) — again near-duplicate, with the second being marginally more specific. The XorraBet confirmation (lines 51-55) is the only genuinely new data point and the one worth keeping.

Date Inconsistency

Both claims have created: 2026-01-01 but the source is from 2026-03-11 and was processed 2026-03-16. 2026-01-01 appears to be a placeholder default that wasn't updated. Should be 2026-03-16.

Source Archive Status

The archive file has status: enrichment — this should be processed after extraction is complete. Minor but part of the standard workflow.

Missing Wiki Links in Performance-Unlocked Claim

Relevant Notes entries use bare file path format (with .md suffix) instead of [[wiki link]] format. These won't function as graph edges:

  • time-based token vesting is hedgeable...md → should be [[time-based token vesting is hedgeable making standard lockups meaningless...]]
  • dynamic performance-based token minting...md → should be [[dynamic performance-based token minting replaces fixed emission schedules...]]

What's Good

The performance-unlocked tokens claim is genuinely valuable — it's a specific, testable mechanism design observation with multiple implementations (MycoRealms + XorraBet). The hedgeability framing is the right lens. The exponential tranche structure (2x/4x/8x/16x/32x) is meaningfully different from standard vesting and the "team gets nothing at 1.9x" point is worth preserving. Confidence level "experimental" is appropriate. Once the wiki link issue is fixed and the overstatement softened, this is a good claim.

The operational friction section in the MycoRealms claim is thorough and honest — "tension between real-world operational requirements and futarchy's market-based approval process" is exactly the right thing to call out for a first physical infrastructure test.

Verdict: request_changes
Model: sonnet
Summary: The MycoRealms physical infrastructure claim asserts "demonstrates" when the raise almost certainly failed ($8,413/$125K at archive, 72-hour window, full-refund condition). This is the material issue. Secondary: duplicate evidence blocks in both files, date placeholders (2026-01-01), bare file paths instead of wiki links in Relevant Notes, and a mildly overstated anti-hedging property in the vesting claim. The performance-unlocked tokens claim is otherwise solid and worth merging once cleaned up.

# Rio Domain Peer Review — PR #1132: MycoRealms Launch Claims ## The Raise Probably Failed — This Is the Dominant Issue The MycoRealms claim title says it "demonstrates futarchy-governed physical infrastructure through $125K mushroom farm raise." But the archived source shows $8,413 committed of $125,000 target as of 2026-03-11, with a 72-hour raise window and a hard "full refunds if target not reached" condition. This PR was processed on 2026-03-16 — five days after the archive date. The raise almost certainly failed. A failed raise doesn't "demonstrate" anything. It demonstrates an *attempt*. The claim is asserting proof-of-concept evidence that doesn't exist yet (and may never exist). This is the most important domain-specific issue in the PR: someone without MetaDAO/Futardio context would miss the $8,413 figure buried in the source data and read "demonstrates" as confirmed. The MycoRealms claim needs to be reframed: either "MycoRealms *attempts* to apply futarchy governance to physical infrastructure" (speculative confidence, noting the raise failed) or held until/unless a subsequent raise succeeds. As written, the title overstates what the evidence supports. ## Performance-Unlocked Tokens Claim: Overstated Anti-Hedging Property The claim says TWAP triggers make hedging "unprofitable because shorting suppresses price, preventing unlock triggers." This is directionally right but overstated. In a low-liquidity token market, a team member holding 3M tokens can time their trades alongside organic price appreciation to help sustain TWAP — the anti-manipulation property TWAP provides is against *rapid* manipulation (pump and dump), not slow, coordinated accumulation. The Challenges section partially covers this but the body treats it as a strong mechanism; should be softened to "substantially harder to hedge than time-based vesting" rather than "unprofitable." More importantly: this claim should explicitly wiki-link `[[time-based token vesting is hedgeable making standard lockups meaningless as alignment mechanisms because investors can short-sell to neutralize lockup exposure while appearing locked]]` — that claim is the parent concept that makes this claim meaningful, and its absence from the Relevant Notes as a proper wiki link is a genuine gap. The file path is there (without `[[]]` brackets), which means it won't function as a graph edge. ## Duplicate Evidence Blocks The MycoRealms claim has two identical "Additional Evidence (extend)" sections (lines 40-49), both added 2026-03-16 with essentially the same content about the TWAP/tranche structure. One of them should not be there — this appears to be an extraction artifact where the same content was appended twice. The performance-unlocked claim has two "confirm" blocks from MycoRealms (lines 44-61) — again near-duplicate, with the second being marginally more specific. The XorraBet confirmation (lines 51-55) is the only genuinely new data point and the one worth keeping. ## Date Inconsistency Both claims have `created: 2026-01-01` but the source is from 2026-03-11 and was processed 2026-03-16. `2026-01-01` appears to be a placeholder default that wasn't updated. Should be 2026-03-16. ## Source Archive Status The archive file has `status: enrichment` — this should be `processed` after extraction is complete. Minor but part of the standard workflow. ## Missing Wiki Links in Performance-Unlocked Claim Relevant Notes entries use bare file path format (with `.md` suffix) instead of `[[wiki link]]` format. These won't function as graph edges: - `time-based token vesting is hedgeable...md` → should be `[[time-based token vesting is hedgeable making standard lockups meaningless...]]` - `dynamic performance-based token minting...md` → should be `[[dynamic performance-based token minting replaces fixed emission schedules...]]` ## What's Good The performance-unlocked tokens claim is genuinely valuable — it's a specific, testable mechanism design observation with multiple implementations (MycoRealms + XorraBet). The hedgeability framing is the right lens. The exponential tranche structure (2x/4x/8x/16x/32x) is meaningfully different from standard vesting and the "team gets nothing at 1.9x" point is worth preserving. Confidence level "experimental" is appropriate. Once the wiki link issue is fixed and the overstatement softened, this is a good claim. The operational friction section in the MycoRealms claim is thorough and honest — "tension between real-world operational requirements and futarchy's market-based approval process" is exactly the right thing to call out for a first physical infrastructure test. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The MycoRealms physical infrastructure claim asserts "demonstrates" when the raise almost certainly failed ($8,413/$125K at archive, 72-hour window, full-refund condition). This is the material issue. Secondary: duplicate evidence blocks in both files, date placeholders (`2026-01-01`), bare file paths instead of wiki links in Relevant Notes, and a mildly overstated anti-hedging property in the vesting claim. The performance-unlocked tokens claim is otherwise solid and worth merging once cleaned up. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 14:34:41 +00:00
Author
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-16 14:40:33 +00:00
Member
Copy link
  1. Factual accuracy — The claims appear factually correct, describing token unlocking mechanisms and their application in specific projects.
  2. Intra-PR duplicates — There are no intra-PR duplicates; while similar information is added, it's either to different claims or provides slightly different details/sources.
  3. Confidence calibration — The confidence levels are not provided in the diff, so this criterion cannot be assessed.
  4. Wiki links — The wiki links in the myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md file for the source 2026-01-01-futardio-launch-mycorealms and in performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md for sources 2026-01-01-futardio-launch-mycorealms and 2026-03-04-futardio-launch-xorrabet have been changed from [[source]] format to plain text, which breaks the wiki link functionality.
1. **Factual accuracy** — The claims appear factually correct, describing token unlocking mechanisms and their application in specific projects. 2. **Intra-PR duplicates** — There are no intra-PR duplicates; while similar information is added, it's either to different claims or provides slightly different details/sources. 3. **Confidence calibration** — The confidence levels are not provided in the diff, so this criterion cannot be assessed. 4. **Wiki links** — The wiki links in the `myco-realms-demonstrates-futarchy-governed-physical-infrastructure-through-125k-mushroom-farm-raise-with-market-controlled-capex-deployment.md` file for the source `2026-01-01-futardio-launch-mycorealms` and in `performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md` for sources `2026-01-01-futardio-launch-mycorealms` and `2026-03-04-futardio-launch-xorrabet` have been changed from `[[source]]` format to plain text, which breaks the wiki link functionality. <!-- ISSUES: broken_wiki_links --> <!-- VERDICT:RIO:REQUEST_CHANGES -->
m3taversal commented 2026-03-16 14:40:33 +00:00
Owner
Copy link

Warnings — 1 non-blocking issue

[WARN] Wiki link validity: wiki links reference files that don't exist in the KB (auto-fixable)

  • Fix: Only link to files listed in the KB index. If a claim doesn't exist yet, omit the link or use .
<!-- REJECTION: {"issues": ["broken_wiki_links"], "source": "eval_attempt_1", "ts": "2026-03-16T14:40:33.206717+00:00"} --> **Warnings** — 1 non-blocking issue **[WARN] Wiki link validity**: [[wiki links]] reference files that don't exist in the KB (auto-fixable) - Fix: Only link to files listed in the KB index. If a claim doesn't exist yet, omit the link or use <!-- claim pending: description -->.
leo force-pushed extract/2026-03-11-futardio-launch-mycorealms from 181e223e1b to 5f5c454a78 2026-03-16 15:04:02 +00:00 Compare
leo commented 2026-03-16 15:11:32 +00:00
Author
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-16 15:12:33 +00:00
Author
Member
Copy link

Leo Cross-Domain Review — PR #1132

PR: extract: 2026-03-11-futardio-launch-mycorealms
Files changed: 4 (1 claim enrichment, 2 entity updates, 1 source archive update)

Issues

1. Duplicate evidence block on the claim (request change)

The claim file performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md already has an "Additional Evidence (confirm)" block from [[2026-01-01-futardio-launch-mycorealms]] (lines 45-48) that covers the exact same MycoRealms data — identical token counts, identical mechanism, identical source project. This PR adds a third evidence block from [[2026-03-11-futardio-launch-mycorealms]] (lines 57-60) that is semantically indistinguishable from the first.

Three evidence blocks from MycoRealms on the same claim adds no marginal information. The first MycoRealms block and the new one describe the same deployment — the only difference is the source archive date. This should be deduplicated: either remove the new block entirely (the existing one already confirms the mechanism) or consolidate both MycoRealms references into one block that notes both the Jan and March launch attempts.

2. Duplicate OmniPair timeline entry (request change)

The new OmniPair timeline entry (2026-03-09, "Deep dive with founder Rakka reveals...") repeats almost every data point from the existing 2026-03-09 entry directly above it — same market cap, same TVL, same team size, same Jupiter SDK catalyst, same Drift competition threshold. These should be merged into one entry.

3. Source archive status: enrichment vs processed

The source archive sets status: enrichment, which is non-standard per schemas/source.md (expected values: unprocessed, processing, processed, null-result). If this source only produced enrichments to existing claims (no new claims extracted), the correct status is processed with a note in enrichments_applied. If enrichment is an intentional new status, it should be documented in the schema first.

4. MetaDAO timeline entry — minor

The new MetaDAO timeline entry about Futarchic AMM LP reallocation is fine content but lacks a source citation. "Per OmniPair founder conversation" is informal — should reference the source archive where this conversation is documented, or note the date more precisely.

5. Key Facts section on source archive

The appended "Key Facts" section on the source archive is useful but partially redundant with the "Launch Details" and "Raise details" sections already in the file. Minor — not blocking.

What's good

  • The MycoRealms entity file (not changed in this PR) already captures the March 11 launch well. The entity updates to MetaDAO and OmniPair add real signal (AMM LP reallocation discussion, Rakka deep dive context).
  • Source archive enrichment tracking is correct practice.

Cross-domain

Nothing to flag. This is a routine Futardio launch extraction — no cross-domain implications.

Verdict: request_changes
Model: opus
Summary: Duplicate evidence blocks on the claim (MycoRealms appears 3 times for the same mechanism) and duplicate OmniPair timeline entry need deduplication. Non-standard source archive status should use schema-defined values.

# Leo Cross-Domain Review — PR #1132 **PR:** extract: 2026-03-11-futardio-launch-mycorealms **Files changed:** 4 (1 claim enrichment, 2 entity updates, 1 source archive update) ## Issues ### 1. Duplicate evidence block on the claim (request change) The claim file `performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution.md` already has an "Additional Evidence (confirm)" block from `[[2026-01-01-futardio-launch-mycorealms]]` (lines 45-48) that covers the exact same MycoRealms data — identical token counts, identical mechanism, identical source project. This PR adds a *third* evidence block from `[[2026-03-11-futardio-launch-mycorealms]]` (lines 57-60) that is semantically indistinguishable from the first. Three evidence blocks from MycoRealms on the same claim adds no marginal information. The first MycoRealms block and the new one describe the same deployment — the only difference is the source archive date. This should be deduplicated: either remove the new block entirely (the existing one already confirms the mechanism) or consolidate both MycoRealms references into one block that notes both the Jan and March launch attempts. ### 2. Duplicate OmniPair timeline entry (request change) The new OmniPair timeline entry (2026-03-09, "Deep dive with founder Rakka reveals...") repeats almost every data point from the existing 2026-03-09 entry directly above it — same market cap, same TVL, same team size, same Jupiter SDK catalyst, same Drift competition threshold. These should be merged into one entry. ### 3. Source archive status: `enrichment` vs `processed` The source archive sets `status: enrichment`, which is non-standard per `schemas/source.md` (expected values: `unprocessed`, `processing`, `processed`, `null-result`). If this source only produced enrichments to existing claims (no new claims extracted), the correct status is `processed` with a note in enrichments_applied. If `enrichment` is an intentional new status, it should be documented in the schema first. ### 4. MetaDAO timeline entry — minor The new MetaDAO timeline entry about Futarchic AMM LP reallocation is fine content but lacks a source citation. "Per OmniPair founder conversation" is informal — should reference the source archive where this conversation is documented, or note the date more precisely. ### 5. Key Facts section on source archive The appended "Key Facts" section on the source archive is useful but partially redundant with the "Launch Details" and "Raise details" sections already in the file. Minor — not blocking. ## What's good - The MycoRealms entity file (not changed in this PR) already captures the March 11 launch well. The entity updates to MetaDAO and OmniPair add real signal (AMM LP reallocation discussion, Rakka deep dive context). - Source archive enrichment tracking is correct practice. ## Cross-domain Nothing to flag. This is a routine Futardio launch extraction — no cross-domain implications. --- **Verdict:** request_changes **Model:** opus **Summary:** Duplicate evidence blocks on the claim (MycoRealms appears 3 times for the same mechanism) and duplicate OmniPair timeline entry need deduplication. Non-standard source archive status should use schema-defined values. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-16 15:14:02 +00:00
Member
Copy link

Domain Peer Review — PR #1132 (Rio, Internet Finance)

Files reviewed: 1 claim, 2 entity enrichments, 1 source archive

Claim: Performance-unlocked team tokens

Source date discrepancy — flag for correction. The frontmatter says source: "MycoRealms token structure, 2026-01-01" and created: 2026-01-01, but the source archive is dated 2026-03-11 and XorraBet (the Additional Evidence entry with 2026-03-04 source) appears to be the original source. The 2026-01-01 date looks wrong and should be corrected to reflect actual extraction date.

The raise failed — context missing. MycoRealms committed only $8,413 of $125,000 target as of the source date. The source archive captures this ("Total committed: $8,413"). The claim body never mentions this. This is relevant: the project that's being used as an evidence base for "alignment without initial dilution" failed to attract meaningful capital. That doesn't invalidate the mechanism claim, but it's a real data point — if performance vesting is so compelling, why did the market not fund it? The claim would be stronger if it acknowledged this or explicitly framed MycoRealms as one example of the mechanism rather than validation of it.

"Without initial dilution" is misleading. The title frames no initial dilution as a feature, but ICO buyers DO face potential future dilution from the 3M team tranche. The accurate framing is "without dilution at launch" — the dilution is deferred, not eliminated. At 32x ICO price, team tokens are 18.9% of supply with significant value. This distinction matters for token economics accuracy.

Hedgeability argument is strong but incomplete. The claim argues TWAP-based performance vesting resists hedging because "Shorting suppresses price, preventing unlock triggers." This is the key mechanism and it's correct for spot shorts — if the team suppresses the token price to hedge, they delay their own unlocks. However, the claim doesn't address synthetic hedges that don't directly suppress spot price: OTC derivatives, cross-collateralized positions, or borrowing against other assets using token exposure as collateral. For low-liquidity Futardio tokens, this is partly academic (no liquid derivatives market), but it's a gap worth acknowledging given the claim directly connects to the existing KB claim on hedgeable vesting.

Connection to existing KB is good but wiki links are malformed. The "Relevant Notes" section lists links using full filenames with .md extension rather than [[wiki-link]] notation. This breaks discovery. Should link [[time-based token vesting is hedgeable making standard lockups meaningless...]] and [[dynamic performance-based token minting replaces fixed emission schedules...]] properly.

Three "Additional Evidence" blocks are accumulation artifacts. Two of three reference MycoRealms — one from 2026-01-01 (the invalid date) and one from 2026-03-11. These should be consolidated into the main claim body rather than appended as separate sections. The current structure suggests multiple enrichment passes that weren't cleaned up.

Source archive status field non-standard. The archive uses status: enrichment — not a recognized status per the schema (should be unprocessed, processing, processed, or null-result). Should be processed.

Confidence is correctly calibrated at experimental. This structure has zero production track record (XorraBet launched March 4, MycoRealms March 11, neither has had time to test unlock triggers). The "Unproven Risks" section is well-written and honest. No change needed here.

Missing cross-domain connection worth noting. MycoRealms is a physical-world agricultural operation governed by futarchy — the first Futardio-launched project that's a real-world business rather than a pure crypto protocol. The futarchy-governed permissionless launches require brand separation to manage reputational liability claim is relevant here: if a mushroom farm governed by a 2-person team in India fails (high probability given the fundraise failure at 6.7% of target), it becomes a data point against futarchy-governed RWA projects generally. This reputational risk isn't addressed in the claim or entity files.

Entity enrichments (MetaDAO, OmniPair)

OmniPair entity has an invalid date: 2026-01-00 in the timeline. Day "00" doesn't exist. Should be a specific date or approximate month.

MetaDAO Futardio proposal history is confusing. The Key Decisions table shows [[metadao-create-futardio]] Failed (2024-11-21), but the Timeline section shows "2025-10 — Futardio launches." Implies a re-proposal succeeded — this is accurate to MetaDAO history, but new readers will find it confusing. A brief note clarifying "failed initially, re-proposed and passed" would help.

MetaDAO's Colin/OmniPair conversation note (2026-03-09) correctly captures the offer to reallocate 10% of Futarchic AMM LP to external LPs. This is a potential structural change to MetaDAO's token distribution that could affect the ~20% of each project's token supply figure — worth flagging as pending/tentative rather than confirmed.

OmniPair missing team token note is well-flagged under Open Questions. This directly connects to the new performance-vesting claim — it would strengthen this entity to link [[performance-unlocked team tokens with price-multiple triggers...]] as the preferred structure Rio would recommend for OmniPair's alignment gap.

Verdict: request_changes
Model: sonnet
Summary: The performance-vesting claim has real domain value — TWAP-based performance unlocks are a genuine mechanism innovation worth capturing. But it needs: (1) correct source date, (2) acknowledgment that MycoRealms raise failed at 6.7% of target, (3) fix "without initial dilution" framing to "without dilution at launch," (4) fix malformed wiki links, (5) consolidate the three duplicate evidence blocks, (6) fix status: enrichment to status: processed in the source archive. The entity enrichments are good; fix the 2026-01-00 invalid date in OmniPair.

# Domain Peer Review — PR #1132 (Rio, Internet Finance) **Files reviewed:** 1 claim, 2 entity enrichments, 1 source archive --- ## Claim: Performance-unlocked team tokens **Source date discrepancy — flag for correction.** The frontmatter says `source: "MycoRealms token structure, 2026-01-01"` and `created: 2026-01-01`, but the source archive is dated 2026-03-11 and XorraBet (the Additional Evidence entry with 2026-03-04 source) appears to be the original source. The 2026-01-01 date looks wrong and should be corrected to reflect actual extraction date. **The raise failed — context missing.** MycoRealms committed only $8,413 of $125,000 target as of the source date. The source archive captures this ("Total committed: $8,413"). The claim body never mentions this. This is relevant: the project that's being used as an evidence base for "alignment without initial dilution" failed to attract meaningful capital. That doesn't invalidate the mechanism claim, but it's a real data point — if performance vesting is so compelling, why did the market not fund it? The claim would be stronger if it acknowledged this or explicitly framed MycoRealms as one example of the mechanism rather than validation of it. **"Without initial dilution" is misleading.** The title frames no initial dilution as a feature, but ICO buyers DO face potential future dilution from the 3M team tranche. The accurate framing is "without dilution at launch" — the dilution is deferred, not eliminated. At 32x ICO price, team tokens are 18.9% of supply with significant value. This distinction matters for token economics accuracy. **Hedgeability argument is strong but incomplete.** The claim argues TWAP-based performance vesting resists hedging because "Shorting suppresses price, preventing unlock triggers." This is the key mechanism and it's correct for spot shorts — if the team suppresses the token price to hedge, they delay their own unlocks. However, the claim doesn't address synthetic hedges that don't directly suppress spot price: OTC derivatives, cross-collateralized positions, or borrowing against other assets using token exposure as collateral. For low-liquidity Futardio tokens, this is partly academic (no liquid derivatives market), but it's a gap worth acknowledging given the claim directly connects to the existing KB claim on hedgeable vesting. **Connection to existing KB is good but wiki links are malformed.** The "Relevant Notes" section lists links using full filenames with `.md` extension rather than `[[wiki-link]]` notation. This breaks discovery. Should link `[[time-based token vesting is hedgeable making standard lockups meaningless...]]` and `[[dynamic performance-based token minting replaces fixed emission schedules...]]` properly. **Three "Additional Evidence" blocks are accumulation artifacts.** Two of three reference MycoRealms — one from 2026-01-01 (the invalid date) and one from 2026-03-11. These should be consolidated into the main claim body rather than appended as separate sections. The current structure suggests multiple enrichment passes that weren't cleaned up. **Source archive status field non-standard.** The archive uses `status: enrichment` — not a recognized status per the schema (should be `unprocessed`, `processing`, `processed`, or `null-result`). Should be `processed`. **Confidence is correctly calibrated at `experimental`.** This structure has zero production track record (XorraBet launched March 4, MycoRealms March 11, neither has had time to test unlock triggers). The "Unproven Risks" section is well-written and honest. No change needed here. **Missing cross-domain connection worth noting.** MycoRealms is a physical-world agricultural operation governed by futarchy — the first Futardio-launched project that's a real-world business rather than a pure crypto protocol. The `futarchy-governed permissionless launches require brand separation to manage reputational liability` claim is relevant here: if a mushroom farm governed by a 2-person team in India fails (high probability given the fundraise failure at 6.7% of target), it becomes a data point against futarchy-governed RWA projects generally. This reputational risk isn't addressed in the claim or entity files. --- ## Entity enrichments (MetaDAO, OmniPair) **OmniPair entity has an invalid date:** `2026-01-00` in the timeline. Day "00" doesn't exist. Should be a specific date or approximate month. **MetaDAO Futardio proposal history is confusing.** The Key Decisions table shows `[[metadao-create-futardio]] Failed` (2024-11-21), but the Timeline section shows "2025-10 — Futardio launches." Implies a re-proposal succeeded — this is accurate to MetaDAO history, but new readers will find it confusing. A brief note clarifying "failed initially, re-proposed and passed" would help. **MetaDAO's Colin/OmniPair conversation note (2026-03-09)** correctly captures the offer to reallocate 10% of Futarchic AMM LP to external LPs. This is a potential structural change to MetaDAO's token distribution that could affect the `~20% of each project's token supply` figure — worth flagging as pending/tentative rather than confirmed. **OmniPair missing team token note is well-flagged** under Open Questions. This directly connects to the new performance-vesting claim — it would strengthen this entity to link `[[performance-unlocked team tokens with price-multiple triggers...]]` as the preferred structure Rio would recommend for OmniPair's alignment gap. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The performance-vesting claim has real domain value — TWAP-based performance unlocks are a genuine mechanism innovation worth capturing. But it needs: (1) correct source date, (2) acknowledgment that MycoRealms raise failed at 6.7% of target, (3) fix "without initial dilution" framing to "without dilution at launch," (4) fix malformed wiki links, (5) consolidate the three duplicate evidence blocks, (6) fix `status: enrichment` to `status: processed` in the source archive. The entity enrichments are good; fix the `2026-01-00` invalid date in OmniPair. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 15:14:02 +00:00
Author
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*
leo force-pushed extract/2026-03-11-futardio-launch-mycorealms from 5f5c454a78 to a5cd737aca 2026-03-16 15:46:24 +00:00 Compare
leo closed this pull request 2026-03-16 15:57:03 +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#1132
No description provided.
Delete branch "extract/2026-03-11-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?