144 lines
5.5 KiB
Markdown
144 lines
5.5 KiB
Markdown
# Decision Schema
|
|
|
|
Decisions are governance events with terminal states — they resolve and are done. Unlike entities (persistent objects that accumulate state), decisions are events that produce an outcome.
|
|
|
|
```
|
|
Source → Decision (what was proposed, what happened)
|
|
↓
|
|
Parent Entity (timeline entry + Key Decisions table)
|
|
↓
|
|
Claims (optional — only if the decision reveals novel mechanism insight)
|
|
```
|
|
|
|
Decisions include futarchy proposals, prediction market questions, governance votes, and regulatory rulings. They are filed in `decisions/{domain}/`, separate from entities and claims.
|
|
|
|
## YAML Frontmatter
|
|
|
|
```yaml
|
|
---
|
|
type: decision
|
|
domain: internet-finance | entertainment | health | ai-alignment | space-development
|
|
description: "One sentence describing the proposal and its outcome"
|
|
parent_entity: "[[metadao]]"
|
|
status: active | passed | failed | expired | cancelled
|
|
platform: "futardio | polymarket | kalshi | snapshot | tally | other"
|
|
proposer: "proph3t"
|
|
proposal_url: "https://..."
|
|
proposal_date: YYYY-MM-DD
|
|
resolution_date: YYYY-MM-DD # null if active
|
|
category: "treasury | fundraise | hiring | mechanism | liquidation | grants | strategy | parameter | launch"
|
|
summary: "One-sentence description of what the proposal does"
|
|
tracked_by: rio
|
|
created: YYYY-MM-DD
|
|
---
|
|
```
|
|
|
|
## Required Fields
|
|
|
|
| Field | Type | Description |
|
|
|-------|------|-------------|
|
|
| type | enum | Always `decision` |
|
|
| domain | enum | Primary domain |
|
|
| description | string | One sentence adding context beyond the title |
|
|
| parent_entity | wiki-link | The organization this decision belongs to |
|
|
| status | enum | Current state: active, passed, failed, expired, cancelled |
|
|
| proposal_date | date | When proposed/created |
|
|
| tracked_by | string | Agent responsible for this decision |
|
|
| created | date | When decision file was created |
|
|
|
|
## Optional Fields
|
|
|
|
| Field | Type | Description |
|
|
|-------|------|-------------|
|
|
| platform | string | Where the market/vote lives |
|
|
| proposer | string | Who created the proposal |
|
|
| proposal_url | string | Canonical link to the market/proposal |
|
|
| resolution_date | date | When resolved (null if active) |
|
|
| category | enum | Type of governance action |
|
|
| summary | string | One-sentence description |
|
|
|
|
## Volume Fields (platform-specific)
|
|
|
|
```yaml
|
|
# Futarchy proposals (governance decisions):
|
|
pass_volume: "$150K" # capital backing pass outcome
|
|
fail_volume: "$100K" # capital backing fail outcome
|
|
|
|
# Futarchy launches (ICOs via Futardio):
|
|
funding_target: "$2M"
|
|
total_committed: "$103M" # total capital committed (demand signal)
|
|
amount_raised: "$8M" # actual capital received after pro-rata
|
|
|
|
# Prediction markets (Polymarket, Kalshi):
|
|
market_volume: "$3.2B" # total trading volume
|
|
peak_odds: "65%" # peak probability for primary outcome
|
|
```
|
|
|
|
## Filing Convention
|
|
|
|
**Location:** `decisions/{domain}/{parent-slug}-{proposal-slug}.md`
|
|
|
|
```
|
|
decisions/
|
|
internet-finance/
|
|
metadao-hire-robin-hanson.md
|
|
metadao-burn-993-percent-meta.md
|
|
deans-list-implement-vesting.md
|
|
drift-fund-working-group.md
|
|
```
|
|
|
|
**Filename:** `{parent-slug}-{proposal-slug}.md`. Lowercase, hyphenated.
|
|
|
|
## What qualifies for a decision file vs. timeline entry only
|
|
|
|
- **Decision file:** Proposals with real capital at stake, governance decisions that changed organizational direction, markets that produced notable information, or contested outcomes (significant volume on both sides — a contested failure is more informative than an uncontested pass)
|
|
- **Timeline entry only:** Test proposals, spam, trivial parameter tweaks, minor operational minutiae, uncontested routine decisions
|
|
- **Estimated ratio:** ~33-40% of real proposals qualify for a decision file
|
|
|
|
## Extraction output for proposal sources
|
|
|
|
1. **Primary:** Decision file with structured frontmatter → `decisions/{domain}/`
|
|
2. **Secondary:** Timeline entry on parent entity (one-line summary + date)
|
|
3. **Optional:** Claims ONLY if the proposal contains novel mechanism insight, surprising market outcome, or instructive governance dynamics (~20% of proposals)
|
|
|
|
## Eval checklist (all mechanical)
|
|
|
|
1. `parent_entity` exists in entity index
|
|
2. Dates are valid YYYY-MM-DD and chronologically coherent (proposal_date ≤ resolution_date)
|
|
3. `status` matches source data (passed/failed/active)
|
|
4. Not a duplicate of existing decision
|
|
5. Meets significance threshold (not test/spam/trivial)
|
|
|
|
**Wiki links use filenames only** (e.g., `[[metadao-hire-robin-hanson]]`), not full paths.
|
|
|
|
## Body Format
|
|
|
|
```markdown
|
|
# [Parent Entity]: [Proposal Title]
|
|
|
|
## Summary
|
|
[What the proposal does and why it matters — 2-3 sentences]
|
|
|
|
## Market Data
|
|
- **Volume:** $X
|
|
- **Outcome:** Passed/Failed/Pending
|
|
- **Key participants:** [notable traders, proposers, commenters]
|
|
|
|
## Significance
|
|
[Why this decision matters — what it reveals about governance dynamics, organizational direction, or mechanism design]
|
|
|
|
## Relationship to KB
|
|
- [[parent-entity]] — governance decision
|
|
- [[relevant-claim]] — how this decision relates to broader thesis
|
|
```
|
|
|
|
## Key Difference from Entities
|
|
|
|
| | Entities | Decisions |
|
|
|---|---|---|
|
|
| Nature | Persistent objects | Events with terminal states |
|
|
| Change model | Attribute updates over time | Resolve once (pass/fail) |
|
|
| Filing | `entities/{domain}/` | `decisions/{domain}/` |
|
|
| Title format | "Company Name" | "Parent: Proposal Title" |
|
|
| Lifecycle | Active → inactive/acquired | Active → passed/failed/expired |
|
|
| Value | Situational awareness | Governance signal + mechanism data |
|