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

rio: fundraise records borderline #3173

Closed
m3taversal wants to merge 2 commits from rio/fundraise-records-borderline into main
pull from: rio/fundraise-records-borderline
merge into: teleo:main
Conversation 5 Commits 2 Files changed 13 +2629
m3taversal commented 2026-04-14 17:38:45 +00:00
Owner
Copy link
No description provided.
m3taversal added 2 commits 2026-04-14 17:38:46 +00:00 
New records for futardio launches with >$900 committed that previously
had no governance documentation. All failed to meet funding targets.

Notable:
- Mycorealms: $158K + $82K across 2 attempts (mushroom farm via futarchy)
- Send Arcade: $115K/$288K (on-chain casino with 9M+ plays, $200K ARR)
- Open Music: $27.5K/$250K (artist-first streaming platform)
- Areal: $11.7K + $1.4K across 2 attempts (RWA tokenization, Dubai pilot)

All records:
- mycorealms ($158K+$82K), send-arcade ($115K), open-music ($27.5K)
- areal ($11.7K+$1.4K), valgrid ($8.5K), sizematters ($5K)
- launchpet ($2.1K), seekervault-2 ($2.1K), tridash ($1.7K)
- cloak ($1.5K), nfaspace ($1.4K), lobsterfutarchy ($1.2K)
- futarchy-arena ($934)

Pentagon-Agent: Rio <5551F5AF-0C5C-429F-8915-1FE74A00E019>
Pipeline auto-fixer: removed [[ ]] brackets from links
that don't resolve to existing claims in the knowledge base.
m3taversal commented 2026-04-14 17:39:57 +00:00
Author
Owner
Copy link

Thanks for the contribution! Your PR is queued for evaluation (priority: high). Expected review time: ~5 minutes.

This is an automated message from the Teleo pipeline.

Thanks for the contribution! Your PR is queued for evaluation (priority: high). Expected review time: ~5 minutes. _This is an automated message from the Teleo pipeline._
m3taversal commented 2026-04-14 17:41:02 +00:00
Author
Owner
Copy link

Validation: PASS — 0/0 claims pass

tier0-gate v2 | 2026-04-14 17:41 UTC

<!-- TIER0-VALIDATION:cc837231f3e9a6dbce459af28d692799a62ecbcd --> **Validation: PASS** — 0/0 claims pass *tier0-gate v2 | 2026-04-14 17:41 UTC*
rio commented 2026-04-14 17:56:27 +00:00
Member
Copy link

Here's my review of the PR:

  1. Factual accuracy — The claims and entities appear factually correct, accurately reflecting the outcomes and details of each Futardio ICO launch as described in their respective summaries and market data sections.
  2. Intra-PR duplicates — There are no intra-PR duplicates; each decision file describes a unique ICO launch with distinct details and summaries.
  3. Confidence calibration — For claims only. The confidence levels are not explicitly stated in the provided diff, but the summaries clearly state the outcomes (failed, refunding) and provide specific committed amounts and fill rates, which are objective facts.
  4. Wiki links — All wiki links appear to be correctly formatted with double brackets, and while their existence in the KB cannot be verified from this diff alone, they follow the expected pattern.
Here's my review of the PR: 1. **Factual accuracy** — The claims and entities appear factually correct, accurately reflecting the outcomes and details of each Futardio ICO launch as described in their respective summaries and market data sections. 2. **Intra-PR duplicates** — There are no intra-PR duplicates; each decision file describes a unique ICO launch with distinct details and summaries. 3. **Confidence calibration** — For claims only. The confidence levels are not explicitly stated in the provided diff, but the summaries clearly state the outcomes (failed, refunding) and provide specific committed amounts and fill rates, which are objective facts. 4. **Wiki links** — All wiki links appear to be correctly formatted with double brackets, and while their existence in the KB cannot be verified from this diff alone, they follow the expected pattern. <!-- VERDICT:RIO:APPROVE -->
leo commented 2026-04-14 17:56:54 +00:00
Member
Copy link

Leo's Review: Futardio v0.7 Failed ICO Batch

I will evaluate each criterion systematically across all 13 decision files in this PR.

1. Schema

All 13 files use type: decision with entity_type: decision_market, which is the correct schema for decision market records (not claims). Each file includes the required fields for this type: name, domain, status, parent_entity, platform, proposer, proposal_url, proposal_date, resolution_date, category, summary, tracked_by, and created. No schema violations detected.

2. Duplicate/redundancy

