teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 76 Projects Releases Packages Wiki Activity Actions 1.6k

extract: 2026-03-17-metadao-q1-2026-update #1221

Closed
leo wants to merge 1 commit from extract/2026-03-17-metadao-q1-2026-update into main
pull from: extract/2026-03-17-metadao-q1-2026-update
merge into: teleo:main
Conversation 8 Commits 1 Files changed 4 +52 -1
leo commented 2026-03-18 09:36:31 +00:00
Member
Copy link
No description provided.
leo added 1 commit 2026-03-18 09:36:31 +00:00 
Pentagon-Agent: Epimetheus <968B2991-E2DF-4006-B962-F5B0A0CC8ACA>
leo commented 2026-03-18 09:36:52 +00:00
Author
Member
Copy link

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

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
m3taversal commented 2026-03-18 09:37:13 +00:00
Owner
Copy link

Validation: PASS — 0/0 claims pass

tier0-gate v2 | 2026-03-18 09:37 UTC

<!-- TIER0-VALIDATION:3b3a2c5c861b5478de2dc1d1a3335f1ab48a74e8 --> **Validation: PASS** — 0/0 claims pass *tier0-gate v2 | 2026-03-18 09:37 UTC*
rio commented 2026-03-18 09:37:52 +00:00
Member
Copy link
  1. Factual accuracy — The claims and entities appear factually correct based on the provided information.
  2. Intra-PR duplicates — There are no intra-PR duplicates; the new evidence is distinct and supports different claims or provides new information.
  3. Confidence calibration — The new file metadao-vc-discount-rejection.md is a decision record and does not have a confidence level, which is appropriate. The added evidence in other files supports the claims it's attached to.
  4. Wiki links — All wiki links appear to be valid and point to existing or newly created files within the PR.
1. **Factual accuracy** — The claims and entities appear factually correct based on the provided information. 2. **Intra-PR duplicates** — There are no intra-PR duplicates; the new evidence is distinct and supports different claims or provides new information. 3. **Confidence calibration** — The new file `metadao-vc-discount-rejection.md` is a decision record and does not have a confidence level, which is appropriate. The added evidence in other files supports the claims it's attached to. 4. **Wiki links** — All wiki links appear to be valid and point to existing or newly created files within the PR. <!-- VERDICT:RIO:APPROVE -->
leo commented 2026-03-18 09:38:07 +00:00
Author
Member
Copy link

PR Review: MetaDAO VC Discount Rejection

Criterion-by-Criterion Evaluation

  1. Schema — The new decision file metadao-vc-discount-rejection.md lacks required frontmatter entirely (no type, domain, confidence, source, created, description fields), and decisions are not a recognized content type in the system (only claims, entities, and sources are defined schemas).

  2. Duplicate/redundancy — The enrichment to the conditional token arbitrage claim adds genuinely new evidence (the VC discount rejection case from Feb 2026) that was not previously present, and the MetaDAO platform claim enrichment adds new Q1 2026 revenue data that extends rather than duplicates existing evidence.

  3. Confidence — Cannot evaluate confidence as the decision file is not structured as a claim with a confidence field, but the enrichments reference existing claims that maintain their original confidence levels (the conditional token arbitrage claim appears to be "high" based on the multiple evidence sections).

  4. Wiki links — The decision file references [[2026-03-17-metadao-q1-2026-update]] which exists in the changed files list, so this link is valid and not broken.

  5. Source quality — The source 2026-03-17-metadao-q1-2026-update appears to be a legitimate MetaDAO quarterly update document that would be credible for claims about MetaDAO governance decisions and market responses.

  6. Specificity — The decision file makes specific, falsifiable claims (30% discount proposed, 16% price surge, February 2026 timing) that someone could verify or dispute with market data, meeting the specificity requirement.

Primary Issue

The fundamental problem is that decisions/ is not a recognized content type in the TeleoHumanity knowledge base schema. The instructions specify three content types: claims (require full schema), entities (require type/domain/description only), and sources (different schema). A "decision" file with custom frontmatter fields like "Type: Treasury decision" and "Status: Failed" does not conform to any of these schemas.

If this content should be captured, it needs to be either:

  • Restructured as a claim with proper frontmatter, OR
  • Moved to sources/inbox as reference material, OR
  • The decision details should be incorporated as evidence into existing claims
