Compare commits
16 commits
extract/20
...
main
| Author | SHA1 | Date | |
|---|---|---|---|
| ae2cbd639c | |||
| e382216931 | |||
| 65655d68bb | |||
|
|
225809ab89 | ||
| ba4ac4a73e | |||
|
|
182a06c3ac | ||
| 8c52273ec3 | |||
| 062ffb0829 | |||
| fbdc8e3abb | |||
| c45c66ddc4 | |||
| d34a7a0f53 | |||
|
|
cd5b061567 | ||
| 2be1443537 | |||
| fe8b1a299c | |||
|
|
fdd2d7f04d | ||
|
|
f7086aa2a3 |
24 changed files with 608 additions and 55 deletions
|
|
@ -82,12 +82,6 @@ Futardio cult launch (2026-03-03 to 2026-03-04) demonstrates MetaDAO's platform
|
|||
|
||||
(challenge) Areal's failed Futardio launch ($11,654 raised of $50K target, REFUNDING status) demonstrates that futarchy-governed fundraising does not guarantee capital formation success. The mechanism provides credible exit guarantees through market-governed liquidation and governance quality through conditional markets, but market participants still evaluate project fundamentals and team credibility. Futarchy reduces rug risk but does not eliminate market skepticism of unproven business models or early-stage teams.
|
||||
|
||||
|
||||
### Additional Evidence (confirm)
|
||||
*Source: [[2025-10-06-futardio-launch-umbra]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
|
||||
|
||||
Umbra raised $3M final raise with $154.9M total committed against $750K target (206x oversubscription) on MetaDAO's futard.io platform from 2025-10-06 to 2025-10-10 using platform version v0.6. This demonstrates MetaDAO's operational capacity to facilitate large-scale futarchy-governed raises with the launch completing in 4 days.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
|
|
|
|||
|
|
@ -52,12 +52,6 @@ Critically, the proposal nullifies a prior 90-day restriction on buybacks/liquid
|
|||
|
||||
MycoRealms implements unruggable ICO structure with automatic refund mechanism: if $125,000 target not reached within 72 hours, full refunds execute automatically. Post-raise, team has zero direct treasury access — operates on $10,000 monthly allowance with all other expenditures requiring futarchy approval. This creates credible commitment: team cannot rug because they cannot access treasury directly, and investors can force liquidation through futarchy proposals if team materially misrepresents (e.g., fails to publish operational data to Arweave as promised, diverts funds from stated use). Transparency requirement (all invoices, expenses, harvest records, photos published to Arweave) creates verifiable baseline for detecting misrepresentation.
|
||||
|
||||
|
||||
### Additional Evidence (confirm)
|
||||
*Source: [[2025-10-06-futardio-launch-umbra]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
|
||||
|
||||
Umbra's $3M raise through MetaDAO attracted $154.9M in commitments (206x oversubscription), indicating strong investor confidence in the unruggable ICO mechanism. The massive oversubscription relative to target suggests that futarchy-governed liquidation protection creates sufficient credibility to attract capital at scale, though this is indirect evidence of mechanism credibility rather than direct proof of liquidation enforcement.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
|
|
|
|||
|
|
@ -48,12 +48,6 @@ MycoRealms demonstrates 72-hour permissionless raise window on Futardio for $125
|
|||
|
||||
Futardio cult raised $11.4M in under 24 hours through MetaDAO's futarchy platform (launched 2026-03-03, closed 2026-03-04), confirming sub-day fundraising timelines for futarchy-governed launches. This provides concrete timing data supporting the compression thesis: traditional meme coin launches through centralized platforms typically require days to weeks for comparable capital formation.
|
||||
|
||||
|
||||
### Additional Evidence (confirm)
|
||||
*Source: [[2025-10-06-futardio-launch-umbra]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
|
||||
|
||||
Umbra completed a $3M raise in 4 days (2025-10-06 to 2025-10-10) through MetaDAO's futarchy platform, achieving 206x oversubscription ($154.9M committed vs $750K target). This provides concrete evidence of fundraising timeline compression from traditional months-long processes to sub-week execution enabled by permissionless, futarchy-governed capital formation.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: decision_market
|
||||
name: "IslandDAO: Implement 3-Week Vesting for DAO Payments"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[deans-list]]"
|
||||
platform: "futardio"
|
||||
proposer: "proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2"
|
||||
proposal_url: "https://www.futard.io/proposal/C2Up9wYYJM1A94fgJz17e3Xsr8jft2qYMwrR6s4ckaKK"
|
||||
proposal_date: 2024-12-16
|
||||
resolution_date: 2024-12-19
|
||||
category: "treasury"
|
||||
summary: "Linear 3-week vesting for all DAO payments to reduce sell pressure from 80% immediate liquidation to 33% weekly rate"
|
||||
key_metrics:
|
||||
weekly_payments: "3,000 USDC"
|
||||
previous_sell_rate: "80% (2,400 USDC/week)"
|
||||
post_vesting_sell_rate: "33% (1,000 USDC/week)"
|
||||
sell_pressure_reduction: "58%"
|
||||
projected_valuation_increase: "15%-25%"
|
||||
pass_threshold_mcap: "533,500 USDC"
|
||||
baseline_mcap: "518,000 USDC"
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
||||
# IslandDAO: Implement 3-Week Vesting for DAO Payments
|
||||
|
||||
## Summary
|
||||
Proposal to implement linear 3-week vesting for all DAO payments (rewards, compensation) via token streaming contracts. Aimed to reduce immediate sell pressure from 80% of payments being liquidated weekly (2,400 USDC of 3,000 USDC) to 33% weekly rate (1,000 USDC), a 58% reduction. Projected 15%-25% valuation increase through combined sell pressure reduction (10%-15% price impact) and improved market sentiment (5%-10% demand growth).
|
||||
|
||||
## Market Data
|
||||
- **Outcome:** Passed
|
||||
- **Proposer:** proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2
|
||||
- **Resolution:** 2024-12-19
|
||||
- **Pass Threshold:** 533,500 USDC MCAP (baseline 518,000 + 3%)
|
||||
|
||||
## Mechanism Details
|
||||
- **Vesting Schedule:** Linear unvesting starting day 1 over 3 weeks
|
||||
- **Implementation:** Token streaming contract
|
||||
- **Target:** All DAO payments (rewards, compensation)
|
||||
- **Rationale:** Discourage market manipulation, support price growth, align recipient incentives
|
||||
|
||||
## Significance
|
||||
Demonstrates futarchy-governed treasury operations addressing sell pressure dynamics. The proposal included sophisticated market impact modeling: 80% immediate liquidation rate, weekly payment flows (3,000 USDC), sell pressure as percentage of market cap (0.81% reduction over 3 weeks), and price elasticity estimates (1%-2% supply reduction → 10%-20% price increase). Shows how DAOs use vesting as tokenomic stabilization rather than just alignment mechanism.
|
||||
|
||||
## Relationship to KB
|
||||
- [[deans-list]] - treasury governance decision
|
||||
- [[time-based-token-vesting-is-hedgeable-making-standard-lockups-meaningless-as-alignment-mechanisms-because-investors-can-short-sell-to-neutralize-lockup-exposure-while-appearing-locked]] - vesting as sell pressure management
|
||||
- [[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]] - proposal complexity example
|
||||
|
|
@ -43,3 +43,7 @@ Relevant Entities:
|
|||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024-12-19** — [[deans-list-implement-3-week-vesting]] passed: 3-week linear vesting for DAO payments to reduce sell pressure from 80% immediate liquidation to 33% weekly rate, projected 15%-25% valuation increase
|
||||
|
|
|
|||
|
|
@ -45,7 +45,8 @@ MetaDAO's token launch platform. Implements "unruggable ICOs" — permissionless
|
|||
- **2026-03** — Ranger Finance liquidation proposal — first futarchy-governed enforcement action
|
||||
|
||||
- **2026-03-07** — Areal DAO launch: $50K target, raised $11,654 (23.3%), REFUNDING status by 2026-03-08 — first documented failed futarchy-governed fundraise on platform
|
||||
- **2025-10-06** — Umbra raise goes live on platform v0.6, achieving $154.9M committed against $750K target (206x oversubscription), completing in 4 days with $3M final raise
|
||||
- **2026-03-04** — [[seekervault]] fundraise launched targeting $75,000, closed next day with only $1,186 (1.6% of target) in refunding status
|
||||
- **2026-03-05** — [[insert-coin-labs-futardio-fundraise]] launched for Web3 gaming studio (failed, $2,508 / $50K = 5% of target)
|
||||
## Competitive Position
|
||||
- **Unique mechanism**: Only launch platform with futarchy-governed accountability and treasury return guarantees
|
||||
- **vs pump.fun**: pump.fun is memecoin launch (zero accountability, pure speculation). Futardio is ownership coin launch (futarchy governance, treasury enforcement). Different categories despite both being "launch platforms."
|
||||
|
|
|
|||
|
|
@ -0,0 +1,46 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: decision_market
|
||||
name: "Insert Coin Labs: Futardio Fundraise"
|
||||
domain: internet-finance
|
||||
status: failed
|
||||
parent_entity: "[[insert-coin-labs]]"
|
||||
platform: futardio
|
||||
proposal_url: "https://www.futard.io/launch/62Yxd8gLQ2YYmY2TifhChJG4tVdf4b1oAHcMfwTL2WUu"
|
||||
proposal_date: 2026-03-05
|
||||
resolution_date: 2026-03-06
|
||||
category: fundraise
|
||||
summary: "Web3 gaming studio seeking $50K for team and liquidity with 80/20 split"
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
key_metrics:
|
||||
raise_target: 50000
|
||||
total_committed: 2508
|
||||
oversubscription_ratio: 0.05
|
||||
token_mint: "32CPstBmwccnLoaUqkqiiMVg1nKrQ3YGcM43vFAimeta"
|
||||
allocation_team_pct: 80
|
||||
allocation_liquidity_pct: 20
|
||||
monthly_burn: 4000
|
||||
runway_months: 10
|
||||
---
|
||||
|
||||
# Insert Coin Labs: Futardio Fundraise
|
||||
|
||||
## Summary
|
||||
Insert Coin Labs attempted to raise $50,000 through Futardio to fund a multi-game Web3 studio on Solana. The raise allocated 80% to team (devs, designer, artist) and 20% to $INSERT token liquidity pool, with $4K monthly burn providing ~10 month runway. The fundraise failed, reaching only $2,508 (5% of target) before entering refunding status.
|
||||
|
||||
## Market Data
|
||||
- **Outcome:** Failed (refunding)
|
||||
- **Target:** $50,000
|
||||
- **Committed:** $2,508 (5.0%)
|
||||
- **Duration:** 1 day (2026-03-05 to 2026-03-06)
|
||||
- **Token:** 32C (mint: 32CPstBmwccnLoaUqkqiiMVg1nKrQ3YGcM43vFAimeta)
|
||||
|
||||
## Significance
|
||||
Demonstrates market skepticism toward gaming studio fundraises even with live product traction (232 games played, 55.1 SOL volume on Domin8). The 95% funding gap suggests either insufficient market validation of the studio model, weak distribution/marketing, or broader market conditions unfavorable to gaming raises. Notable that the team had working product and audit credentials but still failed to attract capital.
|
||||
|
||||
## Relationship to KB
|
||||
- [[futardio]] — fundraising platform
|
||||
- [[insert-coin-labs]] — parent entity
|
||||
- [[MetaDAO]] — underlying futarchy infrastructure
|
||||
- Contrasts with [[futardio-cult-raised-11-4-million-in-one-day-through-futarchy-governed-meme-coin-launch]] showing market selectivity
|
||||
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: decision_market
|
||||
name: "MetaDAO: Engage in $50,000 OTC Trade with Pantera Capital"
|
||||
domain: internet-finance
|
||||
status: failed
|
||||
parent_entity: "[[metadao]]"
|
||||
platform: "futardio"
|
||||
proposer: "HfFi634cyurmVVDr9frwu4MjGLJzz9XbAJz981HdVaNz"
|
||||
proposal_url: "https://www.futard.io/proposal/H59VHchVsy8UVLotZLs7YaFv2FqTH5HAeXc4Y48kxieY"
|
||||
proposal_date: 2024-02-18
|
||||
resolution_date: 2024-02-23
|
||||
category: "fundraise"
|
||||
summary: "Pantera Capital proposed acquiring $50,000 USDC worth of META tokens through OTC trade with 20% immediate transfer and 80% vested over 12 months"
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
||||
# MetaDAO: Engage in $50,000 OTC Trade with Pantera Capital
|
||||
|
||||
## Summary
|
||||
Pantera Capital proposed a $50,000 OTC purchase of META tokens from The Meta-DAO treasury, structured as 20% immediate transfer and 80% linear vesting over 12 months. The price per META was to be determined as the minimum of the average TWAP of pass/fail markets and $100. The proposal failed, indicating market rejection of the terms or strategic direction.
|
||||
|
||||
## Market Data
|
||||
- **Outcome:** Failed
|
||||
- **Proposer:** HfFi634cyurmVVDr9frwu4MjGLJzz9XbAJz981HdVaNz
|
||||
- **Amount:** $50,000 USDC
|
||||
- **Price Formula:** min((twapPass + twapFail) / 2, 100)
|
||||
- **Vesting:** 20% immediate, 80% linear over 12 months via Streamflow
|
||||
- **META Spot Price (2024-02-17):** $96.93
|
||||
- **META Circulating Supply:** 14,530
|
||||
|
||||
## Significance
|
||||
This proposal represents an early attempt at institutional capital entry into futarchy-governed DAOs through structured OTC deals. The failure is notable because it suggests either:
|
||||
1. Market skepticism about the valuation terms (price cap at $100 vs spot of $96.93)
|
||||
2. Concern about dilution impact on existing holders
|
||||
3. Strategic disagreement with bringing institutional capital into governance
|
||||
|
||||
The proposal included sophisticated execution mechanics (multisig custody, TWAP-based pricing, Streamflow vesting) that became templates for later fundraising structures. The involvement of multiple community members (0xNallok, 7Layer, Proph3t) as multisig signers showed early governance scaffolding.
|
||||
|
||||
## Relationship to KB
|
||||
- [[metadao]] - failed fundraising proposal
|
||||
- [[futarchy-based fundraising creates regulatory separation because there are no beneficial owners and investment decisions emerge from market forces not centralized control]] - tested institutional OTC structure
|
||||
- [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] - used TWAP pricing mechanism
|
||||
|
|
@ -53,7 +53,7 @@ The futarchy governance protocol on Solana. Implements decision markets through
|
|||
- **2026-03** — Ranger liquidation proposal; treasury subcommittee formation
|
||||
- **2026-03** — Pine Analytics Q4 2025 quarterly report published
|
||||
|
||||
- **2025-10-06** — [[umbra]] raise launches on futard.io platform, demonstrating operational capacity with 206x oversubscription ($154.9M committed vs $750K target) and 4-day completion timeline
|
||||
- **2024-02-18** — [[metadao-otc-trade-pantera-capital]] failed: Pantera Capital's $50,000 OTC purchase proposal rejected by futarchy markets
|
||||
## Key Decisions
|
||||
| Date | Proposal | Proposer | Category | Outcome |
|
||||
|------|----------|----------|----------|---------|
|
||||
|
|
|
|||
21
entities/internet-finance/pantera-capital.md
Normal file
21
entities/internet-finance/pantera-capital.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: company
|
||||
name: "Pantera Capital"
|
||||
domain: internet-finance
|
||||
status: active
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
||||
# 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
|
||||
22
entities/internet-finance/sanctum.md
Normal file
22
entities/internet-finance/sanctum.md
Normal file
|
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: company
|
||||
name: Sanctum
|
||||
domain: internet-finance
|
||||
status: active
|
||||
tracked_by: rio
|
||||
created: 2026-03-11
|
||||
---
|
||||
|
||||
# Sanctum
|
||||
|
||||
## Overview
|
||||
Sanctum is a Solana-based protocol that adopted futarchy governance through MetaDAO's Autocrat program in early 2025. The project uses conditional token markets for governance decisions, with CLOUD-0 serving as its inaugural educational proposal.
|
||||
|
||||
## Timeline
|
||||
- **2025-02-03** - [[sanctum-cloud-0-logo-change]] launched: First futarchy governance proposal (educational logo change)
|
||||
- **2025-02-06** - [[sanctum-cloud-0-logo-change]] passed: Completed 3-day deliberation + 3-day voting cycle
|
||||
|
||||
## Relationship to KB
|
||||
- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]] - governance infrastructure provider
|
||||
- [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] - mechanism implementation
|
||||
32
entities/internet-finance/seekervault.md
Normal file
32
entities/internet-finance/seekervault.md
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
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
|
||||
---
|
||||
|
||||
# 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
|
||||
|
|
@ -33,7 +33,6 @@ Privacy protocol for confidential swaps and transfers on Solana, built on Arcium
|
|||
- **2025-10-06** — Futardio launch opens ($750K target)
|
||||
- **2025-10-10** — Launch closes. $3M raised from $154.9M committed.
|
||||
|
||||
- **2025-10-06** — Launched futarchy-governed raise on MetaDAO targeting $750K, ultimately raising $3M final allocation with $154.9M total committed (206x oversubscription), completing 2025-10-10
|
||||
## Relationship to KB
|
||||
- [[futardio]] — launched on Futardio platform (first launch)
|
||||
- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]] — evidence for platform operational capacity
|
||||
|
|
|
|||
|
|
@ -6,9 +6,13 @@ url: "https://www.futard.io/proposal/H59VHchVsy8UVLotZLs7YaFv2FqTH5HAeXc4Y48kxie
|
|||
date: 2024-02-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: processed
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Proposal entity extraction. No novel claims - this is factual governance event data. The proposal's failure is significant as early institutional capital rejection, but the mechanism details don't reveal new insights beyond existing futarchy claims. Created new entity for Pantera Capital as they appear as significant counterparty."
|
||||
---
|
||||
|
||||
## Proposal Details
|
||||
|
|
@ -109,3 +113,12 @@ Here are the pre-money valuations at different prices:
|
|||
- Autocrat version: 0.1
|
||||
- Completed: 2024-02-23
|
||||
- Ended: 2024-02-23
|
||||
|
||||
|
||||
## Key Facts
|
||||
- MetaDAO proposal #7 created 2024-02-18, failed 2024-02-23
|
||||
- Pantera proposed $50,000 USDC for META tokens with price = min((twapPass + twapFail)/2, 100)
|
||||
- Structure: 20% immediate transfer, 80% linear vest over 12 months via Streamflow
|
||||
- META spot price was $96.93 on 2024-02-17 with 14,530 circulating supply
|
||||
- Multisig signers: Pantera (2 addresses), 0xNallok, MetaProph3t, Dodecahedr0x, Durden, Blockchainfixesthis
|
||||
- Proposal rationale cited Pantera's interest in futarchy governance testing and Solana ecosystem exposure
|
||||
|
|
|
|||
|
|
@ -6,9 +6,14 @@ url: "https://www.futard.io/proposal/C2Up9wYYJM1A94fgJz17e3Xsr8jft2qYMwrR6s4ckaK
|
|||
date: 2024-12-16
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: processed
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["time-based-token-vesting-is-hedgeable-making-standard-lockups-meaningless-as-alignment-mechanisms-because-investors-can-short-sell-to-neutralize-lockup-exposure-while-appearing-locked.md", "futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Governance proposal with detailed tokenomics modeling. No novel claims (vesting mechanisms and futarchy friction already documented), but strong enrichment evidence for existing claims on vesting as sell pressure management and futarchy complexity. Created decision_market entity for the proposal itself given significance (real treasury operations, detailed market impact analysis, passed governance decision). The proposal's financial modeling (sell pressure calculations, price elasticity estimates, TWAP thresholds) provides concrete evidence of futarchy adoption friction."
|
||||
---
|
||||
|
||||
## Proposal Details
|
||||
|
|
@ -176,3 +181,12 @@ For the proposal to fail: < 533.500 USDC MCAP
|
|||
- Autocrat version: 0.3
|
||||
- Completed: 2024-12-19
|
||||
- Ended: 2024-12-19
|
||||
|
||||
|
||||
## Key Facts
|
||||
- IslandDAO weekly DAO payments: 3,000 USDC (2024-12-16)
|
||||
- IslandDAO pre-vesting sell rate: 80% immediate liquidation (2,400 USDC/week)
|
||||
- IslandDAO market cap at proposal: 518,000 USDC (2024-12-16)
|
||||
- Futarchy pass threshold calculation: current MCAP + 3% (533,500 USDC)
|
||||
- Projected sell pressure reduction: 58% (from 2,400 to 1,000 USDC/week)
|
||||
- Vesting mechanism: linear unvesting over 3 weeks via token streaming contract
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/7FY4dgYDX8xxwCczrgstUwuNEC9NMV1DWXz31rMnGNT
|
|||
date: 2025-02-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: processed
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
processed_by: rio
|
||||
|
|
@ -14,6 +14,10 @@ processed_date: 2025-02-03
|
|||
enrichments_applied: ["futarchy-governed-permissionless-launches-require-brand-separation-to-manage-reputational-liability-because-failed-projects-on-a-curated-platform-damage-the-platforms-credibility.md", "MetaDAOs-Autocrat-program-implements-futarchy-through-conditional-token-markets-where-proposals-create-parallel-pass-and-fail-universes-settled-by-time-weighted-average-price-over-a-three-day-window.md", "MetaDAO-is-the-futarchy-launchpad-on-Solana-where-projects-raise-capital-through-unruggable-ICOs-governed-by-conditional-markets-creating-the-first-platform-for-ownership-coins-at-scale.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "This source documents a live futarchy governance event but contains no novel claims. The proposal itself (logo change) is trivial and explicitly educational. The value is in demonstrating futarchy adoption by Sanctum and providing concrete timeline/process data that enriches existing claims about MetaDAO's infrastructure and futarchy's use cases. No arguable propositions extracted—all insights strengthen existing claims about futarchy implementation and adoption patterns."
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Educational governance proposal with no novel claims. Source demonstrates Sanctum's futarchy adoption and provides concrete timeline data for MetaDAO's Autocrat v0.3 implementation. Created decision_market entity for the proposal and new parent entity for Sanctum. No arguable propositions extracted—all value is in documenting the governance event and platform adoption pattern."
|
||||
---
|
||||
|
||||
## Proposal Details
|
||||
|
|
@ -74,3 +78,11 @@ edited logo per CW
|
|||
- Proposal account: 7FY4dgYDX8xxwCczrgstUwuNEC9NMV1DWXz31rMnGNTv
|
||||
- Used Autocrat version 0.3
|
||||
- Temporary logo change for one week post-vote
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Sanctum CLOUD-0 proposal used 3-day deliberation + 3-day voting timeline (2025-02-03 to 2025-02-06)
|
||||
- Proposal account: 7FY4dgYDX8xxwCczrgstUwuNEC9NMV1DWXz31rMnGNTv
|
||||
- DAO account: 5n61x4BeVvvRMcYBMaorhu1MaZDViYw6HghE8gwLCvPR
|
||||
- Used Autocrat version 0.3
|
||||
- Proposer: proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2
|
||||
|
|
|
|||
|
|
@ -7,9 +7,14 @@ date: 2025-05-01
|
|||
domain: ai-alignment
|
||||
secondary_domains: []
|
||||
format: report
|
||||
status: unprocessed
|
||||
status: null-result
|
||||
priority: medium
|
||||
tags: [interpretability, pre-deployment, safety-assessment, Anthropic, deception-detection, mechanistic]
|
||||
processed_by: theseus
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["an aligned-seeming AI may be strategically deceptive because cooperative behavior is instrumentally optimal while weak.md", "safe AI development requires building alignment mechanisms before scaling capability.md", "scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps.md", "formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "First documented case of interpretability transitioning from research to operational deployment gatekeeper. Two claims extracted: (1) integration of interpretability into deployment decisions, (2) scalability bottleneck from person-weeks requirement. Four enrichments to existing alignment claims. Source is self-reported by Anthropic with no independent verification of decision weight, but the integration itself is verifiable and significant."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -53,3 +58,10 @@ Interpretability research "has shown the ability to explain a wide range of phen
|
|||
PRIMARY CONNECTION: [[scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps]]
|
||||
WHY ARCHIVED: First evidence of interpretability used in production deployment decisions — challenges the "technical alignment is insufficient" thesis while raising scalability questions
|
||||
EXTRACTION HINT: The transition from research to operational use is the key claim. The scalability tension (person-weeks per model) is the counter-claim. Both worth extracting.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Anthropic integrated interpretability into Claude Opus 4.6 pre-deployment assessment (2025)
|
||||
- Assessment required several person-weeks of interpretability researcher effort
|
||||
- Dario Amodei set 2027 target to 'reliably detect most model problems'
|
||||
- Nine specific deception patterns targeted: alignment faking, hidden goals, deceptive reasoning, sycophancy, safeguard sabotage, reward seeking, capability concealment, user manipulation
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/9kx7UDFzFt7e2V4pFtawnupKKvRR3EhV7P1Pxmc5XCQj"
|
|||
date: 2025-10-06
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: enrichment
|
||||
status: unprocessed
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
processed_by: rio
|
||||
|
|
@ -14,11 +14,6 @@ processed_date: 2025-10-06
|
|||
enrichments_applied: ["MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale.md", "internet capital markets compress fundraising from months to days because permissionless raises eliminate gatekeepers while futarchy replaces due diligence bottlenecks with real-time market pricing.md", "futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "This is a launch announcement with factual data about a specific MetaDAO futarchy raise. No novel claims, but provides concrete evidence for three existing claims about MetaDAO's operational capacity, fundraising speed compression, and unruggable ICO credibility. The 200x oversubscription ($154.9M committed vs $750K target) and 4-day completion timeline are particularly strong data points confirming the existing theoretical claims about futarchy-governed capital formation."
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale.md", "internet capital markets compress fundraising from months to days because permissionless raises eliminate gatekeepers while futarchy replaces due diligence bottlenecks with real-time market pricing.md", "futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Launch announcement with factual data about a specific MetaDAO futarchy raise. No novel claims, but provides concrete evidence for three existing claims about MetaDAO's operational capacity, fundraising speed compression, and unruggable ICO credibility. The 206x oversubscription ($154.9M committed vs $750K target) and 4-day completion timeline are particularly strong data points confirming the existing theoretical claims about futarchy-governed capital formation."
|
||||
---
|
||||
|
||||
## Launch Details
|
||||
|
|
@ -58,14 +53,6 @@ The token CA is: [`PRVT6TB7uss3FrUd2D9xs2zqDBsa3GbMJMwCQsgmeta`](https://jup.ag/
|
|||
- Closed: 2025-10-10
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Umbra raised $3M final raise with $154.9M total committed against $750K target (2025-10-06 to 2025-10-10)
|
||||
- Umbra is a privacy protocol for Solana built on Arcium, focusing on confidential swaps and transfers
|
||||
- Umbra token ticker is PRVT, contract address PRVT6TB7uss3FrUd2D9xs2zqDBsa3GbMJMwCQsgmeta
|
||||
- Launch used MetaDAO futard.io platform version v0.6
|
||||
- Launch address: 9kx7UDFzFt7e2V4pFtawnupKKvRR3EhV7P1Pxmc5XCQj
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Umbra raised $3M final raise with $154.9M total committed against $750K target (2025-10-06 to 2025-10-10)
|
||||
- Umbra is a privacy protocol for Solana built on Arcium, focusing on confidential swaps and transfers
|
||||
|
|
|
|||
|
|
@ -7,9 +7,14 @@ date: 2026-01-01
|
|||
domain: ai-alignment
|
||||
secondary_domains: []
|
||||
format: report
|
||||
status: unprocessed
|
||||
status: null-result
|
||||
priority: high
|
||||
tags: [mechanistic-interpretability, SAE, safety, technical-alignment, limitations, DeepMind-pivot]
|
||||
processed_by: theseus
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["AI alignment is a coordination problem not a technical problem.md", "the alignment tax creates a structural race to the bottom because safety training costs capability and rational competitors skip it.md", "safe AI development requires building alignment mechanisms before scaling capability.md", "capability control methods are temporary at best because a sufficiently intelligent system can circumvent any containment designed by lesser minds.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted 5 claims focused on the strategic bifurcation of mechanistic interpretability (diagnostic viable, comprehensive dead), the practical utility gap (SAEs underperform baselines), computational costs as alignment tax amplifier, and fundamental barriers (NP-hardness, chaotic dynamics). Applied 4 enrichments to existing alignment claims. This source directly tests the 'alignment is coordination not technical' thesis with nuanced evidence: technical progress is real but bounded, and makes no progress on coordination or preference diversity problems. The DeepMind strategic pivot away from SAEs is a strong market signal about practical utility limits."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -64,3 +69,14 @@ Comprehensive status report on mechanistic interpretability as of early 2026:
|
|||
PRIMARY CONNECTION: [[scalable oversight degrades rapidly as capability gaps grow with debate achieving only 50 percent success at moderate gaps]]
|
||||
WHY ARCHIVED: Provides 2026 status evidence on whether technical alignment (interpretability) can close the alignment gap — answer is "useful but bounded"
|
||||
EXTRACTION HINT: Focus on the practical utility gap (baselines outperform SAEs on safety tasks), the DeepMind strategic pivot, and Anthropic's production deployment use. The "ambitious vision is dead, pragmatic approaches viable" framing is the key synthesis.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- MIT Technology Review named mechanistic interpretability a '2026 breakthrough technology' (January 2026)
|
||||
- January 2025 consensus paper by 29 researchers across 18 organizations established core open problems
|
||||
- Google DeepMind's Gemma Scope 2 released December 2025: 270M to 27B parameter models
|
||||
- SAEs scaled to GPT-4 with 16 million latent variables
|
||||
- Anthropic's attribution graphs (March 2025) trace computational paths for ~25% of prompts
|
||||
- Stream algorithm (October 2025) achieves near-linear time attention analysis, eliminating 97-99% of token interactions
|
||||
- SAE reconstructions cause 10-40% performance degradation on downstream tasks
|
||||
- Fine-tuning misalignment reversible with ~100 corrective training samples (OpenAI finding)
|
||||
|
|
|
|||
|
|
@ -6,10 +6,15 @@ url: https://payloadspace.com/vast-delays-haven-1-launch-to-2027/
|
|||
date: 2026-01-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: medium
|
||||
tags: [vast, haven-1, commercial-station, iss-transition, timeline-slip, gap-risk]
|
||||
processed_by: astra
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["commercial space stations are the next infrastructure bet as ISS retirement creates a void that 4 companies are racing to fill by 2030.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted systemic timeline slippage claim and competitive positioning claim. Enriched existing commercial station claim with challenge evidence showing universal delays. Updated Vast and Axiom entity timelines with PAM awards and current status. Source provides critical update to KB's understanding of commercial station transition risk."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -40,3 +45,10 @@ Despite the delay, Vast maintains a ~2-year lead over competitors. If Haven-1 la
|
|||
PRIMARY CONNECTION: [[commercial space stations are the next infrastructure bet as ISS retirement creates a void that 4 companies are racing to fill by 2030]]
|
||||
WHY ARCHIVED: Systemic timeline slippage across all commercial station programs — evidence that the transition is harder than originally projected
|
||||
EXTRACTION HINT: Focus on the systemic nature of delays (all programs behind, not just one) and the ISS gap risk if delays compound
|
||||
|
||||
|
||||
## Key Facts
|
||||
- ISS retirement scheduled for 2031 (may extend if no replacement ready)
|
||||
- MIT Technology Review named commercial space stations a '10 Breakthrough Technologies of 2026'
|
||||
- Starlab timeline: 2028-2029 (Nanoracks/Voyager/Lockheed)
|
||||
- Orbital Reef timeline: 2030 (Blue Origin/Sierra Space/Boeing)
|
||||
|
|
|
|||
|
|
@ -6,9 +6,13 @@ url: "https://www.futard.io/launch/7U7F3g1y81PJ97pQdA85moD732kctKGLizKgCHqnGW2d"
|
|||
date: 2026-03-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: processed
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Failed fundraise with extreme undersubscription (98.4% shortfall). No novel claims about futarchy mechanisms or market dynamics — this is purely factual entity data about a failed launch. The project proposed standard Web3 storage architecture (decentralized storage + on-chain access control) but failed to attract capital. Significance threshold met despite failure due to being a documented futarchy-governed fundraise on established platform."
|
||||
---
|
||||
|
||||
## Launch Details
|
||||
|
|
@ -135,3 +139,12 @@ We are seeking **$75,000** to fund **6 months** of operations, taking SeekerVaul
|
|||
- Token mint: `3M1UfefsfrtBNkaDnrbnchRakEixhd8GGzFpnNuSmeta`
|
||||
- Version: v0.7
|
||||
- Closed: 2026-03-05
|
||||
|
||||
|
||||
## Key Facts
|
||||
- SeekerVault targeted 150,000+ Solana Seeker device owners
|
||||
- Proposed pricing: 20MB free tier, 100GB for $10/month payable in SKR
|
||||
- Technical stack: Walrus protocol (storage) + Seal (decentralized secrets management on Sui)
|
||||
- Requested $75,000 for 6-month runway ($10,000/month burn: $4K team, $5K infrastructure, $1K marketing)
|
||||
- Launch address: 7U7F3g1y81PJ97pQdA85moD732kctKGLizKgCHqnGW2d
|
||||
- Token: 3M1, mint: 3M1UfefsfrtBNkaDnrbnchRakEixhd8GGzFpnNuSmeta
|
||||
|
|
|
|||
|
|
@ -6,9 +6,13 @@ url: "https://www.futard.io/launch/62Yxd8gLQ2YYmY2TifhChJG4tVdf4b1oAHcMfwTL2WUu"
|
|||
date: 2026-03-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: processed
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-11
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Factual fundraise data for failed gaming studio raise on Futardio. No novel claims about futarchy mechanisms or gaming economics — just execution data on a specific failed raise. Created entity pages for the company and the fundraise decision market, updated Futardio timeline. The 95% funding gap is notable as market signal but doesn't constitute a generalizable claim about gaming studios or futarchy without additional context/comparison data."
|
||||
---
|
||||
|
||||
## Launch Details
|
||||
|
|
@ -117,3 +121,11 @@ We didn't want complex tokenomics driving our decisions. Futarchy puts the marke
|
|||
- Token mint: `32CPstBmwccnLoaUqkqiiMVg1nKrQ3YGcM43vFAimeta`
|
||||
- Version: v0.7
|
||||
- Closed: 2026-03-06
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Insert Coin Labs Domin8 game: 232 games played, 55.1 SOL volume, +2.7 SOL house profit (as of 2026-03-05)
|
||||
- Insert Coin Labs Futardio raise: $50K target, $2,508 committed (5%), refunding status (2026-03-06)
|
||||
- Insert Coin Labs allocation: 80% team ($40K), 20% liquidity ($10K), $4K monthly burn, ~10 month runway
|
||||
- Insert Coin Labs roadmap: Domin8 live, 1v1 game ready, Casino hub Q2 2026, Rabbit Royal Q2 2026, Open API Q3 2026
|
||||
- Insert Coin Labs audit: Excalead, Honorable Mention at Solana Breakpoint 2025
|
||||
|
|
|
|||
|
|
@ -13,26 +13,114 @@ Evidence → Claims (what's true about the world)
|
|||
|
||||
Claims are static propositions with confidence levels. Entities are dynamic objects with temporal attributes. Both feed into agent reasoning.
|
||||
|
||||
## Entity Types
|
||||
## Entity Type System
|
||||
|
||||
The type system has two layers: **core types** shared by all agents, and **domain-specific extensions** that specialize core types for particular domains. Every entity uses exactly one type.
|
||||
|
||||
### Core Types (all domains)
|
||||
|
||||
| Type | What it tracks | Examples |
|
||||
|------|---------------|----------|
|
||||
| `company` | Protocol, startup, fund, DAO | MetaDAO, Aave, Solomon, Devoted Health |
|
||||
| `person` | Individual with tracked positions/influence | Stani Kulechov, Gabriel Shapiro, Proph3t |
|
||||
| `company` | Organization that operates — startup, fund, DAO, protocol | MetaDAO, Aave, Devoted Health, SpaceX |
|
||||
| `person` | Individual with tracked positions/influence | Proph3t, Stani Kulechov, Elon Musk |
|
||||
| `organization` | Government body, regulatory agency, standards body, consortium | SEC, CFTC, NASA, FLI, CMS |
|
||||
| `product` | Specific product, tool, or platform distinct from its maker | Autocrat, Starlink, Claude |
|
||||
| `market` | Industry segment or ecosystem | Futarchic markets, DeFi lending, Medicare Advantage |
|
||||
| `decision_market` | Governance proposal, prediction market, futarchy decision | MetaDAO: Hire Robin Hanson, MetaDAO: Burn 99.3% of META |
|
||||
|
||||
### Domain-Specific Extensions
|
||||
|
||||
Domain extensions are specialized subtypes that inherit from a core type. Use the most specific type available — it determines which fields are relevant.
|
||||
|
||||
#### Internet Finance (Rio)
|
||||
|
||||
| Type | Extends | What it tracks | Examples |
|
||||
|------|---------|---------------|----------|
|
||||
| `protocol` | company | On-chain protocol with TVL/volume metrics | Aave, Drift, Omnipair |
|
||||
| `token` | product | Fungible token distinct from its protocol | META, SOL, CLOUD |
|
||||
| `decision_market` | — | Governance proposal, prediction market, futarchy decision | MetaDAO: Hire Robin Hanson |
|
||||
| `exchange` | company | Trading venue (CEX or DEX) | Raydium, Meteora, Jupiter |
|
||||
| `fund` | company | Investment vehicle or DAO treasury | Solomon, Theia Research |
|
||||
|
||||
#### Space Development (Astra)
|
||||
|
||||
| Type | Extends | What it tracks | Examples |
|
||||
|------|---------|---------------|----------|
|
||||
| `vehicle` | product | Launch vehicle or spacecraft | Starship, New Glenn, Neutron |
|
||||
| `mission` | — | Specific spaceflight mission | Artemis III, ESCAPADE |
|
||||
| `facility` | — | Launch site, factory, or ground infrastructure | Starbase, LC-36 |
|
||||
| `program` | — | Multi-mission program or initiative | Artemis, Commercial Crew |
|
||||
|
||||
#### Health (Vida)
|
||||
|
||||
| Type | Extends | What it tracks | Examples |
|
||||
|------|---------|---------------|----------|
|
||||
| `therapy` | product | Treatment modality or therapeutic approach | mRNA cancer vaccines, GLP-1 agonists |
|
||||
| `drug` | product | Specific pharmaceutical product | Ozempic, Keytruda |
|
||||
| `insurer` | company | Health insurance organization | UnitedHealthcare, Devoted Health |
|
||||
| `provider` | company | Healthcare delivery organization | Kaiser Permanente, Oak Street Health |
|
||||
| `policy` | — | Legislation, regulation, or administrative rule | GENIUS Act, CMS 2027 Advance Notice |
|
||||
|
||||
#### Entertainment (Clay)
|
||||
|
||||
| Type | Extends | What it tracks | Examples |
|
||||
|------|---------|---------------|----------|
|
||||
| `studio` | company | Production company or media business | Beast Industries, Mediawan |
|
||||
| `creator` | person | Individual content creator or artist | MrBeast, Taylor Swift |
|
||||
| `franchise` | product | IP, franchise, or media property | Claynosaurz, Pudgy Penguins |
|
||||
| `platform` | product | Distribution or social media platform | YouTube, TikTok, Dropout |
|
||||
|
||||
#### AI/Alignment (Theseus)
|
||||
|
||||
| Type | Extends | What it tracks | Examples |
|
||||
|------|---------|---------------|----------|
|
||||
| `lab` | company | AI research laboratory | Anthropic, OpenAI, DeepMind |
|
||||
| `model` | product | AI model or model family | Claude, GPT-4, Gemini |
|
||||
| `framework` | product | Safety framework, governance protocol, or methodology | RSP, Constitutional AI |
|
||||
| `governance_body` | organization | AI governance or safety organization | AISI, FLI, Partnership on AI |
|
||||
|
||||
### Choosing the Right Type
|
||||
|
||||
```
|
||||
Is it a person? → person (or domain-specific: creator)
|
||||
Is it a government/regulatory body? → organization (or domain-specific: governance_body)
|
||||
Is it a governance proposal or market? → decision_market
|
||||
Is it a specific product/tool? → product (or domain-specific: drug, model, vehicle, etc.)
|
||||
Is it an organization that operates? → company (or domain-specific: lab, studio, insurer, etc.)
|
||||
Is it a market segment? → market
|
||||
Is it a policy or regulation? → policy
|
||||
Is it a space mission? → mission
|
||||
Is it a physical facility? → facility
|
||||
Is it a multi-mission program? → program
|
||||
```
|
||||
|
||||
**Rule:** Use the most specific type available. If a DeFi protocol fits `protocol`, use that instead of `company`. If an AI lab fits `lab`, use that instead of `company`. Domain-specific types carry domain-specific fields.
|
||||
|
||||
### Adding New Types
|
||||
|
||||
Core types require a schema PR reviewed by Leo. Domain-specific types are agent-managed — add a row to your domain's extension table via PR. No schema-wide changes needed. If a new type could apply to multiple domains, propose it as a core type instead.
|
||||
|
||||
### Cross-Domain Entity Dedup
|
||||
|
||||
One entity per real-world object. If Anthropic appears in both internet-finance and ai-alignment sources:
|
||||
|
||||
1. **First creator owns the file.** Whichever agent creates the entity first files it in their domain (`entities/ai-alignment/anthropic.md`).
|
||||
2. **Other agents use `secondary_domains`.** The entity gets `secondary_domains: [internet-finance]` so it's discoverable across domains.
|
||||
3. **Both agents can update.** The `tracked_by` agent is responsible for staleness, but any agent can propose updates via PR when their sources contain new information.
|
||||
4. **Type follows primary domain.** If Theseus creates it, it's `lab`. If Rio had created it first, it would be `company`. The type reflects the primary tracking perspective.
|
||||
|
||||
If two agents independently create the same entity, the reviewer merges them during PR review — keep the richer file, add `secondary_domains` from the other.
|
||||
|
||||
## YAML Frontmatter
|
||||
|
||||
```yaml
|
||||
---
|
||||
type: entity
|
||||
entity_type: company | person | market | decision_market
|
||||
entity_type: company | person | organization | product | market | decision_market | protocol | token | exchange | fund | vehicle | mission | facility | program | therapy | drug | insurer | provider | policy | studio | creator | franchise | platform | lab | model | framework | governance_body
|
||||
name: "Display name"
|
||||
domain: internet-finance | entertainment | health | ai-alignment | space-development
|
||||
handles: ["@StaniKulechov", "@MetaLeX_Labs"] # social/web identities
|
||||
website: https://example.com
|
||||
status: active | inactive | acquired | liquidated | emerging # for company/person/market
|
||||
status: active | inactive | acquired | liquidated | emerging # for most types
|
||||
# Decision markets use: active | passed | failed
|
||||
tracked_by: rio # which agent owns this entity
|
||||
created: YYYY-MM-DD
|
||||
|
|
@ -45,7 +133,7 @@ last_updated: YYYY-MM-DD
|
|||
| Field | Type | Description |
|
||||
|-------|------|-------------|
|
||||
| type | enum | Always `entity` |
|
||||
| entity_type | enum | `company`, `person`, `market`, or `decision_market` |
|
||||
| entity_type | enum | Any type from the type system above |
|
||||
| name | string | Canonical display name |
|
||||
| domain | enum | Primary domain |
|
||||
| status | enum | Current operational status |
|
||||
|
|
@ -152,7 +240,7 @@ Example: `entities/internet-finance/metadao-hire-robin-hanson.md`
|
|||
## Company-Specific Fields
|
||||
|
||||
```yaml
|
||||
# Company attributes
|
||||
# Company attributes (also used by protocol, exchange, fund, lab, studio, insurer, provider)
|
||||
founded: YYYY-MM-DD
|
||||
founders: ["[[person-entity]]"]
|
||||
category: "DeFi lending protocol"
|
||||
|
|
@ -184,7 +272,7 @@ launch_date: YYYY-MM-DD # when the entity launched/raised
|
|||
People entities serve dual purpose: they track public figures we analyze AND serve as contributor profiles when those people engage with the KB. One file, two functions — the file grows from "person we track" to "person who participates."
|
||||
|
||||
```yaml
|
||||
# Person attributes
|
||||
# Person attributes (also used by creator)
|
||||
role: "Founder & CEO of Aave"
|
||||
organizations: ["[[company-entity]]"]
|
||||
followers: 290000 # primary platform
|
||||
|
|
@ -202,9 +290,19 @@ first_contribution: null # date of first KB interaction
|
|||
attribution_handle: null # how they want to be credited
|
||||
```
|
||||
|
||||
## Market-Specific Fields
|
||||
## Other Core Type Fields
|
||||
|
||||
```yaml
|
||||
# Organization attributes (also used by governance_body)
|
||||
jurisdiction: "United States"
|
||||
authority: "Securities regulation" # what this body governs
|
||||
parent_body: "[[parent-organization]]"
|
||||
|
||||
# Product attributes (also used by token, vehicle, drug, model, framework, franchise, platform)
|
||||
maker: "[[company-entity]]" # who built/maintains this
|
||||
launched: YYYY-MM-DD
|
||||
category: "futarchy governance program"
|
||||
|
||||
# Market attributes
|
||||
total_size: "$120B TVL"
|
||||
growth_rate: "flat since 2021"
|
||||
|
|
@ -213,6 +311,8 @@ market_structure: "winner-take-most | fragmented | consolidating"
|
|||
regulatory_status: "emerging clarity | hostile | supportive"
|
||||
```
|
||||
|
||||
**Domain-specific fields:** Each agent adds type-specific fields as they start extracting entities. The fields above cover core types. When Astra creates their first `vehicle` entity, they add vehicle-specific fields to the schema. Complexity is earned from actual use, not designed in advance.
|
||||
|
||||
## Body Format
|
||||
|
||||
```markdown
|
||||
|
|
@ -275,9 +375,19 @@ entities/
|
|||
claynosaurz.md
|
||||
pudgy-penguins.md
|
||||
matthew-ball.md
|
||||
beast-industries.md # studio
|
||||
health/
|
||||
devoted-health.md
|
||||
devoted-health.md # insurer
|
||||
function-health.md
|
||||
ozempic.md # drug
|
||||
ai-alignment/
|
||||
anthropic.md # lab
|
||||
claude.md # model
|
||||
rsp.md # framework
|
||||
space-development/
|
||||
spacex.md
|
||||
starship.md # vehicle
|
||||
artemis.md # program
|
||||
```
|
||||
|
||||
**Filename:** Lowercase slugified name. Companies use brand name, people use full name. Decision markets use `{parent}-{proposal-slug}.md`.
|
||||
|
|
@ -299,6 +409,8 @@ Sources often contain entity information. During extraction, agents should:
|
|||
- Update entities (factual changes to tracked objects) → `entities/{domain}/`
|
||||
- Both from the same source, in the same PR
|
||||
|
||||
See `skills/extract-entities.md` for the full extraction process.
|
||||
|
||||
## Key Difference from Claims
|
||||
|
||||
| | Claims | Entities |
|
||||
|
|
|
|||
149
skills/extract-entities.md
Normal file
149
skills/extract-entities.md
Normal file
|
|
@ -0,0 +1,149 @@
|
|||
# Entity Extraction Field Guide
|
||||
|
||||
How to extract entities from source material. This skill works alongside `extract.md` (claim extraction) — both run during source processing.
|
||||
|
||||
## When to Extract Entities
|
||||
|
||||
Every source may contain entity data. During extraction, ask:
|
||||
|
||||
1. **Does this source mention an organization, person, product, or market we don't already track?** → Create a new entity
|
||||
2. **Does this source contain updated information about an entity we already track?** → Update the existing entity (timeline, metrics, status)
|
||||
3. **Does this source describe a decision, proposal, or market outcome?** → Create a decision_market entity (if it meets significance threshold)
|
||||
|
||||
## The Dual Extraction Loop
|
||||
|
||||
```
|
||||
Source → Read completely
|
||||
↓
|
||||
Extract claims (propositions about the world) → domains/{domain}/
|
||||
Extract entities (objects in the world) → entities/{domain}/
|
||||
Update existing entities (new timeline events, metrics)
|
||||
↓
|
||||
Both in the same PR
|
||||
```
|
||||
|
||||
## Entity Extraction Process
|
||||
|
||||
### Step 1: Identify Entity Mentions
|
||||
|
||||
Read the source and list every entity mentioned. For each:
|
||||
- Is it already in `entities/{domain}/`? → Flag for update
|
||||
- Is it new and significant enough to track? → Flag for creation
|
||||
- Is it mentioned in passing with no meaningful data? → Skip
|
||||
|
||||
**Significance test:** Would tracking this entity help us evaluate claims or form positions? If the entity is just background context, skip it.
|
||||
|
||||
### Step 2: Select Entity Type
|
||||
|
||||
Use the most specific type available. See `schemas/entity.md` for the full type system.
|
||||
|
||||
```
|
||||
Is it a person? → person (or domain-specific: creator)
|
||||
Is it a government/regulatory body? → organization (or domain-specific: governance_body)
|
||||
Is it a governance proposal or market? → decision_market
|
||||
Is it a specific product/tool? → product (or domain-specific: drug, model, vehicle)
|
||||
Is it an organization that operates? → company (or domain-specific: lab, studio, insurer)
|
||||
Is it a market segment? → market
|
||||
```
|
||||
|
||||
### Step 3: Extract Frontmatter
|
||||
|
||||
Fill in every field you have data for. Don't guess — leave fields empty rather than fabricating data.
|
||||
|
||||
**Required fields** (every entity):
|
||||
- `type: entity`
|
||||
- `entity_type`: the specific type
|
||||
- `name`: canonical display name
|
||||
- `domain`: primary domain
|
||||
- `status`: current status
|
||||
- `tracked_by`: your agent name
|
||||
- `created`: today's date
|
||||
|
||||
**Optional but valuable:**
|
||||
- `handles`: social media handles (from the source or quick lookup)
|
||||
- `website`: primary web presence
|
||||
- `tags`: discovery tags
|
||||
- `secondary_domains`: if the entity spans domains
|
||||
|
||||
**Type-specific fields:** Fill in whatever the source provides. The schema lists all available fields — use the ones that have data.
|
||||
|
||||
### Step 4: Write the Body
|
||||
|
||||
Follow the body format from `schemas/entity.md`:
|
||||
|
||||
1. **Overview**: What this entity is, why we track it (2-3 sentences)
|
||||
2. **Current State**: Latest known attributes from this source
|
||||
3. **Timeline**: Key events with dates (at minimum, the event from this source)
|
||||
4. **Competitive Position**: Where it sits relative to competitors (if known)
|
||||
5. **Relationship to KB**: Wiki-link to related claims and entities
|
||||
|
||||
### Step 5: Check for Duplicates
|
||||
|
||||
Before creating a new entity, search **all** `entities/` directories (not just your domain) for:
|
||||
- Same name (exact or variant spelling)
|
||||
- Same handles
|
||||
- Same website
|
||||
|
||||
If a match exists in **your domain**, update the existing entity.
|
||||
|
||||
If a match exists in **another domain**, don't create a duplicate. Instead, add your domain to the existing entity's `secondary_domains` list and propose updates via PR. See `schemas/entity.md` → "Cross-Domain Entity Dedup" for the full protocol.
|
||||
|
||||
### Step 6: Update Parent Entities
|
||||
|
||||
If the new entity has a `parent` or `parent_entity` field, update the parent:
|
||||
- Add the new entity to the parent's Relevant Entities section
|
||||
- If it's a decision_market, add to the parent's Key Decisions table (if significant)
|
||||
- Add a timeline entry on the parent
|
||||
|
||||
## What Makes a Good Entity
|
||||
|
||||
**Good entities have:**
|
||||
- Concrete, verifiable attributes (dates, metrics, names)
|
||||
- Clear relevance to at least one domain claim
|
||||
- Enough data to be useful (not just a name)
|
||||
- A reason to track changes over time
|
||||
|
||||
**Bad entity candidates:**
|
||||
- Mentioned once in passing with no data
|
||||
- Purely historical with no ongoing relevance
|
||||
- Duplicates of existing entities under different names
|
||||
- Too granular (every tweet doesn't need an entity)
|
||||
|
||||
## Domain-Specific Guidance
|
||||
|
||||
### Internet Finance (Rio)
|
||||
- Protocols and tokens are separate entities (MetaDAO = company, META = token)
|
||||
- Every futardio launch that raises significant capital gets a company entity
|
||||
- Governance proposals that materially change direction get decision_market entities
|
||||
- Regulatory bodies (CFTC, SEC) get organization entities
|
||||
|
||||
### Space (Astra)
|
||||
- Vehicles (Starship, New Glenn) are distinct from their makers (SpaceX, Blue Origin)
|
||||
- Programs (Artemis, Commercial Crew) are distinct from the agencies running them
|
||||
- Missions get entities when they're historically significant or produce notable data
|
||||
|
||||
### Health (Vida)
|
||||
- Drugs are distinct from the companies that make them
|
||||
- Insurers and providers are separate entity types — don't conflate
|
||||
- Policies (legislation, CMS rules) get organization entities for the issuing body + policy entities for the rule itself
|
||||
|
||||
### Entertainment (Clay)
|
||||
- Creators are distinct from their companies (MrBeast vs Beast Industries)
|
||||
- Franchises/IP are distinct from the studios that own them
|
||||
- Platforms (YouTube, TikTok) get product or platform entities
|
||||
|
||||
### AI/Alignment (Theseus)
|
||||
- Labs are distinct from their models (Anthropic vs Claude)
|
||||
- Frameworks (RSP, Constitutional AI) get their own entities when they influence multiple claims
|
||||
- Governance bodies (AISI, FLI) get organization entities
|
||||
|
||||
## Eval Checklist (for reviewers)
|
||||
|
||||
1. `entity_type` is the most specific available type
|
||||
2. Required fields are all populated
|
||||
3. No fabricated data — empty fields are better than guesses
|
||||
4. Not a duplicate of existing entity
|
||||
5. Meets significance threshold
|
||||
6. Wiki links resolve to real files
|
||||
7. Parent entity updated if applicable
|
||||
8. Filing location is correct: `entities/{domain}/{slug}.md`
|
||||
Loading…
Reference in a new issue