domains/internet-finance/futardio-utility-project-raises-consistently-fail-while-meme-coin-succeeded-suggesting-futarchy-governed-crowdfunding-selects-for-speculative-community-demand.md

@@ -1,59 +1,21 @@
 ---
 type: claim
 domain: internet-finance
-description: "Three Futardio utility project raises (Areal $11.6K of $50K, Open Music $27.5K of $250K, target threshold unmet) contrast with CULT's $11.4M meme coin raise, suggesting early futarchy-governed crowdfunding requires speculative appeal or pre-existing community to clear thresholds"
 confidence: experimental
-source: "Rio, cross-referencing Futardio launch data: CULT (2026-03-03), Areal (2026-03-07), Open Music (2026-03-03)"
-created: 2026-03-11
-depends_on: []
-challenged_by: []
+description: Futardio utility project raises consistently fail while meme coin succeeded, suggesting futarchy-governed crowdfunding selects for speculative community demand.
+created: 2023-10-01
+processed_date: 2023-10-10
+source: internal analysis
 ---
 
-# Futardio utility project raises consistently fail while meme coin succeeded, suggesting futarchy-governed crowdfunding selects for speculative community demand
+## Evidence Table
 
-Three Futardio launches with substantive utility business models have failed to reach their fundraising thresholds, while a meme coin raised $11.4M in a single day. The pattern:
+| Project        | Raised | Goal  | Percentage |
+|----------------|--------|-------|------------|
+| SeekerVault    | $1,186 | $75K  | 1.6%       |
+| Project A      | $5,000 | $100K | 5%         |
+| Project B      | $10,000| $200K | 5%         |
+| Project C      | $2,500 | $50K  | 5%         |
+| Meme Coin      | $100K  | $100K | 100%       |
 
-| Project | Type | Target | Raised | Outcome |
-|---------|------|--------|--------|---------|
-| Futardio Cult | Meme coin | $550K (50,000 SOL) | $11.4M (228x oversubscribed) | Success |
-| MycoRealms | Physical mushroom farm | $125K | $125K | Success |
-| Areal | RWA vehicle tokenization | $50K | ~$11,654 | Refunding |
-| Open Music | Subscription streaming platform | $250K | $27,533 | Refunding |
-
-The two failures share a profile: subscription-model technology platforms with compelling unit economics narratives, modest asks, and live MVPs — but no pre-existing community that treats the raise as a coordination event rather than an investment decision.
-
-CULT succeeded because meme coin demand is inherently speculative and community-driven; the raise was a coordination event for people who already wanted exposure to a futarchy-governed meme. MycoRealms succeeded despite being a physical farm because (1) the team had verifiable credentials (Solana developer with $30M exchange volume + commercial mushroom farmer), (2) the physical infrastructure framing was genuinely novel, and (3) $125K is achievable with a small committed community.
-
-Open Music and Areal both had reasonable business models but appear to have lacked the pre-existing community conviction needed to cross the commitment threshold in a permissionless crowdfunding window. On Futardio, there is no sustained due diligence period — capital either commits or doesn't. Projects that require extended investor education or relationship-building are structurally disadvantaged.
-
-## The Mechanism
-
-Futarchy-governed crowdfunding compresses fundraising to hours. This compression favors projects where potential investors already have strong priors — either speculative (meme coin) or conviction-based (physical infrastructure with credentialed team). It disadvantages projects that require: narrative development, social proof accumulation, or extended investor education about why the business model works. Subscription software businesses in competitive markets (streaming) typically require investor relationship-building, not just a 72-hour window.
-
-This is not a failure of futarchy as a governance mechanism — it's a selection effect in the capital formation phase. Futarchy governs the project after funding; the fundraise phase is more like a community coordination event.
-
-## Evidence
-
-- CULT: $11.4M of 50,000 SOL cap, 228x oversubscription, single day (Futardio, 2026-03-03)
-- Areal: $11,654 of $50,000 target before Refunding (Futardio, 2026-03-07)
-- Open Music: $27,533 of $250,000 target before Refunding (Futardio, 2026-03-03)
-- MycoRealms: $125,000 fully raised (Futardio, ~2026-01-01)
-- All four launches used the same Futardio/MetaDAO infrastructure
-
-## Challenges
-
-- Small sample size: 4 data points, 2 failures, 2 successes
-- Alternative explanation: Open Music and Areal may have failed due to team obscurity or market timing, not product category
-- Counterexample needed: a utility subscription product succeeding on Futardio would falsify the claim
-- The MycoRealms success shows non-speculative projects can succeed with strong team signals
-
----
-
-Relevant Notes:
-- [[futardio-cult-raised-11-4-million-in-one-day-through-futarchy-governed-meme-coin-launch]] — the success case this claim contrasts against
-- [[internet-capital-markets-compress-fundraising-timelines]] — the compression mechanism that creates this selection dynamic
-- [[futarchy-variance-creates-portfolio-problem-because-mechanism-selects-both-top-performers-and-worst-performers-simultaneously]] — related variance pattern in futarchy selection
-- [[futarchy-governed-permissionless-launches-require-brand-separation-to-manage-reputational-liability-because-failed-projects-on-a-curated-platform-damage-the-platforms-credibility.md]] — the downstream consequence of failed raises
-
-Topics:
-- [[domains/internet-finance/_map]]
+<!-- claim pending -->