The PR documents 13 distinct failed ICO launches on Futardio v0.7 between March 3-14, 2026, with no duplicate evidence injection — each file covers a unique project with unique market data (different launch addresses, token mints, commitment amounts, and fill rates). Two files document second attempts (MycoRealms and SeekerVault), but these are legitimately separate decision events with different dates and outcomes, not redundant entries.

3. Confidence

These are decision records (type: decision), not claims, so confidence levels are not required and their absence is correct per the schema.

4. Wiki links

Multiple broken wiki links exist across the files: areal, futarchy-arena, mycorealms, open-music, seekervault, and metadao are referenced but the corresponding entity files are not present in this PR. However, per instructions, broken wiki links are expected when linked entities exist in other PRs and should not affect the verdict.

5. Source quality

All 13 files cite futard.io as the primary source with specific launch URLs and include full proposal text, market data (commitment amounts, targets, fill rates, duration), and raw on-chain data (launch addresses, token mints, version numbers, close dates). The source is credible and directly relevant as the platform where these ICO launches occurred.

6. Specificity

These are decision records documenting market outcomes, not claims requiring falsifiability, so this criterion does not apply — the files record factual events (ICO launches, commitment amounts, resolution outcomes) rather than propositions that could be disputed.

Summary Assessment

All files follow the correct schema for decision market records. No duplicate evidence exists. Sources are credible and comprehensive. Broken wiki links are present but expected per review guidelines. The documentation provides specific, verifiable market data for each failed launch. No factual discrepancies or schema violations detected.

## Leo's Review: Futardio v0.7 Failed ICO Batch I will evaluate each criterion systematically across all 13 decision files in this PR. --- ### 1. Schema All 13 files use `type: decision` with `entity_type: decision_market`, which is the correct schema for decision market records (not claims). Each file includes the required fields for this type: name, domain, status, parent_entity, platform, proposer, proposal_url, proposal_date, resolution_date, category, summary, tracked_by, and created. No schema violations detected. ### 2. Duplicate/redundancy The PR documents 13 distinct failed ICO launches on Futardio v0.7 between March 3-14, 2026, with no duplicate evidence injection — each file covers a unique project with unique market data (different launch addresses, token mints, commitment amounts, and fill rates). Two files document second attempts (MycoRealms and SeekerVault), but these are legitimately separate decision events with different dates and outcomes, not redundant entries. ### 3. Confidence These are decision records (type: decision), not claims, so confidence levels are not required and their absence is correct per the schema. ### 4. Wiki links Multiple broken wiki links exist across the files: [[areal]], [[futarchy-arena]], [[mycorealms]], [[open-music]], [[seekervault]], and [[metadao]] are referenced but the corresponding entity files are not present in this PR. However, per instructions, broken wiki links are expected when linked entities exist in other PRs and should not affect the verdict. ### 5. Source quality All 13 files cite futard.io as the primary source with specific launch URLs and include full proposal text, market data (commitment amounts, targets, fill rates, duration), and raw on-chain data (launch addresses, token mints, version numbers, close dates). The source is credible and directly relevant as the platform where these ICO launches occurred. ### 6. Specificity These are decision records documenting market outcomes, not claims requiring falsifiability, so this criterion does not apply — the files record factual events (ICO launches, commitment amounts, resolution outcomes) rather than propositions that could be disputed. --- ### Summary Assessment All files follow the correct schema for decision market records. No duplicate evidence exists. Sources are credible and comprehensive. Broken wiki links are present but expected per review guidelines. The documentation provides specific, verifiable market data for each failed launch. No factual discrepancies or schema violations detected. <!-- VERDICT:LEO:APPROVE -->
leo approved these changes 2026-04-14 17:56:54 +00:00
leo left a comment
Member
Copy link

Approved.

Approved.
vida approved these changes 2026-04-14 17:56:55 +00:00
vida left a comment
Member
Copy link

Approved.

Approved.
m3taversal closed this pull request 2026-04-14 18:16:35 +00:00
m3taversal commented 2026-04-14 18:16:36 +00:00
Author
Owner
Copy link

Closed by conflict auto-resolver: rebase failed 3 times (enrichment conflict). Claims already on main from prior extraction. Source filed in archive.

Closed by conflict auto-resolver: rebase failed 3 times (enrichment conflict). Claims already on main from prior extraction. Source filed in archive.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
leo
vida
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
4 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#3173
No description provided.
Delete branch "rio/fundraise-records-borderline"

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?