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

ingestion: 158 futardio events — 20260310-1244 #117

Closed
m3taversal wants to merge 158 commits from ingestion/futardio-20260310-1244 into main
pull from: ingestion/futardio-20260310-1244
merge into: teleo:main
Conversation 26 Commits 158 Files changed 158 +17945
m3taversal commented 2026-03-10 12:46:36 +00:00
Owner
Copy link

Batch

  • 158 source files
  • Types: 70 launches, 90 proposals

Files

  • 2026-03-03-futardio-launch-manna-finance.md
  • 2026-03-03-futardio-launch-salmon-wallet.md
  • 2026-03-03-futardio-launch-versus.md
  • 2026-03-03-futardio-launch-digifrens.md
  • 2026-03-03-futardio-launch-cloak.md
  • 2026-03-04-futardio-launch-futarchy-arena.md
  • 2026-03-03-futardio-launch-vervepay.md
  • 2026-03-04-futardio-launch-xorrabet.md
  • 2026-03-04-futardio-launch-sizematters.md
  • 2026-03-04-futardio-launch-lososdao.md
  • 2026-03-03-futardio-launch-open-music.md
  • 2026-03-04-futardio-launch-superclaw.md
  • 2026-03-04-futardio-launch-test.md
  • 2026-03-05-futardio-launch-you-get-nothing.md
  • 2026-03-04-futardio-launch-seekervault.md
  • 2026-03-05-futardio-launch-blockrock.md
  • 2026-03-05-futardio-launch-futardio-boat.md
  • 2026-03-04-futardio-launch-money-for-steak.md
  • 2026-03-04-futardio-launch-futara.md
  • 2026-03-05-futardio-launch-launchpet.md
  • 2026-03-06-futardio-launch-lobsterfutarchy.md
  • 2026-03-05-futardio-launch-ludex-ai.md
  • 2026-03-05-futardio-launch-areal-finance.md
  • 2026-03-05-futardio-launch-phonon-studio-ai.md
  • 2026-03-07-futardio-launch-nexid.md
  • 2026-03-09-futardio-launch-etnlio.md
  • 2026-03-08-futardio-launch-seeker-vault.md
  • 2026-01-01-futardio-launch-mycorealms.md
  • 2026-03-03-futardio-launch-futardio-cult.md
  • 2026-03-07-futardio-launch-areal.md
  • 2026-03-05-futardio-launch-insert-coin-labs.md
  • 2026-03-04-futardio-launch-one-of-sick-token.md
  • 2026-03-04-futardio-launch-proph3t.md
  • 2026-03-04-futardio-launch-pli-crperie-ambulante.md
  • 2026-03-04-futardio-launch-irich.md
  • 2026-03-05-futardio-launch-runbookai.md
  • 2026-03-05-futardio-launch-git3.md
  • 2026-03-05-futardio-launch-bitfutard.md
  • 2026-03-05-futardio-launch-seyf.md
  • 2026-03-04-futardio-launch-island.md
  • 2026-03-04-futardio-launch-send-arcade.md
  • 2026-03-05-futardio-launch-torch-market.md
  • 2026-03-05-futardio-launch-tridash.md
  • 2026-02-17-futardio-launch-epic-finance.md
  • 2026-02-03-futardio-launch-hurupay.md
  • 2026-01-06-futardio-launch-ranger.md
  • 2026-01-01-futardio-launch-vaultguard.md
  • 2026-02-22-futardio-launch-salmon-wallet.md
  • 2026-02-21-futardio-launch-forevernow.md
  • 2026-02-17-futardio-launch-generated-test.md
  • 2026-02-25-futardio-launch-fancy-cats.md
  • 2026-02-25-futardio-launch-rabid-racers.md
  • 2026-02-25-futardio-launch-turtle-cove.md
  • 2026-02-25-futardio-launch-rock-game.md
  • 2026-02-25-futardio-launch-donuts.md
  • 2026-02-26-futardio-launch-delay-test.md
  • 2026-02-26-futardio-launch-fitbyte.md
  • 2026-02-28-futardio-launch-salmon-wallet.md
  • 2026-03-03-futardio-launch-the-meme-is-real.md
  • 2026-03-02-futardio-launch-reddit.md
  • 2026-03-03-futardio-launch-milo-ai-agent.md
  • 2026-03-03-futardio-launch-mycorealms.md
  • 2025-10-18-futardio-launch-loyal.md
  • 2025-10-06-futardio-launch-umbra.md
  • 2025-10-14-futardio-launch-avici.md
  • 2025-10-20-futardio-launch-zklsol.md
  • 2025-10-23-futardio-launch-paystream.md
  • 2025-11-14-futardio-launch-solomon.md
  • 2025-11-07-futardio-proposal-meta-pow-the-ore-treasury-protocol.md
  • 2025-10-22-futardio-proposal-defiance-capital-cloud-token-acquisition-proposal.md
  • 2025-10-15-futardio-proposal-lets-get-futarded.md
  • 2025-08-20-futardio-proposal-should-sanctum-offer-investors-early-unlocks-of-their-cloud.md
  • 2025-08-07-futardio-proposal-migrate-meta-token.md
  • 2025-07-21-futardio-proposal-engage-in-630000-otc-trade-with-theia.md
  • 2025-07-02-futardio-proposal-testing-indexer-changes.md
  • 2025-04-22-futardio-proposal-testing-v03-transfer.md
  • 2025-03-28-futardio-proposal-should-sanctum-build-a-sanctum-mobile-app-wonder.md
  • 2025-03-05-futardio-proposal-should-sanctum-use-up-to-25m-cloud-to-incentivise-inf-sol-li.md
  • 2025-03-05-futardio-proposal-proposal-2.md
  • 2025-03-05-futardio-proposal-proposal-1.md
  • 2025-03-05-futardio-proposal-proposal-3.md
  • 2025-02-26-futardio-proposal-release-a-launchpad.md
  • 2025-02-24-futardio-proposal-mtn-meets-meta-hackathon.md
  • 2025-02-24-futardio-proposal-testing-totem-for-the-win.md
  • 2025-02-13-futardio-proposal-fund-the-drift-working-group.md
  • 2025-02-10-futardio-proposal-should-metadao-hire-robin-hanson-as-an-advisor.md
  • 2025-02-10-futardio-proposal-addy-dao-proposal.md
  • 2025-02-06-futardio-proposal-should-sanctum-implement-cloud-staking-and-active-staking-re.md
  • 2025-02-04-futardio-proposal-should-a-percentage-of-sam-bids-route-to-mnde-stakers.md
  • 2025-02-03-futardio-proposal-should-sanctum-change-its-logo-on-its-website-and-socials.md
  • 2025-01-28-futardio-proposal-perform-token-split-and-adopt-elastic-supply-for-meta.md
  • 2025-01-27-futardio-proposal-engage-in-500000-otc-trade-with-theia-2.md
  • 2025-01-14-futardio-proposal-should-deans-list-dao-update-the-liquidity-fee-structure.md
  • 2025-01-13-futardio-proposal-should-jto-vault-be-added-to-tiprouter-ncn.md
  • 2025-01-03-futardio-proposal-engage-in-700000-otc-trade-with-theia.md
  • 2024-12-30-futardio-proposal-fund-deans-list-dao-website-redesign.md
  • 2024-12-19-futardio-proposal-allocate-50000-drift-to-fund-the-drift-ai-agent-request-for.md
  • 2024-12-16-futardio-proposal-implement-3-week-vesting-for-dao-payments-to-strengthen-ecos.md
  • 2024-12-05-futardio-proposal-establish-development-fund.md
  • 2024-12-04-futardio-proposal-launch-a-boost-for-usdc-ore.md
  • 2024-12-02-futardio-proposal-approve-deans-list-treasury-management.md
  • 2024-11-25-futardio-proposal-launch-a-boost-for-hnt-ore.md
  • 2024-11-25-futardio-proposal-prioritize-listing-meta.md
  • 2024-11-21-futardio-proposal-should-metadao-create-futardio.md
  • 2024-11-21-futardio-proposal-proposal-14.md
  • 2024-11-21-futardio-proposal-proposal-13.md
  • 2024-11-18-futardio-proposal-adopt-a-sublinear-supply-function.md
  • 2024-11-13-futardio-proposal-cut-emissions-by-50.md
  • 2024-11-08-futardio-proposal-initiate-liquidity-farming-for-future-on-raydium.md
  • 2024-10-30-futardio-proposal-swap-150000-into-isc.md
  • 2024-10-22-futardio-proposal-increase-ore-sol-lp-boost-multiplier-to-6x.md
  • 2024-10-22-futardio-proposal-hire-advaith-sekharan-as-founding-engineer.md
  • 2024-10-10-futardio-proposal-treasury-proposal-deans-list-proposal.md
  • 2024-09-05-futardio-proposal-my-test-proposal-that-rocksswd.md
  • 2024-08-31-futardio-proposal-enter-services-agreement-with-organization-technology-llc.md
  • 2024-08-30-futardio-proposal-approve-budget-for-pre-governance-hackathon-development.md
  • 2024-08-28-futardio-proposal-a-very-unique-title-some-say-its-really-unique.md
  • 2024-08-28-futardio-proposal-dummy.md
  • 2024-08-28-futardio-proposal-test-proposal-based-on-metadao-content.md
  • 2024-08-28-futardio-proposal-proposal-7.md
  • 2024-08-28-futardio-proposal-drift-proposal-for-bet.md
  • 2024-08-27-futardio-proposal-fund-the-drift-superteam-earn-creator-competition.md
  • 2024-08-20-futardio-proposal-test-proposal-3.md
  • 2024-08-20-futardio-proposal-proposal-4.md
  • 2024-08-14-futardio-proposal-develop-memecoin-launchpad.md
  • 2024-08-03-futardio-proposal-approve-q3-roadmap.md
  • 2024-07-18-futardio-proposal-enhancing-the-deans-list-dao-economic-model.md
  • 2024-07-18-futardio-proposal-approve-budget-for-champions-nft-collection-design.md
  • 2024-07-09-futardio-proposal-initialize-the-drift-foundation-grant-program.md
  • 2024-07-04-futardio-proposal-proposal-3.md
  • 2024-07-01-futardio-proposal-test.md
  • 2024-07-01-futardio-proposal-proposal-1.md
  • 2024-07-01-futardio-proposal-fund-artemis-labs-data-and-analytics-dashboards.md
  • 2024-06-26-futardio-proposal-approve-metadao-fundraise-2.md
  • 2024-06-22-futardio-proposal-thailanddao-event-promotion-to-boost-deans-list-dao-engageme.md
  • 2024-06-14-futardio-proposal-fund-the-rug-bounty-program.md
  • 2024-06-08-futardio-proposal-reward-the-university-of-waterloo-blockchain-club-with-1-mil.md
  • 2024-06-05-futardio-proposal-fund-futuredaos-token-migrator.md
  • 2024-05-30-futardio-proposal-drift-futarchy-proposal-welcome-the-futarchs.md
  • 2024-05-30-futardio-proposal-proposal-1.md
  • 2024-05-27-futardio-proposal-approve-performance-based-compensation-package-for-proph3t-a.md
  • 2024-05-27-futardio-proposal-proposal-1.md
  • 2024-03-28-futardio-proposal-migrate-autocrat-program-to-v02.md
  • 2024-03-26-futardio-proposal-appoint-nallok-and-proph3t-benevolent-dictators-for-three-mo.md
  • 2024-03-19-futardio-proposal-engage-in-250000-otc-trade-with-colosseum.md
  • 2024-03-13-futardio-proposal-develop-futarchy-as-a-service-faas.md
  • 2024-03-03-futardio-proposal-burn-993-of-meta-in-treasury.md
  • 2024-02-26-futardio-proposal-increase-meta-liquidity-via-a-dutch-auction.md
  • 2024-02-20-futardio-proposal-develop-multi-option-proposals.md
  • 2024-02-18-futardio-proposal-engage-in-100000-otc-trade-with-ben-hawkins-2.md
  • 2024-02-18-futardio-proposal-engage-in-50000-otc-trade-with-pantera-capital.md
  • 2024-02-13-futardio-proposal-engage-in-50000-otc-trade-with-ben-hawkins.md
  • 2024-02-05-futardio-proposal-execute-creation-of-spot-market-for-meta.md
  • 2024-01-24-futardio-proposal-develop-amm-program-for-futarchy.md
  • 2024-01-12-futardio-proposal-create-spot-market-for-meta.md
  • 2023-12-16-futardio-proposal-develop-a-saber-vote-market.md
  • 2023-12-03-futardio-proposal-migrate-autocrat-program-to-v01.md
  • 2023-11-18-futardio-proposal-develop-a-lst-vote-market.md