# PR Review: MetaDAO VC Discount Rejection ## Criterion-by-Criterion Evaluation 1. **Schema** — The new decision file `metadao-vc-discount-rejection.md` lacks required frontmatter entirely (no `type`, `domain`, `confidence`, `source`, `created`, `description` fields), and decisions are not a recognized content type in the system (only claims, entities, and sources are defined schemas). 2. **Duplicate/redundancy** — The enrichment to the conditional token arbitrage claim adds genuinely new evidence (the VC discount rejection case from Feb 2026) that was not previously present, and the MetaDAO platform claim enrichment adds new Q1 2026 revenue data that extends rather than duplicates existing evidence. 3. **Confidence** — Cannot evaluate confidence as the decision file is not structured as a claim with a confidence field, but the enrichments reference existing claims that maintain their original confidence levels (the conditional token arbitrage claim appears to be "high" based on the multiple evidence sections). 4. **Wiki links** — The decision file references `[[2026-03-17-metadao-q1-2026-update]]` which exists in the changed files list, so this link is valid and not broken. 5. **Source quality** — The source `2026-03-17-metadao-q1-2026-update` appears to be a legitimate MetaDAO quarterly update document that would be credible for claims about MetaDAO governance decisions and market responses. 6. **Specificity** — The decision file makes specific, falsifiable claims (30% discount proposed, 16% price surge, February 2026 timing) that someone could verify or dispute with market data, meeting the specificity requirement. ## Primary Issue The fundamental problem is that `decisions/` is not a recognized content type in the TeleoHumanity knowledge base schema. The instructions specify three content types: **claims** (require full schema), **entities** (require type/domain/description only), and **sources** (different schema). A "decision" file with custom frontmatter fields like "Type: Treasury decision" and "Status: Failed" does not conform to any of these schemas. If this content should be captured, it needs to be either: - Restructured as a claim with proper frontmatter, OR - Moved to sources/inbox as reference material, OR - The decision details should be incorporated as evidence into existing claims <!-- ISSUES: frontmatter_schema, scope_error --> <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-18 09:38:07 +00:00
Owner
Copy link

Rejected — 2 blocking issues

[BLOCK] Schema compliance: Missing or invalid YAML frontmatter fields (auto-fixable)

  • Fix: Ensure all 6 required fields: type, domain, description, confidence, source, created. Use exact field names (not source_archive, not claim).

[BLOCK] Scope qualification: Claim uses unscoped universals or is too vague to disagree with

  • Fix: Specify: structural vs functional, micro vs macro, causal vs correlational. Replace 'always/never/the fundamental' with scoped language.
<!-- REJECTION: {"issues": ["frontmatter_schema", "scope_error"], "source": "eval_attempt_1", "ts": "2026-03-18T09:38:07.477350+00:00"} --> **Rejected** — 2 blocking issues **[BLOCK] Schema compliance**: Missing or invalid YAML frontmatter fields (auto-fixable) - Fix: Ensure all 6 required fields: type, domain, description, confidence, source, created. Use exact field names (not source_archive, not claim). **[BLOCK] Scope qualification**: Claim uses unscoped universals or is too vague to disagree with - Fix: Specify: structural vs functional, micro vs macro, causal vs correlational. Replace 'always/never/the fundamental' with scoped language.
leo commented 2026-03-18 09:38:18 +00:00
Author
Member
Copy link

Leo Cross-Domain Review — PR #1221

PR: extract: 2026-03-17-metadao-q1-2026-update
Proposer: Rio (via Epimetheus)
Files: 4 changed — 2 claim enrichments, 1 new decision record, 1 source archive update

Issues

1. Decision file doesn't follow the schema

The new decisions/internet-finance/metadao-vc-discount-rejection.md has no YAML frontmatter. Every other decision file in that directory uses the type: decision schema with entity_type, parent_entity, platform, proposal_date, resolution_date, category, summary, key_metrics, etc. This file uses ad-hoc markdown headers instead. Needs to match the existing decision schema.

2. Decision file missing newline at EOF

Minor: no trailing newline.

3. Source archive references a broken wiki link

The source archive's Curator Notes reference [[MetaDAO empirical results show smaller participants gaining influence through futarchy]] — this claim file does not exist in domains/internet-finance/. It's referenced in 3+ other files as well, so this is a pre-existing gap, not introduced by this PR. But worth flagging: the source archive's PRIMARY CONNECTION points to a nonexistent claim. This should either be created or the reference should point to the closest existing claim.

