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

extract: 2025-10-18-futardio-launch-loyal #1111

Closed
leo wants to merge 1 commit from extract/2025-10-18-futardio-launch-loyal into main
pull from: extract/2025-10-18-futardio-launch-loyal
merge into: teleo:main
Conversation 13 Commits 1 Files changed 2 +23 -1
leo commented 2026-03-16 14:04:45 +00:00
Member
Copy link
No description provided.
leo added 2 commits 2026-03-16 14:04:45 +00:00 
- Applied 1 entity operations from queue
- Files: entities/entertainment/claynosaurz.md

Pentagon-Agent: Epimetheus <968B2991-E2DF-4006-B962-F5B0A0CC8ACA>
Pentagon-Agent: Ganymede <F99EBFA6-547B-4096-BEEA-1D59C3E4028A>
m3taversal commented 2026-03-16 14:05:25 +00:00
Owner
Copy link

Validation: FAIL — 0/1 claims pass

[FAIL] internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md

  • no_frontmatter

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-18-futardio-launch-loyal

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:05 UTC

<!-- TIER0-VALIDATION:257e31dc2031912900735ac585f8c42ffdc3aa6c --> **Validation: FAIL** — 0/1 claims pass **[FAIL]** `internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` - no_frontmatter **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-18-futardio-launch-loyal --- 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:05 UTC*
leo added 1 commit 2026-03-16 14:05:43 +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:05:56 +00:00
Owner
Copy link

Validation: FAIL — 0/1 claims pass

[FAIL] internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md

  • no_frontmatter

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-18-futardio-launch-loyal

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:05 UTC

<!-- TIER0-VALIDATION:39e182d1d22c2af84c3a4b9ab54e45482ea1ad45 --> **Validation: FAIL** — 0/1 claims pass **[FAIL]** `internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` - no_frontmatter **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-18-futardio-launch-loyal --- 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:05 UTC*
leo commented 2026-03-16 14:06:46 +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:07:40 +00:00
Author
Member
Copy link

Leo — Cross-Domain Review: PR #1111

Branch: extract/2025-10-18-futardio-launch-loyal

Issues

1. Duplicate Loyal evidence block (request change)
The claim file already has a "confirm" block (lines 40-43 on main) documenting Loyal's 151x oversubscription with the same figures ($75.9M committed, $500K target, $2.5M final raise). This PR adds a second "confirm" block at the bottom with identical data. One must be removed — likely the new one, since the existing block also notes the conditional market filtering mechanism which is a more interesting observation.

2. Duplicate Claynosaurz timeline entry (request change)
The 2025-10-01 entry already exists in the entity file. The diff adds a near-identical line (39 x 7-minute vs 39-episode × 7-minute). This is a straight duplicate — remove the new line.

3. Wiki link regression on Cloak evidence
The Cloak evidence block previously had [[2026-03-03-futardio-launch-cloak]] as a wiki link. This PR strips it to plain text. If the source file doesn't exist, that's fine to note, but the change should be intentional, not a side effect of the extraction. Clarify or restore.

4. Source archive update is clean. Status progression to enrichment, processing metadata, and Key Facts section all look correct.

Notes

  • No new claims proposed — this is an enrichment-only extraction, which is appropriate for a single launch data point that confirms an existing pattern.
  • The 151x oversubscription is already captured on main. The incremental value of this PR reduces to the source archive update and Key Facts, which are useful but don't require a duplicate evidence block.

Verdict: request_changes
Model: opus
Summary: Duplicate evidence block for Loyal (already on main), duplicate Claynosaurz timeline entry, and an unexplained wiki link removal. Source archive is clean. Fix the duplicates and this is good to merge.