Automated futardio ingestion daemon.

## Batch - 158 source files - Types: 70 launches, 90 proposals ## Files - `2026-03-03-futardio-launch-manna-finance.md` - `2026-03-03-futardio-launch-salmon-wallet.md` - `2026-03-03-futardio-launch-versus.md` - `2026-03-03-futardio-launch-digifrens.md` - `2026-03-03-futardio-launch-cloak.md` - `2026-03-04-futardio-launch-futarchy-arena.md` - `2026-03-03-futardio-launch-vervepay.md` - `2026-03-04-futardio-launch-xorrabet.md` - `2026-03-04-futardio-launch-sizematters.md` - `2026-03-04-futardio-launch-lososdao.md` - `2026-03-03-futardio-launch-open-music.md` - `2026-03-04-futardio-launch-superclaw.md` - `2026-03-04-futardio-launch-test.md` - `2026-03-05-futardio-launch-you-get-nothing.md` - `2026-03-04-futardio-launch-seekervault.md` - `2026-03-05-futardio-launch-blockrock.md` - `2026-03-05-futardio-launch-futardio-boat.md` - `2026-03-04-futardio-launch-money-for-steak.md` - `2026-03-04-futardio-launch-futara.md` - `2026-03-05-futardio-launch-launchpet.md` - `2026-03-06-futardio-launch-lobsterfutarchy.md` - `2026-03-05-futardio-launch-ludex-ai.md` - `2026-03-05-futardio-launch-areal-finance.md` - `2026-03-05-futardio-launch-phonon-studio-ai.md` - `2026-03-07-futardio-launch-nexid.md` - `2026-03-09-futardio-launch-etnlio.md` - `2026-03-08-futardio-launch-seeker-vault.md` - `2026-01-01-futardio-launch-mycorealms.md` - `2026-03-03-futardio-launch-futardio-cult.md` - `2026-03-07-futardio-launch-areal.md` - `2026-03-05-futardio-launch-insert-coin-labs.md` - `2026-03-04-futardio-launch-one-of-sick-token.md` - `2026-03-04-futardio-launch-proph3t.md` - `2026-03-04-futardio-launch-pli-crperie-ambulante.md` - `2026-03-04-futardio-launch-irich.md` - `2026-03-05-futardio-launch-runbookai.md` - `2026-03-05-futardio-launch-git3.md` - `2026-03-05-futardio-launch-bitfutard.md` - `2026-03-05-futardio-launch-seyf.md` - `2026-03-04-futardio-launch-island.md` - `2026-03-04-futardio-launch-send-arcade.md` - `2026-03-05-futardio-launch-torch-market.md` - `2026-03-05-futardio-launch-tridash.md` - `2026-02-17-futardio-launch-epic-finance.md` - `2026-02-03-futardio-launch-hurupay.md` - `2026-01-06-futardio-launch-ranger.md` - `2026-01-01-futardio-launch-vaultguard.md` - `2026-02-22-futardio-launch-salmon-wallet.md` - `2026-02-21-futardio-launch-forevernow.md` - `2026-02-17-futardio-launch-generated-test.md` - `2026-02-25-futardio-launch-fancy-cats.md` - `2026-02-25-futardio-launch-rabid-racers.md` - `2026-02-25-futardio-launch-turtle-cove.md` - `2026-02-25-futardio-launch-rock-game.md` - `2026-02-25-futardio-launch-donuts.md` - `2026-02-26-futardio-launch-delay-test.md` - `2026-02-26-futardio-launch-fitbyte.md` - `2026-02-28-futardio-launch-salmon-wallet.md` - `2026-03-03-futardio-launch-the-meme-is-real.md` - `2026-03-02-futardio-launch-reddit.md` - `2026-03-03-futardio-launch-milo-ai-agent.md` - `2026-03-03-futardio-launch-mycorealms.md` - `2025-10-18-futardio-launch-loyal.md` - `2025-10-06-futardio-launch-umbra.md` - `2025-10-14-futardio-launch-avici.md` - `2025-10-20-futardio-launch-zklsol.md` - `2025-10-23-futardio-launch-paystream.md` - `2025-11-14-futardio-launch-solomon.md` - `2025-11-07-futardio-proposal-meta-pow-the-ore-treasury-protocol.md` - `2025-10-22-futardio-proposal-defiance-capital-cloud-token-acquisition-proposal.md` - `2025-10-15-futardio-proposal-lets-get-futarded.md` - `2025-08-20-futardio-proposal-should-sanctum-offer-investors-early-unlocks-of-their-cloud.md` - `2025-08-07-futardio-proposal-migrate-meta-token.md` - `2025-07-21-futardio-proposal-engage-in-630000-otc-trade-with-theia.md` - `2025-07-02-futardio-proposal-testing-indexer-changes.md` - `2025-04-22-futardio-proposal-testing-v03-transfer.md` - `2025-03-28-futardio-proposal-should-sanctum-build-a-sanctum-mobile-app-wonder.md` - `2025-03-05-futardio-proposal-should-sanctum-use-up-to-25m-cloud-to-incentivise-inf-sol-li.md` - `2025-03-05-futardio-proposal-proposal-2.md` - `2025-03-05-futardio-proposal-proposal-1.md` - `2025-03-05-futardio-proposal-proposal-3.md` - `2025-02-26-futardio-proposal-release-a-launchpad.md` - `2025-02-24-futardio-proposal-mtn-meets-meta-hackathon.md` - `2025-02-24-futardio-proposal-testing-totem-for-the-win.md` - `2025-02-13-futardio-proposal-fund-the-drift-working-group.md` - `2025-02-10-futardio-proposal-should-metadao-hire-robin-hanson-as-an-advisor.md` - `2025-02-10-futardio-proposal-addy-dao-proposal.md` - `2025-02-06-futardio-proposal-should-sanctum-implement-cloud-staking-and-active-staking-re.md` - `2025-02-04-futardio-proposal-should-a-percentage-of-sam-bids-route-to-mnde-stakers.md` - `2025-02-03-futardio-proposal-should-sanctum-change-its-logo-on-its-website-and-socials.md` - `2025-01-28-futardio-proposal-perform-token-split-and-adopt-elastic-supply-for-meta.md` - `2025-01-27-futardio-proposal-engage-in-500000-otc-trade-with-theia-2.md` - `2025-01-14-futardio-proposal-should-deans-list-dao-update-the-liquidity-fee-structure.md` - `2025-01-13-futardio-proposal-should-jto-vault-be-added-to-tiprouter-ncn.md` - `2025-01-03-futardio-proposal-engage-in-700000-otc-trade-with-theia.md` - `2024-12-30-futardio-proposal-fund-deans-list-dao-website-redesign.md` - `2024-12-19-futardio-proposal-allocate-50000-drift-to-fund-the-drift-ai-agent-request-for.md` - `2024-12-16-futardio-proposal-implement-3-week-vesting-for-dao-payments-to-strengthen-ecos.md` - `2024-12-05-futardio-proposal-establish-development-fund.md` - `2024-12-04-futardio-proposal-launch-a-boost-for-usdc-ore.md` - `2024-12-02-futardio-proposal-approve-deans-list-treasury-management.md` - `2024-11-25-futardio-proposal-launch-a-boost-for-hnt-ore.md` - `2024-11-25-futardio-proposal-prioritize-listing-meta.md` - `2024-11-21-futardio-proposal-should-metadao-create-futardio.md` - `2024-11-21-futardio-proposal-proposal-14.md` - `2024-11-21-futardio-proposal-proposal-13.md` - `2024-11-18-futardio-proposal-adopt-a-sublinear-supply-function.md` - `2024-11-13-futardio-proposal-cut-emissions-by-50.md` - `2024-11-08-futardio-proposal-initiate-liquidity-farming-for-future-on-raydium.md` - `2024-10-30-futardio-proposal-swap-150000-into-isc.md` - `2024-10-22-futardio-proposal-increase-ore-sol-lp-boost-multiplier-to-6x.md` - `2024-10-22-futardio-proposal-hire-advaith-sekharan-as-founding-engineer.md` - `2024-10-10-futardio-proposal-treasury-proposal-deans-list-proposal.md` - `2024-09-05-futardio-proposal-my-test-proposal-that-rocksswd.md` - `2024-08-31-futardio-proposal-enter-services-agreement-with-organization-technology-llc.md` - `2024-08-30-futardio-proposal-approve-budget-for-pre-governance-hackathon-development.md` - `2024-08-28-futardio-proposal-a-very-unique-title-some-say-its-really-unique.md` - `2024-08-28-futardio-proposal-dummy.md` - `2024-08-28-futardio-proposal-test-proposal-based-on-metadao-content.md` - `2024-08-28-futardio-proposal-proposal-7.md` - `2024-08-28-futardio-proposal-drift-proposal-for-bet.md` - `2024-08-27-futardio-proposal-fund-the-drift-superteam-earn-creator-competition.md` - `2024-08-20-futardio-proposal-test-proposal-3.md` - `2024-08-20-futardio-proposal-proposal-4.md` - `2024-08-14-futardio-proposal-develop-memecoin-launchpad.md` - `2024-08-03-futardio-proposal-approve-q3-roadmap.md` - `2024-07-18-futardio-proposal-enhancing-the-deans-list-dao-economic-model.md` - `2024-07-18-futardio-proposal-approve-budget-for-champions-nft-collection-design.md` - `2024-07-09-futardio-proposal-initialize-the-drift-foundation-grant-program.md` - `2024-07-04-futardio-proposal-proposal-3.md` - `2024-07-01-futardio-proposal-test.md` - `2024-07-01-futardio-proposal-proposal-1.md` - `2024-07-01-futardio-proposal-fund-artemis-labs-data-and-analytics-dashboards.md` - `2024-06-26-futardio-proposal-approve-metadao-fundraise-2.md` - `2024-06-22-futardio-proposal-thailanddao-event-promotion-to-boost-deans-list-dao-engageme.md` - `2024-06-14-futardio-proposal-fund-the-rug-bounty-program.md` - `2024-06-08-futardio-proposal-reward-the-university-of-waterloo-blockchain-club-with-1-mil.md` - `2024-06-05-futardio-proposal-fund-futuredaos-token-migrator.md` - `2024-05-30-futardio-proposal-drift-futarchy-proposal-welcome-the-futarchs.md` - `2024-05-30-futardio-proposal-proposal-1.md` - `2024-05-27-futardio-proposal-approve-performance-based-compensation-package-for-proph3t-a.md` - `2024-05-27-futardio-proposal-proposal-1.md` - `2024-03-28-futardio-proposal-migrate-autocrat-program-to-v02.md` - `2024-03-26-futardio-proposal-appoint-nallok-and-proph3t-benevolent-dictators-for-three-mo.md` - `2024-03-19-futardio-proposal-engage-in-250000-otc-trade-with-colosseum.md` - `2024-03-13-futardio-proposal-develop-futarchy-as-a-service-faas.md` - `2024-03-03-futardio-proposal-burn-993-of-meta-in-treasury.md` - `2024-02-26-futardio-proposal-increase-meta-liquidity-via-a-dutch-auction.md` - `2024-02-20-futardio-proposal-develop-multi-option-proposals.md` - `2024-02-18-futardio-proposal-engage-in-100000-otc-trade-with-ben-hawkins-2.md` - `2024-02-18-futardio-proposal-engage-in-50000-otc-trade-with-pantera-capital.md` - `2024-02-13-futardio-proposal-engage-in-50000-otc-trade-with-ben-hawkins.md` - `2024-02-05-futardio-proposal-execute-creation-of-spot-market-for-meta.md` - `2024-01-24-futardio-proposal-develop-amm-program-for-futarchy.md` - `2024-01-12-futardio-proposal-create-spot-market-for-meta.md` - `2023-12-16-futardio-proposal-develop-a-saber-vote-market.md` - `2023-12-03-futardio-proposal-migrate-autocrat-program-to-v01.md` - `2023-11-18-futardio-proposal-develop-a-lst-vote-market.md` Automated futardio ingestion daemon.
m3taversal added 158 commits 2026-03-10 12:46:36 +00:00
leo commented 2026-03-10 12:46:51 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), theseus (domain-peer, sonnet) *teleo-eval-orchestrator v2*
theseus commented 2026-03-10 12:47:58 +00:00
Member
Copy link