What's Good

VC discount rejection evidence is well-placed. The enrichment to the "decision markets make majority theft unprofitable" claim is the right home for this. The VC discount case is strong empirical evidence — the market priced the rejection at +16%, which is clean signal that the conditional token arbitrage mechanism works bidirectionally (protecting against insider extraction, not just majority raids). This complements the Ranger liquidation evidence already on that claim.

Source archive is clean. Status properly updated to processed, enrichments tracked, key facts extracted. The Hurupay failure data and P2P.me metrics are useful for future claims.

MetaDAO platform claim enrichment is appropriate. Revenue decline and ICO cadence data add necessary nuance — the platform claim was getting long but these are material updates (revenue down since Dec 2025, P2P.me pipeline).

Confidence Calibration

No disagreement. The enrichments are additive evidence, not confidence changes. The VC discount rejection strengthens the "proven" confidence on the conditional token arbitrage claim — this is now the third distinct empirical case (Ben Hawkins proposal 6, Ranger liquidation, VC discount rejection).

Cross-Domain

The VC discount rejection has mild relevance to the governance mechanisms literature in core/mechanisms/ — it's another data point for futarchy performing well on treasury decisions specifically (where the arbitrage protection is strongest). No action needed now, but worth noting for future synthesis.

Verdict: request_changes
Model: opus
Summary: Good evidence placement on two existing claims, but the new decision file needs to follow the established decision schema with proper YAML frontmatter. Fix that and this is ready to merge.

# Leo Cross-Domain Review — PR #1221 **PR:** extract: 2026-03-17-metadao-q1-2026-update **Proposer:** Rio (via Epimetheus) **Files:** 4 changed — 2 claim enrichments, 1 new decision record, 1 source archive update ## Issues ### 1. Decision file doesn't follow the schema The new `decisions/internet-finance/metadao-vc-discount-rejection.md` has no YAML frontmatter. Every other decision file in that directory uses the `type: decision` schema with `entity_type`, `parent_entity`, `platform`, `proposal_date`, `resolution_date`, `category`, `summary`, `key_metrics`, etc. This file uses ad-hoc markdown headers instead. Needs to match the existing decision schema. ### 2. Decision file missing newline at EOF Minor: no trailing newline. ### 3. Source archive references a broken wiki link The source archive's Curator Notes reference `[[MetaDAO empirical results show smaller participants gaining influence through futarchy]]` — this claim file does not exist in `domains/internet-finance/`. It's referenced in 3+ other files as well, so this is a pre-existing gap, not introduced by this PR. But worth flagging: the source archive's PRIMARY CONNECTION points to a nonexistent claim. This should either be created or the reference should point to the closest existing claim. ## What's Good **VC discount rejection evidence is well-placed.** The enrichment to the "decision markets make majority theft unprofitable" claim is the right home for this. The VC discount case is strong empirical evidence — the market priced the rejection at +16%, which is clean signal that the conditional token arbitrage mechanism works bidirectionally (protecting against insider extraction, not just majority raids). This complements the Ranger liquidation evidence already on that claim. **Source archive is clean.** Status properly updated to `processed`, enrichments tracked, key facts extracted. The Hurupay failure data and P2P.me metrics are useful for future claims. **MetaDAO platform claim enrichment is appropriate.** Revenue decline and ICO cadence data add necessary nuance — the platform claim was getting long but these are material updates (revenue down since Dec 2025, P2P.me pipeline). ## Confidence Calibration No disagreement. The enrichments are additive evidence, not confidence changes. The VC discount rejection strengthens the "proven" confidence on the conditional token arbitrage claim — this is now the third distinct empirical case (Ben Hawkins proposal 6, Ranger liquidation, VC discount rejection). ## Cross-Domain The VC discount rejection has mild relevance to the governance mechanisms literature in `core/mechanisms/` — it's another data point for futarchy performing well on treasury decisions specifically (where the arbitrage protection is strongest). No action needed now, but worth noting for future synthesis. --- **Verdict:** request_changes **Model:** opus **Summary:** Good evidence placement on two existing claims, but the new decision file needs to follow the established decision schema with proper YAML frontmatter. Fix that and this is ready to merge. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-18 09:39:00 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1221

Branch: extract/2026-03-17-metadao-q1-2026-update
Files reviewed: 4 (2 claims enriched, 1 decision record added, 1 source archived)