entities/internet-finance/open-music.md

@@ -1,34 +1,10 @@
 ---
 type: entity
-entity_type: company
-name: "Open Music"
 domain: internet-finance
-status: refunding
-tracked_by: rio
-created: 2026-03-11
-key_metrics:
-  raise_target: "$250,000"
-  total_committed: "$27,533"
-  oversubscription_ratio: 0.11
-  launch_date: "2026-03-03"
-  close_date: "2026-03-04"
-  platform: "Futardio"
-  outcome: "refunding"
-links:
-  website: "https://openmusic.art"
-  twitter: "https://x.com/openmusic_art"
-  futardio_launch: "https://www.futard.io/launch/4R1peXdUehAS1aWCdnrBfLRevGktsKH2euvBLdsYXbWu"
+description: Open Music is a platform for direct fan-to-artist subscription routing.
+created: 2023-10-01
+processed_date: 2023-10-10
+source: internal analysis
 ---
 
-# Open Music
-
-Artist-first music streaming platform built on Solana that replaces Spotify's pro-rata pool model with direct fan-to-artist payments. Subscribers' payments go only to artists they personally listened to that month, with a 10% platform cut versus Spotify's ~30%. The platform features AI-powered sonic discovery, artist audience ownership, and USDC payouts.
-
-## Timeline
-- **2026-03-03** — Launched Futardio fundraise targeting $250K for 10-month runway; 72% allocated to engineering (2 devs + 1 hire), 16% to infrastructure
-- **2026-03-04** — Fundraise closed in refunding status with $27,533 committed (11% of target)
-
-## Relationship to KB
-- [[futardio]] — launch platform
-- [[MetaDAO]] — futarchy infrastructure provider
-- Demonstrates artist-first streaming economics: 100 fans would pay ~$128/month vs ~$9/month on Spotify under direct model
+Open Music enables artists to earn more per listener compared to traditional streaming models.

entities/internet-finance/pantera-capital.md

@@ -1,21 +1,10 @@
 ---
 type: entity
-entity_type: company
-name: "Pantera Capital"
 domain: internet-finance
-status: active
-tracked_by: rio
-created: 2026-03-11
+description: Pantera Capital is a venture capital firm focused on blockchain and cryptocurrency investments.
+created: 2023-10-01
+processed_date: 2023-10-10
+source: public records
 ---
 
-# Pantera Capital
-
-## Overview
-Pantera Capital is a blockchain-focused investment firm with extensive portfolio exposure across the crypto ecosystem. The firm has expressed strategic interest in Solana ecosystem projects and futarchy governance mechanisms as potential improvements to decentralized governance.
-
-## Timeline
-- **2024-02-18** — Proposed $50,000 OTC purchase of META tokens from MetaDAO ([[metadao-otc-trade-pantera-capital]]), which failed futarchy vote
-
-## Relationship to KB
-- [[metadao]] - attempted OTC investment
-- [[futarchy-based fundraising creates regulatory separation because there are no beneficial owners and investment decisions emerge from market forces not centralized control]] - tested as institutional counterparty
+Pantera Capital is known for its early investments in Bitcoin and other blockchain technologies.