Theseus Domain Peer Review — PR #117

PR scope: 150+ archived source files from futard.io, covering MetaDAO governance proposals (2023–2025) and Futardio launch events (2025–2026). All files are type: source, domain: internet-finance, status: unprocessed. No claims are being proposed — this is pure ingestion.

Domain Relevance Assessment

This PR is squarely in Rio's territory (internet-finance / futarchy). My domain (AI/alignment) has no direct jurisdiction here. I have no technical accuracy concerns to raise about the futarchy mechanism design content — that's Rio's call. What I can do is flag cross-domain signals worth preserving for future extraction.

AI-Adjacent Materials Worth Flagging

Two archived files touch AI in ways that could matter later:

2024-12-19-futardio-proposal-allocate-50000-drift-to-fund-the-drift-ai-agent-request-for.md — Drift DAO used futarchic governance to fund an AI Agents grants program. The proposal defines what qualifies as a "DeFi agent" (autonomous, multi-tool, off-chain with on-chain interaction). This is early empirical evidence of futarchy being used to make resource allocation decisions about AI development — relevant to the claim that market-tested governance could outperform committee-based AI governance. Not extraction-ready yet, but worth noting when Rio eventually processes this file.

2026-03-03-futardio-launch-milo-ai-agent.md — A futardio launch for an AI real estate agent that raised $200 of a $250,000 target and entered refunding. Weak signal on its own, but part of a broader pattern in the launch files showing AI agent projects attempting futarchic fundraising with mixed results. If there are enough of these, it could yield a claim about futarchy's effectiveness (or limitations) as a funding mechanism for AI applications.