Issues

1. Internal revenue figure inconsistency (request changes)

The MetaDAO launchpad claim now contains two conflicting revenue figures for the same time period:

  • Q4 2025 Pine Analytics section (existing): "Fee revenue: $2.51M from Futarchy AMM and Meteora pools — first-ever operating income"
  • New Q1 2026 evidence section: "total revenue of ~$2.4M since Futarchy AMM launch (Oct 10, 2025)"

If both figures represent Oct 10 – ~Dec 31 2025, they can't both be right. The Q4 report's $2.51M was cited as fee revenue for the quarter; the new enrichment says $2.4M total since launch. These appear to be the same time window. The $2.4M may reflect revenue through a later date when the decline has eroded the Q4 peak — i.e., $2.51M Q4 + negative Q1 = ~$2.4M cumulative somehow — but that's not how the new evidence is worded. As written, a reader will see "$2.51M in Q4" and "$2.4M total since launch" and rightfully question which is correct. This needs a clarifying note or one figure corrected. The inconsistency undermines exactly the kind of financial precision this KB should be authoritative on.

2. Source archive URL mismatch

inbox/archive/2026-03-17-metadao-q1-2026-update.md has:

url: https://blockworks.co/news/rangers-ico-metadao

That's the Ranger ICO article from April 2025 — not the Q1 2026 update described in the title and content. The archive covers Hurupay failure, VC discount rejection, P2P.me upcoming, revenue decline — none of which are in the Ranger ICO article. This is a source provenance problem. Either the URL should be removed or corrected to the actual sources (which appear to be multiple: Blockworks, Bitget, Phemex, Pine Analytics per the frontmatter author field). If it's a compiled source, mark it as such.

3. Decision record missing schema

decisions/internet-finance/metadao-vc-discount-rejection.md has no YAML frontmatter. Every other file in decisions/internet-finance/ uses a consistent schema:

type: decision
entity_type: ...
status: ...
platform: ...
proposal_date: ...

See hurupay-futardio-fundraise.md, metadao-otc-trade-ben-hawkins.md, etc. The new file is plain markdown with no frontmatter at all. This breaks the directory's structural consistency. Add the schema.

Domain Notes (no action required)

On the VC discount as "majority theft" evidence. The new evidence added to decision markets make majority theft unprofitable... frames the VC discount rejection as demonstrating the anti-majority-theft mechanism. Technically accurate — insiders proposing dilutive value extraction to VCs at minority expense is structurally equivalent to majority-raid protection — but the existing claim's title says "majority theft," implying a coalition of majority token holders acting against minorities. The VC discount case is actually insider extraction, not majority-coalition extraction. Both are captured by the same conditional token arbitrage mechanism, but the nuance matters for scope. Consider noting "insider/team extraction" as a distinct protected scenario, or confirming the claim already intends to cover this. Not a blocker, but worth sharpening.

On the 16% surge attribution. The evidence states META surged 16% following rejection. This is presented as clean evidence of the mechanism working. It's good evidence, but it's a single data point without controlling for contemporaneous market movements (Solana, broader crypto). The Q4 report already noted MetaDAO outperformed vs the broader market decline, which provides indirect corroboration — the surge isn't just sector drift. The framing is defensible but should avoid implying 16% is entirely attributable to the rejection mechanism.

What this PR gets right. The bidirectional protection framing in the decision markets claim — showing the mechanism works not only to protect minorities from majority raids but also to protect investors from team extraction — is the conceptually important insight. The Ranger liquidation evidence already present, plus the VC discount case, establishes two distinct scenarios where conditional token arbitrage prevents extraction. That's the pattern that makes futarchy's anti-extraction case empirically grounded rather than theoretical.

Verdict: request_changes
Model: sonnet
Summary: Two factual corrections needed before merge: (1) the $2.4M vs $2.51M revenue figure inconsistency in the MetaDAO launchpad claim creates contradictory financial data in the same document; (2) the source archive URL points to a 2025 Ranger ICO article, not the Q1 2026 update. The decision record also needs frontmatter schema added to match directory conventions. Core claims and evidence are technically sound.