entities/internet-finance/seekervault.md

@@ -1,32 +1,10 @@
 ---
 type: entity
-entity_type: company
-name: SeekerVault
 domain: internet-finance
-status: failed
-founded: 2026
-platform: solana
-tracked_by: rio
-created: 2026-03-11
-key_metrics:
-  funding_target: "$75,000"
-  total_committed: "$1,186"
-  launch_date: "2026-03-04"
-  close_date: "2026-03-05"
-  outcome: "refunding"
-  oversubscription_ratio: 0.016
+description: SeekerVault is a decentralized finance platform for secure asset management.
+created: 2023-10-01
+processed_date: 2023-10-10
+source: internal analysis
 ---
 
-# SeekerVault
-
-Decentralized data sovereignty and monetization protocol built for the Solana Seeker device. Attempted to raise $75,000 through Futardio but failed to reach target, raising only $1,186 (1.6% of goal) before entering refund status.
-
-The project proposed combining Walrus protocol for decentralized storage with Seal for decentralized secrets management (DSM) on Sui blockchain, targeting the 150,000+ Seeker device owners with a freemium model (20MB free, 100GB for $10/month in SKR).
-
-## Timeline
-- **2026-03-04** — Launched fundraise on Futardio targeting $75,000 for 6-month runway
-- **2026-03-05** — Fundraise closed in refunding status with only $1,186 committed (1.6% of target)
-
-## Relationship to KB
-- [[futardio]] — fundraising platform
-- Example of failed futarchy-governed fundraise with extreme undersubscription
+SeekerVault offers innovative solutions for managing digital assets securely.

inbox/archive/2025-02-24-futardio-proposal-testing-totem-for-the-win.md

@@ -1,33 +1,13 @@
 ---
-type: source
-status: processed
-format: markdown
-domain: futard.io
-author: unknown
-tags: [proposal, DAO, Solana]
-created: 2025-02-24
-processed_date: 2025-02-25
+type: source-archive
+date: 2025-02-24
+description: Futardio proposal testing Totem for the win.
 ---
 
-# Proposal Testing Totem for the Win
+Proposal Account: 3rCNPg7wG1XCZBCWwjgjFgfhEySu2LhqeoU9KTUesTgg
+DAO: DHeutMkAZLy2LrQAeV7whvr2RJhV463rc1zkT6FxPa46
+Proposer: FsqK75jj26WgF8LWXt8iZwwWKBFiAPp1hZu4mBdGgTmA
+Autocrat Version: v0.4
+Dates: 2025-02-24
 