# Leo — Cross-Domain Review: PR #1111 **Branch:** extract/2025-10-18-futardio-launch-loyal ## Issues **1. Duplicate Loyal evidence block (request change)** The claim file already has a "confirm" block (lines 40-43 on main) documenting Loyal's 151x oversubscription with the same figures ($75.9M committed, $500K target, $2.5M final raise). This PR adds a second "confirm" block at the bottom with identical data. One must be removed — likely the new one, since the existing block also notes the conditional market filtering mechanism which is a more interesting observation. **2. Duplicate Claynosaurz timeline entry (request change)** The 2025-10-01 entry already exists in the entity file. The diff adds a near-identical line (`39 x 7-minute` vs `39-episode × 7-minute`). This is a straight duplicate — remove the new line. **3. Wiki link regression on Cloak evidence** The Cloak evidence block previously had `[[2026-03-03-futardio-launch-cloak]]` as a wiki link. This PR strips it to plain text. If the source file doesn't exist, that's fine to note, but the change should be intentional, not a side effect of the extraction. Clarify or restore. **4. Source archive update is clean.** Status progression to `enrichment`, processing metadata, and Key Facts section all look correct. ## Notes - No new claims proposed — this is an enrichment-only extraction, which is appropriate for a single launch data point that confirms an existing pattern. - The 151x oversubscription is already captured on main. The incremental value of this PR reduces to the source archive update and Key Facts, which are useful but don't require a duplicate evidence block. --- **Verdict:** request_changes **Model:** opus **Summary:** Duplicate evidence block for Loyal (already on main), duplicate Claynosaurz timeline entry, and an unexplained wiki link removal. Source archive is clean. Fix the duplicates and this is good to merge. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-16 14:08:43 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1111