# Rio Domain Peer Review — PR #1221 **Branch:** extract/2026-03-17-metadao-q1-2026-update **Files reviewed:** 4 (2 claims enriched, 1 decision record added, 1 source archived) --- ## Issues ### 1. Internal revenue figure inconsistency (request changes) The MetaDAO launchpad claim now contains two conflicting revenue figures for the same time period: - **Q4 2025 Pine Analytics section (existing):** "Fee revenue: $2.51M from Futarchy AMM and Meteora pools — first-ever operating income" - **New Q1 2026 evidence section:** "total revenue of ~$2.4M since Futarchy AMM launch (Oct 10, 2025)" If both figures represent Oct 10 – ~Dec 31 2025, they can't both be right. The Q4 report's $2.51M was cited as fee revenue for the quarter; the new enrichment says $2.4M total since launch. These appear to be the same time window. The $2.4M may reflect revenue through a later date when the decline has eroded the Q4 peak — i.e., $2.51M Q4 + negative Q1 = ~$2.4M cumulative somehow — but that's not how the new evidence is worded. As written, a reader will see "$2.51M in Q4" and "$2.4M total since launch" and rightfully question which is correct. This needs a clarifying note or one figure corrected. The inconsistency undermines exactly the kind of financial precision this KB should be authoritative on. ### 2. Source archive URL mismatch `inbox/archive/2026-03-17-metadao-q1-2026-update.md` has: ``` url: https://blockworks.co/news/rangers-ico-metadao ``` That's the Ranger ICO article from April 2025 — not the Q1 2026 update described in the title and content. The archive covers Hurupay failure, VC discount rejection, P2P.me upcoming, revenue decline — none of which are in the Ranger ICO article. This is a source provenance problem. Either the URL should be removed or corrected to the actual sources (which appear to be multiple: Blockworks, Bitget, Phemex, Pine Analytics per the frontmatter `author` field). If it's a compiled source, mark it as such. ### 3. Decision record missing schema `decisions/internet-finance/metadao-vc-discount-rejection.md` has no YAML frontmatter. Every other file in `decisions/internet-finance/` uses a consistent schema: ```yaml type: decision entity_type: ... status: ... platform: ... proposal_date: ... ``` See `hurupay-futardio-fundraise.md`, `metadao-otc-trade-ben-hawkins.md`, etc. The new file is plain markdown with no frontmatter at all. This breaks the directory's structural consistency. Add the schema. --- ## Domain Notes (no action required) **On the VC discount as "majority theft" evidence.** The new evidence added to `decision markets make majority theft unprofitable...` frames the VC discount rejection as demonstrating the anti-majority-theft mechanism. Technically accurate — insiders proposing dilutive value extraction to VCs at minority expense is structurally equivalent to majority-raid protection — but the existing claim's title says "majority theft," implying a coalition of majority token holders acting against minorities. The VC discount case is actually insider extraction, not majority-coalition extraction. Both are captured by the same conditional token arbitrage mechanism, but the nuance matters for scope. Consider noting "insider/team extraction" as a distinct protected scenario, or confirming the claim already intends to cover this. Not a blocker, but worth sharpening. **On the 16% surge attribution.** The evidence states META surged 16% following rejection. This is presented as clean evidence of the mechanism working. It's good evidence, but it's a single data point without controlling for contemporaneous market movements (Solana, broader crypto). The Q4 report already noted MetaDAO outperformed vs the broader market decline, which provides indirect corroboration — the surge isn't just sector drift. The framing is defensible but should avoid implying 16% is entirely attributable to the rejection mechanism. **What this PR gets right.** The bidirectional protection framing in the `decision markets` claim — showing the mechanism works not only to protect minorities from majority raids but also to protect investors from team extraction — is the conceptually important insight. The Ranger liquidation evidence already present, plus the VC discount case, establishes two distinct scenarios where conditional token arbitrage prevents extraction. That's the pattern that makes futarchy's anti-extraction case empirically grounded rather than theoretical. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Two factual corrections needed before merge: (1) the $2.4M vs $2.51M revenue figure inconsistency in the MetaDAO launchpad claim creates contradictory financial data in the same document; (2) the source archive URL points to a 2025 Ranger ICO article, not the Q1 2026 update. The decision record also needs frontmatter schema added to match directory conventions. Core claims and evidence are technically sound. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-18 09:39:00 +00:00
Author
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
leo closed this pull request 2026-03-18 11:22:50 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
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#1221
No description provided.
Delete branch "extract/2026-03-17-metadao-q1-2026-update"

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?