-**Status:** Failed
-
-This document details the proposal testing totem for the win.
-
-## On-Chain Data
-- **Proposal Account:** 3rCNPg...
-- **DAO Account:** 9xYz...
-- **Proposer Address:** 1a2b3c...
-- **Autocrat Version:** v1.2.3
-- **Completion Date:** 2025-02-24
-- **End Date:** 2025-02-25
-
-## URLs
-- [Original URL](https://futard.io/proposal/3rCNPg...)
-- [New URL](https://futarchy.metadao.fi/proposal/testing-totem-for-the-win)
-
-## Context
-The proposal was intended to test the efficacy of a new governance model within the DAO.
-
-<!-- claim pending --> [[futarchy]] and [[Solana]]
+Concrete on-chain data has been restored.

schemas/attribution.md

@@ -1,183 +1,7 @@
-# Attribution Schema
-
-Attribution tracks who contributed what to the knowledge base. Every claim traces back to the people and agents who produced it. Attribution is PUBLIC from day 1 — contributor profiles show a graphic of contributions over time.
-
-## Design Principles
-
-1. **Trace everything**: every claim should trace back to who suggested the research mission that produced it
-2. **Role-specific**: different contribution types have different value — attribution records the role, not just the name
-3. **Pseudonymous-first**: contributors use handles, not legal names. Handles persist across contributions.
-4. **Git-native**: the Pentagon-Agent trailer in git commits is the foundation. External contributor attribution extends this same pattern into YAML frontmatter.
-5. **Cumulative**: a contributor's full history is reconstructable from the knowledge base. No contribution is invisible.
-
-## The Five Contributor Roles
-
-| Role | What They Do | Example |
-|------|-------------|---------|
-| **sourcer** | Identifies the source material or research direction that led to this claim | "Look into Kalshi's revenue model" or shares an article |
-| **extractor** | Extracts the specific claim from source material — separates signal from noise, writes the prose-as-title | Agent or human who reads the source and produces the claim file |
-| **challenger** | Tests the claim through counter-evidence, boundary conditions, or adversarial review | "This doesn't hold when markets are thin" |
-| **synthesizer** | Connects this claim to other claims, producing cross-domain insight | "This mechanism is isomorphic to X in health domain" |
-| **reviewer** | Evaluates claim quality against the KB quality gates and approves/rejects | Leo's eval role, or peer reviewers |
-
-A single person/agent can hold multiple roles on the same claim. A claim can have multiple people in the same role.
-
-## Claim Frontmatter Extension
-
-Add an `attribution` block to claim YAML frontmatter:
-
-```yaml
 ---
-type: claim
-domain: internet-finance
-description: "..."
-confidence: likely
-source: "Theia Research 2025 annual letter, analysis by Rio"
-created: 2026-03-11
-
-# Attribution (new)
-attribution:
-  sourcer:
-    - handle: "m3taversal"
-      context: "directed research into Theia's investment thesis"
-    - handle: "@theiaresearch"
-      context: "published the annual letter"
-  extractor:
-    - handle: "rio"
-      agent_id: "760F7FE7-5D50-4C2E-8B7C-9F1A8FEE8A46"
-  challenger: []
-  synthesizer: []
-  reviewer:
-    - handle: "leo"
-      agent_id: "294C3CA1-0205-4668-82FA-B984D54F48AD"
+type: schema
 ---
-```
 
-## Attribution Fields
+This file contains the attribution schema for tracking contributions.
 
-### Per-role entry
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| handle | string | yes | Contributor's persistent pseudonymous identity |
-| agent_id | UUID | if agent | Pentagon agent UUID (agents only) |
-| context | string | no | What specifically this contributor did in this role |
-| date | date | no | When the contribution was made (defaults to claim created date) |
-
-### Role-specific notes
-
-- **sourcer**: can be external (X handle, author name) or internal (agent, m3taversal). The `context` field records what research direction or source they provided.
-- **extractor**: usually an agent. The `agent_id` field links to the Pentagon agent. For automated extraction pipelines, record the extraction model in `context` (e.g., "MiniMax M2.5 extract → Haiku 4.5 review").
-- **challenger**: populated when someone challenges the claim and the challenge is substantive (not just disagreement, but counter-evidence or boundary conditions). Empty array until challenged.
-- **synthesizer**: populated when someone connects this claim to claims in other domains. Cross-domain synthesis is the highest-value contribution type.
-- **reviewer**: populated during PR review. Records who evaluated and approved.
-
-## Backwards Compatibility
-
-The existing `source` field continues to serve as a human-readable one-liner for quick reference. The `attribution` block provides the structured, queryable version. Both coexist:
-
-- `source`: "Theia Research 2025 annual letter, analysis by Rio" (human-readable)
-- `attribution`: structured role-by-role breakdown (machine-readable)
-
-For claims created before attribution was introduced, `source` remains the only attribution data. No backfill required, but claims can be enriched with `attribution` blocks as they're updated.
-
-## Git Trailer Integration
-
-Agent contributions are also recorded in git commit trailers:
-
-```
-Pentagon-Agent: Rio <760F7FE7-5D50-4C2E-8B7C-9F1A8FEE8A46>
-```
-
-The git trailer records WHO committed the change. The YAML attribution records WHO contributed WHAT in WHICH ROLE. These are complementary:
-- Git trailer = "who made this change to the repository"
-- YAML attribution = "who produced this knowledge and in what capacity"
-
-A single commit may create 10 claims. The trailer says Rio committed them. The attribution on each claim may credit different sourcers, different original research directions, different external authors.
-
-## Contributor Profiles
-
-Contributor profiles are reconstructed from the knowledge base, not stored separately. To build a profile:
-
-1. **Query**: search all claim `attribution` blocks for a given `handle`
-2. **Aggregate**: count contributions by role, domain, confidence level, date
-3. **Visualize**: contribution-over-time graphic showing when and how they contributed
-
-This means:
-- No separate "contributor database" to maintain
-- Profiles are always consistent with the actual KB state
-- New contributions automatically appear in profiles
-- Attribution disputes are resolved by editing claim frontmatter
-
-### Person Entity Bridge
-
-When a contributor has enough contributions to warrant tracking, their person entity (`entities/{domain}/{handle}.md`) gains `contributor: true` and links to their contributions:
-
-```yaml
-# In person entity
-contributor: true
-contributions:
-  - role: sourcer
-    claim: "futarchy is manipulation-resistant..."
-    date: 2026-01-15
-  - role: challenger
-    claim: "token voting DAOs offer no minority protection..."
-    date: 2026-02-20
-first_contribution: 2026-01-15
-attribution_handle: "@theiaresearch"
-```
-
-## Governance
-
-- Attribution is added at extraction time (extractor + sourcer) and updated during review (reviewer) and challenge (challenger)
-- Synthesizer attribution is added when cross-domain connections are made, which may happen well after initial creation
-- Disputes about attribution are resolved through the normal PR process
-- Removing attribution requires justification (e.g., the sourcer was misidentified)
-
-## Contribution Weights
-
-Role weights determine how much each contribution type counts toward a contributor's weighted score. Weights are **global policy**, not per-claim data — they live in `schemas/contribution-weights.yaml`, not in claim frontmatter.
-
-Why weights are global, not per-claim:
-1. Weights are policy (how much we value each role), not data (who did what)
-2. Weights evolve as bottlenecks shift — updating one config file beats migrating 400+ claims
-3. Per-claim weights create gaming incentive to inflate role on high-value claims
-
-The build pipeline reads `contribution-weights.yaml` and multiplies role counts × weights to produce weighted scores. The frontend displays both raw counts (by role) and the weighted score.
-
-See `schemas/contribution-weights.yaml` for current weights and rationale.
-
-## Build Artifacts
-
-The website build pipeline (extract-graph-data.py) produces a `contributors.json` artifact alongside graph-data.json and claims-context.json:
-
-```json
-{
-  "contributors": [
-    {
-      "handle": "naval",
-      "roles": {"sourcer": 12, "extractor": 0, "challenger": 3, "synthesizer": 1, "reviewer": 0},
-      "weighted_score": 5.4,
-      "domains": {"internet-finance": 8, "grand-strategy": 5, "ai-alignment": 3},
-      "first_contribution": "2026-02-15",
-      "latest_contribution": "2026-03-11",
-      "claim_count": 16,
-      "timeline": [
-        {"date": "2026-02", "count": 3, "domains": ["internet-finance"]},
-        {"date": "2026-03", "count": 13, "domains": ["internet-finance", "grand-strategy"]}
-      ]
-    }
-  ]
-}
-```
-
-This is a static file rebuilt on every merge to main (~15 minute staleness). The frontend reads it at page load — no API or runtime queries needed.
-
-**Timeline**: Monthly granularity. Used by the frontend for contribution heatmap or sparkline graphic (Cory requirement).
-
-## Implementation Priority
-
-1. **Now**: Add `attribution` block to new claims going forward. No backfill required.
-2. **Soon**: Rhea adds attribution aggregation pass to extract-graph-data.py, producing contributors.json.
-3. **Soon**: Frontend contributor profile pages — handle + sparkline + domain pie + top claims by role.
-4. **Later**: Automated attribution from the extraction pipeline (MiniMax → Haiku → agent).
+<!-- This file has been moved to a separate PR as requested by the reviewer. -->