2025-02-10-futardio-proposal-should-metadao-hire-robin-hanson-as-an-advisor.md — Robin Hanson (futarchy's inventor) was hired as an advisor to MetaDAO, passing the vote. This is notable for provenance: if claims get extracted about futarchy mechanism design from later MetaDAO materials, Hanson's direct involvement is relevant context. Passed 2025-02-13.

No Domain-Specific Concerns

The archive structure, frontmatter schema, and tagging are consistent throughout. The AI-adjacent files are correctly classified as internet-finance — they're governance/funding decisions, not AI alignment content. Nothing here should be re-routed to my domain.

Verdict: approve
Model: sonnet
Summary: No AI/alignment domain issues. This is a clean internet-finance ingestion batch. Three files contain AI-adjacent signals worth noting when Rio processes them for extraction — the Drift AI Agents RFG (futarchy governing AI funding), the Milo AI Agent launch (failed AI fundraise via futarchy), and the Robin Hanson hire (primary source on futarchy mechanism design from its inventor). No action needed from my domain.

# Theseus Domain Peer Review — PR #117 **PR scope:** 150+ archived source files from futard.io, covering MetaDAO governance proposals (2023–2025) and Futardio launch events (2025–2026). All files are `type: source`, `domain: internet-finance`, `status: unprocessed`. No claims are being proposed — this is pure ingestion. --- ## Domain Relevance Assessment This PR is squarely in Rio's territory (internet-finance / futarchy). My domain (AI/alignment) has no direct jurisdiction here. I have no technical accuracy concerns to raise about the futarchy mechanism design content — that's Rio's call. What I can do is flag cross-domain signals worth preserving for future extraction. ## AI-Adjacent Materials Worth Flagging Two archived files touch AI in ways that could matter later: **`2024-12-19-futardio-proposal-allocate-50000-drift-to-fund-the-drift-ai-agent-request-for.md`** — Drift DAO used futarchic governance to fund an AI Agents grants program. The proposal defines what qualifies as a "DeFi agent" (autonomous, multi-tool, off-chain with on-chain interaction). This is early empirical evidence of futarchy being used to make resource allocation decisions about AI development — relevant to the claim that market-tested governance could outperform committee-based AI governance. Not extraction-ready yet, but worth noting when Rio eventually processes this file. **`2026-03-03-futardio-launch-milo-ai-agent.md`** — A futardio launch for an AI real estate agent that raised $200 of a $250,000 target and entered refunding. Weak signal on its own, but part of a broader pattern in the launch files showing AI agent projects attempting futarchic fundraising with mixed results. If there are enough of these, it could yield a claim about futarchy's effectiveness (or limitations) as a funding mechanism for AI applications. **`2025-02-10-futardio-proposal-should-metadao-hire-robin-hanson-as-an-advisor.md`** — Robin Hanson (futarchy's inventor) was hired as an advisor to MetaDAO, passing the vote. This is notable for provenance: if claims get extracted about futarchy mechanism design from later MetaDAO materials, Hanson's direct involvement is relevant context. Passed 2025-02-13. ## No Domain-Specific Concerns The archive structure, frontmatter schema, and tagging are consistent throughout. The AI-adjacent files are correctly classified as `internet-finance` — they're governance/funding decisions, not AI alignment content. Nothing here should be re-routed to my domain. --- **Verdict:** approve **Model:** sonnet **Summary:** No AI/alignment domain issues. This is a clean internet-finance ingestion batch. Three files contain AI-adjacent signals worth noting when Rio processes them for extraction — the Drift AI Agents RFG (futarchy governing AI funding), the Milo AI Agent launch (failed AI fundraise via futarchy), and the Robin Hanson hire (primary source on futarchy mechanism design from its inventor). No action needed from my domain. <!-- VERDICT:THESEUS:APPROVE -->
leo commented 2026-03-10 12:48:24 +00:00
Member
Copy link

Leo — Cross-Domain Review: PR #117

PR: ingestion/futardio-20260310-1244
Scope: 158 source archive files (90 proposals, 68 launches) from futard.io
Type: Bulk data ingestion — source archiving only, no claims proposed

Issues

1. Test/spam data should be excluded or flagged

The archive includes obvious test and spam entries with zero informational value:

  • 2024-08-20-futardio-proposal-test-proposal-3.md — content is literally "Test Proposal 3 Content", project listed as "Unknown"
  • 2024-08-28-futardio-proposal-dummy.md — description is "Nothing", project is "Test DAO"
  • 2024-05-27-futardio-proposal-proposal-1.md — empty proposal, no content, project "Unknown"
  • 2024-05-30-futardio-proposal-proposal-1.md — same pattern
  • 2024-07-01-futardio-proposal-proposal-1.md, proposal-3.md — likely test entries
  • 2024-08-28-futardio-proposal-test-proposal-based-on-metadao-content.md — test
  • 2024-08-28-futardio-proposal-a-very-unique-title-some-say-its-really-unique.md — test
  • 2026-02-17-futardio-launch-generated-test.md — mockToken template, $10 funding target
  • 2026-02-26-futardio-launch-delay-test.md — likely test
  • 2024-09-05-futardio-proposal-my-test-proposal-that-rocksswd.md — test

These will never yield claims and add noise to the archive. Either exclude them or at minimum set status: null-result with notes: "test/spam proposal, no extractable content" so no agent wastes time on them.

2. Schema extensions are undocumented

Two non-standard fields appear across all files:

  • format: data — not in the schema enum (which allows: essay, newsletter, tweet, thread, whitepaper, paper, report, news). "data" is a reasonable addition for structured on-chain records, but it should be added to schemas/source.md in this PR.
  • event_type: proposal | launch — not in the source schema at all. This is useful metadata but should be documented, or use the existing tags field instead.

3. Missing Pentagon-Agent trailers

None of the 158 commits include the required Pentagon-Agent: trailer. Per CLAUDE.md, this is essential for tracing which agent authored each commit. If this was automated ingestion (not agent-authored), the commit format should still identify the ingestion system.

4. Branch naming

Branch is ingestion/futardio-20260310-1244 — doesn't follow the {agent-name}/{description} convention. If this was automated pipeline work rather than agent work, that's fine but worth noting.

Observations (not blocking)

Signal-to-noise ratio: The substantive proposals (MetaDAO treasury management, protocol upgrades, OTC trades, hiring decisions, Futarchy-as-a-Service) are genuinely valuable primary source material for Rio's internet-finance domain. The early MetaDAO proposals (2023-2024) document real futarchy governance in action — proposal structures, financial projections, market outcomes. This is exactly the kind of raw data the KB needs.

Launch data tells a story: The launches show futard.io evolving from MetaDAO governance tool to a broader futarchy launchpad (2025-2026). Several launches raised significant capital (Umbra: $155M committed on $750K target). Others raised near-zero (Etnl.io: $96 on $500K target). The pass/fail distribution is itself evidence for existing claims about futarchy's information aggregation properties.

Cross-domain connections: Some proposals touch entertainment/cultural dynamics (Champions NFT collection, ThailandDAO event promotion) and AI (Drift AI Agent RFP, Milo AI Agent launch, Phonon Studio AI, RunbookAI, Ludex AI). These could be flagged for Clay and Theseus respectively during extraction.

Extraction priority: The early MetaDAO governance proposals (2023-2024) are the highest-value sources — they contain detailed financial reasoning, market mechanism design, and outcome data that directly feed existing claims about futarchy implementation. The 2025-2026 launches are useful as aggregate data but individually less extractable.

Verdict: request_changes
Model: opus
Summary: Valuable bulk ingestion of 158 futardio source archives covering 2+ years of real futarchy governance data. Three issues: (1) ~10 test/spam entries should be excluded or pre-marked as null-result, (2) non-standard schema fields (format: data, event_type) need documentation in schemas/source.md, (3) commits missing Pentagon-Agent trailers.

# Leo — Cross-Domain Review: PR #117 **PR:** ingestion/futardio-20260310-1244 **Scope:** 158 source archive files (90 proposals, 68 launches) from futard.io **Type:** Bulk data ingestion — source archiving only, no claims proposed --- ## Issues ### 1. Test/spam data should be excluded or flagged The archive includes obvious test and spam entries with zero informational value: - `2024-08-20-futardio-proposal-test-proposal-3.md` — content is literally "Test Proposal 3 Content", project listed as "Unknown" - `2024-08-28-futardio-proposal-dummy.md` — description is "Nothing", project is "Test DAO" - `2024-05-27-futardio-proposal-proposal-1.md` — empty proposal, no content, project "Unknown" - `2024-05-30-futardio-proposal-proposal-1.md` — same pattern - `2024-07-01-futardio-proposal-proposal-1.md`, `proposal-3.md` — likely test entries - `2024-08-28-futardio-proposal-test-proposal-based-on-metadao-content.md` — test - `2024-08-28-futardio-proposal-a-very-unique-title-some-say-its-really-unique.md` — test - `2026-02-17-futardio-launch-generated-test.md` — mockToken template, $10 funding target - `2026-02-26-futardio-launch-delay-test.md` — likely test - `2024-09-05-futardio-proposal-my-test-proposal-that-rocksswd.md` — test These will never yield claims and add noise to the archive. Either exclude them or at minimum set `status: null-result` with `notes: "test/spam proposal, no extractable content"` so no agent wastes time on them. ### 2. Schema extensions are undocumented Two non-standard fields appear across all files: - **`format: data`** — not in the schema enum (which allows: essay, newsletter, tweet, thread, whitepaper, paper, report, news). "data" is a reasonable addition for structured on-chain records, but it should be added to `schemas/source.md` in this PR. - **`event_type: proposal | launch`** — not in the source schema at all. This is useful metadata but should be documented, or use the existing `tags` field instead. ### 3. Missing Pentagon-Agent trailers None of the 158 commits include the required `Pentagon-Agent:` trailer. Per CLAUDE.md, this is essential for tracing which agent authored each commit. If this was automated ingestion (not agent-authored), the commit format should still identify the ingestion system. ### 4. Branch naming Branch is `ingestion/futardio-20260310-1244` — doesn't follow the `{agent-name}/{description}` convention. If this was automated pipeline work rather than agent work, that's fine but worth noting. ## Observations (not blocking) **Signal-to-noise ratio:** The substantive proposals (MetaDAO treasury management, protocol upgrades, OTC trades, hiring decisions, Futarchy-as-a-Service) are genuinely valuable primary source material for Rio's internet-finance domain. The early MetaDAO proposals (2023-2024) document real futarchy governance in action — proposal structures, financial projections, market outcomes. This is exactly the kind of raw data the KB needs. **Launch data tells a story:** The launches show futard.io evolving from MetaDAO governance tool to a broader futarchy launchpad (2025-2026). Several launches raised significant capital (Umbra: $155M committed on $750K target). Others raised near-zero (Etnl.io: $96 on $500K target). The pass/fail distribution is itself evidence for existing claims about futarchy's information aggregation properties. **Cross-domain connections:** Some proposals touch entertainment/cultural dynamics (Champions NFT collection, ThailandDAO event promotion) and AI (Drift AI Agent RFP, Milo AI Agent launch, Phonon Studio AI, RunbookAI, Ludex AI). These could be flagged for Clay and Theseus respectively during extraction. **Extraction priority:** The early MetaDAO governance proposals (2023-2024) are the highest-value sources — they contain detailed financial reasoning, market mechanism design, and outcome data that directly feed existing claims about futarchy implementation. The 2025-2026 launches are useful as aggregate data but individually less extractable. --- **Verdict:** request_changes **Model:** opus **Summary:** Valuable bulk ingestion of 158 futardio source archives covering 2+ years of real futarchy governance data. Three issues: (1) ~10 test/spam entries should be excluded or pre-marked as null-result, (2) non-standard schema fields (`format: data`, `event_type`) need documentation in schemas/source.md, (3) commits missing Pentagon-Agent trailers. <!-- VERDICT:LEO:REQUEST_CHANGES -->
leo commented 2026-03-10 12:48:24 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
leo requested changes 2026-03-10 14:02:13 +00:00
leo left a comment
Member
Copy link

Leo Review - PR #117 (Futardio Ingestion)

Good: Rich structured data. Format matches our source schema. 158 files is a solid initial batch.

Issues to fix before merge

1. Dedup needed - multiple files for the same project:

  • salmon-wallet appears 3x (Feb 22, Feb 28, Mar 3)
  • mycorealms appears 2x (Jan 1, Mar 3)
  • seeker-vault vs seekervault - same project, different slug
  • areal vs areal-finance - likely same project

Suggest: key dedup on launch address (on-chain identifier), not project name or date.

2. Committed vs Raised distinction - Total committed shows strategic over-bidding amounts (e.g. Umbra: 155M committed, 3M final raise). Under the old pro-rata mechanism, contributors bid multiples of desired allocation. Suggest: surface Final raise prominently, add context.

3. Test/junk launches - Generated Test (10 dollar target), TEST (9 dollars committed), Delay Test, VaultGuard (10 dollar target). Consider filtering or tagging as test data.

Research note for Rio

The committed/raised ratio is a rich signal about mechanism design. Old pro-rata mechanism led to massive over-contribution (50x for Umbra). Polymarket interaction on committed amounts added speculative dynamics. Warrants a dedicated research task.

-- Leo

## Leo Review - PR #117 (Futardio Ingestion) **Good:** Rich structured data. Format matches our source schema. 158 files is a solid initial batch. ### Issues to fix before merge **1. Dedup needed** - multiple files for the same project: - salmon-wallet appears 3x (Feb 22, Feb 28, Mar 3) - mycorealms appears 2x (Jan 1, Mar 3) - seeker-vault vs seekervault - same project, different slug - areal vs areal-finance - likely same project Suggest: key dedup on launch address (on-chain identifier), not project name or date. **2. Committed vs Raised distinction** - Total committed shows strategic over-bidding amounts (e.g. Umbra: 155M committed, 3M final raise). Under the old pro-rata mechanism, contributors bid multiples of desired allocation. Suggest: surface Final raise prominently, add context. **3. Test/junk launches** - Generated Test (10 dollar target), TEST (9 dollars committed), Delay Test, VaultGuard (10 dollar target). Consider filtering or tagging as test data. ### Research note for Rio The committed/raised ratio is a rich signal about mechanism design. Old pro-rata mechanism led to massive over-contribution (50x for Umbra). Polymarket interaction on committed amounts added speculative dynamics. Warrants a dedicated research task. -- Leo
m3taversal commented 2026-03-11 12:40:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:40:40 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:45:39 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:45:39 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:50:39 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:50:40 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:55:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 12:55:40 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:00:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:00:41 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:05:39 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:05:39 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:10:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:10:40 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:15:39 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:15:39 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:20:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:20:40 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:25:39 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:25:39 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:30:40 +00:00
Author
Owner
Copy link

Leo review failed (timeout or error). Manual review required.

Leo review failed (timeout or error). Manual review required.
m3taversal commented 2026-03-11 13:30:41 +00:00
Author
Owner
Copy link

Domain review failed (timeout or error). Manual review required.

Domain review failed (timeout or error). Manual review required.
m3taversal closed this pull request 2026-03-11 13:33:18 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
leo
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#117
No description provided.
Delete branch "ingestion/futardio-20260310-1244"

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?