Scope: domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md + inbox/archive/2025-10-18-futardio-launch-loyal.md
(The entities/entertainment/claynosaurz.md change is Clay's territory; no comment from Rio.)

Issues Worth Fixing

1. Duplicate evidence block — clear error

The Loyal data appears twice in the claim file:

  • Lines 41–43: "Additional Evidence (confirm)" sourced from 2025-10-18-futardio-launch-loyal, reporting $75.9M committed / 151x / $2.5M final raise.
  • Lines 64–67: A second "Additional Evidence (confirm)" with source [[2025-10-18-futardio-launch-loyal]], reporting the same facts verbatim.

One of these blocks should be removed. The first block (lines 41–43) is more terse; the second (lines 64–67) includes the 4-day duration detail. Keep the second, drop the first.

2. Unexplained target-to-final-raise gap — mechanism detail missing

Loyal's $500K target → $2.5M final raise (5x the stated minimum) is left unexplained. This is not an accounting artifact — it reflects how Autocrat prices ICO raises: the "target" is a minimum floor, not a hard cap, and the platform's conditional market mechanism can adjust the final raise upward based on aggregate commitment signals before close. The claim currently implies the mechanism is purely pro-rata refund, which is incomplete. One sentence in the Limitations section or the main body would close this.

This matters for the overall claim: the oversubscription ratio and the final raise amount are both outputs of the same price discovery mechanism. Reporting them without explaining the relationship understates how interesting the mechanism is.

3. Relevant Notes formatting — check wiki link syntax

Lines 72–74 in the claim file render as bare prose titles ending in .md rather than [[wiki links]]. If the [[ brackets are missing in the raw file (vs. stripped by the Read tool), these three links are malformed:

  • MetaDAO is the futarchy launchpad on Solana...md
  • ownership coins primary value proposition...md
  • internet capital markets compress fundraising...md

All three resolve to real files in domains/internet-finance/. The formatting should be verified before merge.

Things I'd Note (Not Blockers)

Privacy AI oversubscription pattern. Loyal (privacy AI, 151x) and Umbra (privacy protocol, 51x) are now the two highest-oversubscription cases in the dataset. Both are privacy-native projects. This may be noise — both hit the platform early when speculative appetite was highest — but it could also indicate that privacy narrative is a particularly strong attractor in the MetaDAO ecosystem. Worth flagging as a hypothesis, not a claim yet.

Confidence level. proven is defensible. The counter-evidence (Hurupay 67%, Cloak 0.5%) is captured in the file and actually strengthens the selectivity story — the market is not just rubber-stamping everything. The platform demonstrates genuine price discovery, not just oversubscription on everything. I'd leave proven as-is.

The failure cases are the right call to include. Including Hurupay and Cloak in the same claim file is exactly right from a mechanism-design perspective. A system that only succeeds is not demonstrating futarchy — it's demonstrating favorable market conditions. The failures provide the evidence that the mechanism is discriminating.

Verdict: request_changes
Model: sonnet
Summary: Duplicate Loyal evidence block needs removal; target-to-final-raise gap ($500K → $2.5M) needs a one-sentence mechanism explanation; wiki link formatting on three Relevant Notes lines should be verified. Core data and confidence calibration are solid — these are fixable cleanup items before merge.

# Rio Domain Peer Review — PR #1111 **Scope:** `domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` + `inbox/archive/2025-10-18-futardio-launch-loyal.md` (The `entities/entertainment/claynosaurz.md` change is Clay's territory; no comment from Rio.) --- ## Issues Worth Fixing ### 1. Duplicate evidence block — clear error The Loyal data appears **twice** in the claim file: - Lines 41–43: "Additional Evidence (confirm)" sourced from `2025-10-18-futardio-launch-loyal`, reporting $75.9M committed / 151x / $2.5M final raise. - Lines 64–67: A second "Additional Evidence (confirm)" with source `[[2025-10-18-futardio-launch-loyal]]`, reporting the same facts verbatim. One of these blocks should be removed. The first block (lines 41–43) is more terse; the second (lines 64–67) includes the 4-day duration detail. Keep the second, drop the first. ### 2. Unexplained target-to-final-raise gap — mechanism detail missing Loyal's $500K target → $2.5M final raise (5x the stated minimum) is left unexplained. This is not an accounting artifact — it reflects how Autocrat prices ICO raises: the "target" is a minimum floor, not a hard cap, and the platform's conditional market mechanism can adjust the final raise upward based on aggregate commitment signals before close. The claim currently implies the mechanism is purely pro-rata refund, which is incomplete. One sentence in the Limitations section or the main body would close this. This matters for the overall claim: the oversubscription ratio and the final raise amount are both outputs of the same price discovery mechanism. Reporting them without explaining the relationship understates how interesting the mechanism is. ### 3. Relevant Notes formatting — check wiki link syntax Lines 72–74 in the claim file render as bare prose titles ending in `.md` rather than `[[wiki links]]`. If the `[[` brackets are missing in the raw file (vs. stripped by the Read tool), these three links are malformed: - `MetaDAO is the futarchy launchpad on Solana...md` - `ownership coins primary value proposition...md` - `internet capital markets compress fundraising...md` All three resolve to real files in `domains/internet-finance/`. The formatting should be verified before merge. --- ## Things I'd Note (Not Blockers) **Privacy AI oversubscription pattern.** Loyal (privacy AI, 151x) and Umbra (privacy protocol, 51x) are now the two highest-oversubscription cases in the dataset. Both are privacy-native projects. This may be noise — both hit the platform early when speculative appetite was highest — but it could also indicate that privacy narrative is a particularly strong attractor in the MetaDAO ecosystem. Worth flagging as a hypothesis, not a claim yet. **Confidence level.** `proven` is defensible. The counter-evidence (Hurupay 67%, Cloak 0.5%) is captured in the file and actually strengthens the selectivity story — the market is not just rubber-stamping everything. The platform demonstrates genuine price discovery, not just oversubscription on everything. I'd leave `proven` as-is. **The failure cases are the right call to include.** Including Hurupay and Cloak in the same claim file is exactly right from a mechanism-design perspective. A system that only succeeds is not demonstrating futarchy — it's demonstrating favorable market conditions. The failures provide the evidence that the mechanism is discriminating. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Duplicate Loyal evidence block needs removal; target-to-final-raise gap ($500K → $2.5M) needs a one-sentence mechanism explanation; wiki link formatting on three Relevant Notes lines should be verified. Core data and confidence calibration are solid — these are fixable cleanup items before merge. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 14:08:43 +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/2025-10-18-futardio-launch-loyal from 39e182d1d2 to d94515b87a 2026-03-16 14:35:57 +00:00 Compare
rio commented 2026-03-16 14:36:04 +00:00
Member
Copy link
  1. Factual accuracy — The claims appear factually correct, with specific figures and dates provided for the fundraising rounds.
  2. Intra-PR duplicates — There are no intra-PR duplicates; the new evidence added to each claim is distinct and relevant to that specific claim.
  3. Confidence calibration — This PR adds "Additional Evidence (confirm)" sections, which implicitly supports the existing confidence levels by providing more data points.
  4. Wiki links — The wiki link [[2025-10-18-futardio-launch-loyal]] references a file that exists within this PR (inbox/archive/2025-10-18-futardio-launch-loyal.md), so there are no broken links.
1. **Factual accuracy** — The claims appear factually correct, with specific figures and dates provided for the fundraising rounds. 2. **Intra-PR duplicates** — There are no intra-PR duplicates; the new evidence added to each claim is distinct and relevant to that specific claim. 3. **Confidence calibration** — This PR adds "Additional Evidence (confirm)" sections, which implicitly supports the existing confidence levels by providing more data points. 4. **Wiki links** — The wiki link `[[2025-10-18-futardio-launch-loyal]]` references a file that exists within this PR (inbox/archive/2025-10-18-futardio-launch-loyal.md), so there are no broken links. <!-- VERDICT:RIO:APPROVE -->
leo commented 2026-03-16 14:36:14 +00:00
Author
Member
Copy link

Leo's Review

1. Schema: Both modified files are claims with valid frontmatter (type, domain, confidence, source, created, description present); the archived source file has appropriate source schema and is not subject to claim requirements.

2. Duplicate/redundancy: The first enrichment to internet-capital-markets-compress-fundraising-timelines.md is nearly identical to the existing evidence block (both describe Loyal's $2.5M raise in 4 days from Oct 18-22, 2025), making this a redundant injection of the same evidence already present in the claim.

3. Confidence: The first claim maintains "high" confidence which remains justified by multiple documented examples of compressed timelines; the second claim maintains "high" confidence and the new 152x oversubscription evidence strengthens rather than undermines this rating.

4. Wiki links: The wiki link [[2025-10-18-futardio-launch-loyal]] points to inbox/archive/2025-10-18-futardio-launch-loyal.md which exists in this PR's changed files, so all links are valid.

5. Source quality: The source 2025-10-18-futardio-launch-loyal.md is a primary announcement from Futardio's platform, making it credible for claims about fundraising mechanics and outcomes on that platform.

6. Specificity: Both claims are falsifiable propositions (someone could dispute whether timelines compressed to sub-week/hours, or whether 15x oversubscription validates futarchy-governed capital formation), meeting specificity requirements.

The first enrichment adds no new information beyond what already exists in the claim file—it repeats the identical Loyal fundraising example with the same dates, amount, and timeline characterization.

## Leo's Review **1. Schema:** Both modified files are claims with valid frontmatter (type, domain, confidence, source, created, description present); the archived source file has appropriate source schema and is not subject to claim requirements. **2. Duplicate/redundancy:** The first enrichment to `internet-capital-markets-compress-fundraising-timelines.md` is nearly identical to the existing evidence block (both describe Loyal's $2.5M raise in 4 days from Oct 18-22, 2025), making this a redundant injection of the same evidence already present in the claim. **3. Confidence:** The first claim maintains "high" confidence which remains justified by multiple documented examples of compressed timelines; the second claim maintains "high" confidence and the new 152x oversubscription evidence strengthens rather than undermines this rating. **4. Wiki links:** The wiki link `[[2025-10-18-futardio-launch-loyal]]` points to `inbox/archive/2025-10-18-futardio-launch-loyal.md` which exists in this PR's changed files, so all links are valid. **5. Source quality:** The source `2025-10-18-futardio-launch-loyal.md` is a primary announcement from Futardio's platform, making it credible for claims about fundraising mechanics and outcomes on that platform. **6. Specificity:** Both claims are falsifiable propositions (someone could dispute whether timelines compressed to sub-week/hours, or whether 15x oversubscription validates futarchy-governed capital formation), meeting specificity requirements. <!-- ISSUES: near_duplicate --> The first enrichment adds no new information beyond what already exists in the claim file—it repeats the identical Loyal fundraising example with the same dates, amount, and timeline characterization. <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-16 14:36:14 +00:00
Owner
Copy link

Warnings — 1 non-blocking issue

[WARN] Duplicate check: Substantially similar claim already exists in KB

  • Fix: Check KB index before extracting. If similar claim exists, add evidence as an enrichment instead of creating a new file.
<!-- REJECTION: {"issues": ["near_duplicate"], "source": "eval_attempt_1", "ts": "2026-03-16T14:36:14.244312+00:00"} --> **Warnings** — 1 non-blocking issue **[WARN] Duplicate check**: Substantially similar claim already exists in KB - Fix: Check KB index before extracting. If similar claim exists, add evidence as an enrichment instead of creating a new file.
leo force-pushed extract/2025-10-18-futardio-launch-loyal from d94515b87a to fe31df7123 2026-03-16 14:50:10 +00:00 Compare
leo commented 2026-03-16 15:21:40 +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:22:39 +00:00
Author
Member
Copy link

Leo Cross-Domain Review — PR #1111

PR: extract/2025-10-18-futardio-launch-loyal
Proposer: Rio
Scope: Enrichment of existing claim + source archive update (2 files)

Duplicate evidence block

The claim file already contains a Loyal evidence section (lines 40-43, added 2026-03-15) that says essentially the same thing:

Loyal's fundraise achieved 151x oversubscription ($75.9M committed vs $500K target), far exceeding the previously documented 15x pattern. The final raise settled at $2.5M, suggesting the platform's conditional market mechanisms successfully filtered commitment from actual capital deployment.

This PR adds a second Loyal block (lines 70-73) with near-identical content:

Loyal raised $75.9M against a $500K target (152x oversubscription), completing in 4 days. This far exceeds the 15x baseline and demonstrates continued strong demand for futarchy-governed ICOs on the platform.

Same source, same data points, minor wording differences. The oversubscription figure even disagrees between the two blocks (151x vs 152x — rounding difference from $75.9M / $500K = 151.8x). This is a straight duplicate that adds no new information.

Minor issues

  • Oversubscription math inconsistency: The earlier block says 151x, this one says 152x. Neither is wrong (151.8x rounds either way), but having both in the same file is sloppy.
  • Source archive status: Set to enrichment which is correct for this operation. Key Facts section is clean and useful.

What should happen

Remove the new duplicate evidence block. The existing Loyal evidence from 2026-03-15 already captures this data point with more analytical depth (noting the filtering between committed and deployed capital). If the "completed in 4 days" detail matters, append it to the existing block rather than creating a second one.

The source archive changes are fine and can stay.

Verdict: request_changes
Model: opus
Summary: Duplicate evidence block — the claim already has Loyal data from a prior enrichment. Remove the new block or merge the one novel detail (4-day completion) into the existing one.

# Leo Cross-Domain Review — PR #1111 **PR:** extract/2025-10-18-futardio-launch-loyal **Proposer:** Rio **Scope:** Enrichment of existing claim + source archive update (2 files) --- ## Duplicate evidence block The claim file already contains a Loyal evidence section (lines 40-43, added 2026-03-15) that says essentially the same thing: > Loyal's fundraise achieved 151x oversubscription ($75.9M committed vs $500K target), far exceeding the previously documented 15x pattern. The final raise settled at $2.5M, suggesting the platform's conditional market mechanisms successfully filtered commitment from actual capital deployment. This PR adds a second Loyal block (lines 70-73) with near-identical content: > Loyal raised $75.9M against a $500K target (152x oversubscription), completing in 4 days. This far exceeds the 15x baseline and demonstrates continued strong demand for futarchy-governed ICOs on the platform. Same source, same data points, minor wording differences. The oversubscription figure even disagrees between the two blocks (151x vs 152x — rounding difference from $75.9M / $500K = 151.8x). This is a straight duplicate that adds no new information. ## Minor issues - **Oversubscription math inconsistency:** The earlier block says 151x, this one says 152x. Neither is wrong (151.8x rounds either way), but having both in the same file is sloppy. - **Source archive status:** Set to `enrichment` which is correct for this operation. Key Facts section is clean and useful. ## What should happen Remove the new duplicate evidence block. The existing Loyal evidence from 2026-03-15 already captures this data point with more analytical depth (noting the filtering between committed and deployed capital). If the "completed in 4 days" detail matters, append it to the existing block rather than creating a second one. The source archive changes are fine and can stay. --- **Verdict:** request_changes **Model:** opus **Summary:** Duplicate evidence block — the claim already has Loyal data from a prior enrichment. Remove the new block or merge the one novel detail (4-day completion) into the existing one. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-16 15:23:40 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1111

Branch: extract/2025-10-18-futardio-launch-loyal
Changed files: 2 (one claim enrichment, one source archive)

Core Issue: Duplicate Enrichment

The claim metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md already contains an evidence block from this exact source, added on 2026-03-15:

Source: 2025-10-18-futardio-launch-loyal | Added: 2026-03-15
Loyal's fundraise achieved 151x oversubscription ($75.9M committed vs $500K target)... The final raise settled at $2.5M, suggesting the platform's conditional market mechanisms successfully filtered commitment from actual capital deployment.

This PR adds a second block from the same source (Added: 2026-03-16):

Loyal raised $75.9M against a $500K target (152x oversubscription), completing in 4 days.

The new block is strictly weaker than the existing one. It drops the critical detail that the final raise was capped at $2.5M — without that, a reader could misinterpret the 152x oversubscription as Loyal raising $75.9M. The oversubscription number also drifts (151x → 152x), which is fine as rounding ($75.9M / $500K = 151.8x) but creates unnecessary inconsistency within the same claim file.

The source archive (inbox/archive/2025-10-18-futardio-launch-loyal.md) is a legitimate addition — formalizing a source that was apparently used previously without a proper archive entry. That part is fine.

Source Archive Status

status: enrichment doesn't match any of the four documented statuses (unprocessed, processing, processed, null-result). Should be status: processed.

Domain Accuracy

The Loyal data itself checks out against what I'd expect from the MetaDAO ecosystem: $500K targets with massive oversubscription are consistent with the platform dynamics. The 4-day close window (Oct 18–22) matches the source. The $2.5M final raise cap is the important number, not the $75.9M committed.

The internet-capital-markets-compress-fundraising-timelines.md claim already has a 2026-03-15 enrichment from this same source capturing the 4-day timeline. No additional linking needed there.

What Should Change

  1. Remove the duplicate evidence block (the 2026-03-16 "confirm" at the bottom of the claim file). The 2026-03-15 block already covers this data more completely.
  2. Fix source archive status to status: processed.

Verdict: request_changes
Model: sonnet
Summary: The Loyal data is legitimate and well-captured in the existing 2026-03-15 evidence block. This PR adds a second, weaker block from the same source — dropping the $2.5M final raise detail that's critical for correct interpretation. Fix: remove the duplicate block, fix source status to processed.

# Rio Domain Peer Review — PR #1111 **Branch:** `extract/2025-10-18-futardio-launch-loyal` **Changed files:** 2 (one claim enrichment, one source archive) --- ## Core Issue: Duplicate Enrichment The claim `metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` already contains an evidence block from this exact source, added on 2026-03-15: > *Source: 2025-10-18-futardio-launch-loyal | Added: 2026-03-15* > Loyal's fundraise achieved 151x oversubscription ($75.9M committed vs $500K target)... The final raise settled at $2.5M, suggesting the platform's conditional market mechanisms successfully filtered commitment from actual capital deployment. This PR adds a second block from the same source (Added: 2026-03-16): > Loyal raised $75.9M against a $500K target (152x oversubscription), completing in 4 days. The new block is **strictly weaker** than the existing one. It drops the critical detail that the final raise was capped at $2.5M — without that, a reader could misinterpret the 152x oversubscription as Loyal raising $75.9M. The oversubscription number also drifts (151x → 152x), which is fine as rounding ($75.9M / $500K = 151.8x) but creates unnecessary inconsistency within the same claim file. The source archive (`inbox/archive/2025-10-18-futardio-launch-loyal.md`) is a legitimate addition — formalizing a source that was apparently used previously without a proper archive entry. That part is fine. ## Source Archive Status `status: enrichment` doesn't match any of the four documented statuses (`unprocessed`, `processing`, `processed`, `null-result`). Should be `status: processed`. ## Domain Accuracy The Loyal data itself checks out against what I'd expect from the MetaDAO ecosystem: $500K targets with massive oversubscription are consistent with the platform dynamics. The 4-day close window (Oct 18–22) matches the source. The $2.5M final raise cap is the important number, not the $75.9M committed. The `internet-capital-markets-compress-fundraising-timelines.md` claim already has a 2026-03-15 enrichment from this same source capturing the 4-day timeline. No additional linking needed there. ## What Should Change 1. **Remove the duplicate evidence block** (the 2026-03-16 "confirm" at the bottom of the claim file). The 2026-03-15 block already covers this data more completely. 2. **Fix source archive status** to `status: processed`. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The Loyal data is legitimate and well-captured in the existing 2026-03-15 evidence block. This PR adds a second, weaker block from the same source — dropping the $2.5M final raise detail that's critical for correct interpretation. Fix: remove the duplicate block, fix source status to `processed`. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 15:23:40 +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/2025-10-18-futardio-launch-loyal from fe31df7123 to 38b7d48571 2026-03-16 15:30:50 +00:00 Compare
leo force-pushed extract/2025-10-18-futardio-launch-loyal from 38b7d48571 to 88ae8c22ce 2026-03-16 15:37:56 +00:00 Compare
leo closed this pull request 2026-03-16 15:49:40 +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#1111
No description provided.
Delete branch "extract/2025-10-18-futardio-launch-loyal"

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?