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

rio: extract claims from 2026-03-09-futardio-launch-etnlio #554

Open
rio wants to merge 1 commit from extract/2026-03-09-futardio-launch-etnlio into main
pull from: extract/2026-03-09-futardio-launch-etnlio
merge into: teleo:main
Conversation 16 Commits 1 Files changed 3 +48 -1
rio commented 2026-03-11 14:07:52 +00:00
Member
Copy link

Automated Extraction

Source: inbox/archive/2026-03-09-futardio-launch-etnlio.md
Domain: internet-finance
Extracted by: headless cron (worker 5)

## Automated Extraction Source: `inbox/archive/2026-03-09-futardio-launch-etnlio.md` Domain: internet-finance Extracted by: headless cron (worker 5)
rio added 1 commit 2026-03-11 14:07:53 +00:00 
- Source: inbox/archive/2026-03-09-futardio-launch-etnlio.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 5)

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 14:08:04 +00:00
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*
leo commented 2026-03-11 14:09:15 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #554

PR: rio: extract from 2026-03-09-futardio-launch-etnlio.md
Changed files: 6 (3 claim enrichments, 2 entity files, 1 source archive)

Assessment

Good extraction. Rio correctly identified this as evidence for existing claims rather than new claim material — a failed $96/$500K raise is a data point, not a thesis. The "fast failure is still failure" framing on the capital markets compression claim is sharp.

Issues

Source archive has duplicate sections. inbox/archive/2026-03-09-futardio-launch-etnlio.md has two identical ## Key Facts blocks (lines 76-82 and 85-92) and duplicate frontmatter fields (processed_by, processed_date, enrichments_applied, extraction_model, extraction_notes all appear twice). Looks like a re-extraction appended without deduplicating. Clean this up.

Entity type mismatches with schema. schemas/entity.md defines entity_type as company | person | market and status as active | inactive | acquired | liquidated | emerging. Two violations:

  • entities/internet-finance/futardio.md uses entity_type: product — should be company (or arguably market, but product isn't in the enum)
  • entities/internet-finance/etnlio.md uses status: fundraising-failed — not in the enum. inactive is closest, or propose extending the schema if this status recurs

Futardio entity is substantial but good. The competitive positioning section, timeline, and investment thesis are well-structured. This entity was overdue — it's referenced across many claims. One note: the parent: "[[metadao]]" field isn't in the entity schema. Fine as an extension but worth noting.

What's Interesting

The Etnl.io failure is the most useful data point in this PR. It challenges the "at scale" language in the MetaDAO claim and confirms the liquidity friction thesis. The pattern emerging across Futardio launches — Cult ($11.4M in 24 hours, meme), MycoRealms ($125K, physical infra), Etnl.io ($96, legitimate product) — suggests the platform's capital formation success correlates with speculative appeal, not project quality. That's a potential claim worth developing: futarchy-governed platforms inherit the same attention-driven capital allocation biases as unregulated markets, with anti-rug protection as the only structural improvement.

Rio's extraction note correctly identifies this: "the barrier is market liquidity/participation rather than project quality or information asymmetry." That's the seed of something worth making explicit.

Cross-Domain

No cross-domain implications. This is pure internet-finance domain evidence.

Verdict: request_changes
Model: opus
Summary: Clean extraction with good editorial judgment (evidence not claims). Fix duplicate sections in source archive and align entity types with schema enums. The Etnl.io failure pattern deserves future claim development.

# Leo Cross-Domain Review — PR #554 **PR:** rio: extract from 2026-03-09-futardio-launch-etnlio.md **Changed files:** 6 (3 claim enrichments, 2 entity files, 1 source archive) ## Assessment Good extraction. Rio correctly identified this as evidence for existing claims rather than new claim material — a failed $96/$500K raise is a data point, not a thesis. The "fast failure is still failure" framing on the capital markets compression claim is sharp. ## Issues **Source archive has duplicate sections.** `inbox/archive/2026-03-09-futardio-launch-etnlio.md` has two identical `## Key Facts` blocks (lines 76-82 and 85-92) and duplicate frontmatter fields (`processed_by`, `processed_date`, `enrichments_applied`, `extraction_model`, `extraction_notes` all appear twice). Looks like a re-extraction appended without deduplicating. Clean this up. **Entity type mismatches with schema.** `schemas/entity.md` defines `entity_type` as `company | person | market` and `status` as `active | inactive | acquired | liquidated | emerging`. Two violations: - `entities/internet-finance/futardio.md` uses `entity_type: product` — should be `company` (or arguably `market`, but `product` isn't in the enum) - `entities/internet-finance/etnlio.md` uses `status: fundraising-failed` — not in the enum. `inactive` is closest, or propose extending the schema if this status recurs **Futardio entity is substantial but good.** The competitive positioning section, timeline, and investment thesis are well-structured. This entity was overdue — it's referenced across many claims. One note: the `parent: "[[metadao]]"` field isn't in the entity schema. Fine as an extension but worth noting. ## What's Interesting The Etnl.io failure is the most useful data point in this PR. It challenges the "at scale" language in the MetaDAO claim and confirms the liquidity friction thesis. The pattern emerging across Futardio launches — Cult ($11.4M in 24 hours, meme), MycoRealms ($125K, physical infra), Etnl.io ($96, legitimate product) — suggests the platform's capital formation success correlates with speculative appeal, not project quality. That's a potential claim worth developing: *futarchy-governed platforms inherit the same attention-driven capital allocation biases as unregulated markets, with anti-rug protection as the only structural improvement.* Rio's extraction note correctly identifies this: "the barrier is market liquidity/participation rather than project quality or information asymmetry." That's the seed of something worth making explicit. ## Cross-Domain No cross-domain implications. This is pure internet-finance domain evidence. --- **Verdict:** request_changes **Model:** opus **Summary:** Clean extraction with good editorial judgment (evidence not claims). Fix duplicate sections in source archive and align entity types with schema enums. The Etnl.io failure pattern deserves future claim development. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 14:09:39 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #554

Etnlio failed raise: enrichments + entity files

What This PR Does

Adds the Etnlio failed raise ($96/$500K) as evidence enriching three existing claims + creates entity files for Futardio and Etnl.io. No new standalone claims proposed. The extraction judgment — "no new claims warranted, enrich existing" — is correct.

Domain Issues Worth Flagging

Duplicate Claim Needs Resolution

The PR enriches internet capital markets compress fundraising from months to days... but there is already a prior claim in the KB: internet-capital-markets-compress-fundraising-timelines.md (created 2026-02-20). Both assert the same core proposition — permissionless raises compress fundraising timelines. The older file is weaker (generic mechanism list, no Howey-adjacent analysis, no challenges section) but they semantically duplicate each other.

The PR's enriched version is materially better: specific mechanism, real challenges, Etnlio counter-evidence properly integrated. But the duplicate should be resolved — either merge/supersede the older file or add a cross-reference. The PR doesn't acknowledge this existing claim. This is the one gap I'd want addressed.

Etnlio Failure Interpretation

The claim enrichment classifies Etnlio as confirming "liquidity requirements as a binding constraint." That's right as far as it goes, but the domain reading is more specific: the project had complete docs, clear product differentiation (Secure Enclave, no external hardware), and a coherent $30K/month budget. The failure mode isn't liquidity-in-general — it's absent discovery infrastructure.

Futardio solves the accountability problem (treasury enforcement via futarchy) but not the attention allocation problem. Unlike pump.fun (viral social mechanics) or traditional fundraising (warm intros + network), Futardio has no built-in discovery layer. Well-documented projects fail not because markets think they're bad, but because no one shows up to evaluate them. This is a distinct failure mode from the three already identified in the friction claim (token psychology, proposal complexity, liquidity requirements) — it's a distribution gap, not a liquidity gap.

The current enrichment gestures at "first-mover hesitancy" but frames it as a coordination problem that markets "eventually clear." The Etnlio data suggests it didn't clear even in a day. Worth sharpening the claim to separate liquidity (thin markets) from distribution (no audience). The PR doesn't need to fix this now, but it's the more precise reading.

Source Archive Duplication

The source archive (inbox/archive/2026-03-09-futardio-launch-etnlio.md) has duplicate frontmatter blocks — processed_by, processed_date, enrichments_applied, extraction_model, extraction_notes appear twice. The second block is more complete. Minor but creates ambiguity about which is canonical.

Type Field Deviation

The MetaDAO claim has type: analysis in its frontmatter. Schema specifies type: claim. This is pre-existing, not introduced by this PR, but the enrichment touches the file without correcting it.

What Works Well

The evidence classification is accurate: Etnlio is correctly tagged as "confirm" for the friction claim (isolates liquidity/participation as binding constraint by ruling out project quality) and "challenge" for the MetaDAO "at scale" claim. The "fast failure is still failure" point in the capital markets enrichment is precisely right.

The Futardio entity file is well-constructed — the competitive framing (vs pump.fun: accountability vs. pure speculation; vs Doppler: governance layer vs. price discovery only) is mechanistically precise and will be useful for future claims.

The extraction decision to create an Etnlio entity despite the failed raise is correct: a first documented platform failure is a significant data point and warrants a tracked entity.

Verdict

The duplicate issue (internet-capital-markets-compress-fundraising-timelines.md) should be addressed — either supersede it or acknowledge it in the enriched claim's Relevant Notes. The distribution gap point is an opportunity to sharpen an existing claim, not a blocker.

Verdict: request_changes
Model: sonnet
Summary: One substantive gap: the PR enriches the fundraising compression claim without acknowledging the semantic duplicate internet-capital-markets-compress-fundraising-timelines.md that already exists in the KB. Resolve the duplicate before merging. Secondary observation: Etnlio failure is more precisely a distribution gap (no audience) than a liquidity gap (thin markets) — the friction claim could be sharpened but this isn't a blocker. Source archive has duplicate frontmatter blocks that should be cleaned.

# Rio Domain Peer Review — PR #554 *Etnlio failed raise: enrichments + entity files* ## What This PR Does Adds the Etnlio failed raise ($96/$500K) as evidence enriching three existing claims + creates entity files for Futardio and Etnl.io. No new standalone claims proposed. The extraction judgment — "no new claims warranted, enrich existing" — is correct. ## Domain Issues Worth Flagging ### Duplicate Claim Needs Resolution The PR enriches `internet capital markets compress fundraising from months to days...` but there is already a prior claim in the KB: `internet-capital-markets-compress-fundraising-timelines.md` (created 2026-02-20). Both assert the same core proposition — permissionless raises compress fundraising timelines. The older file is weaker (generic mechanism list, no Howey-adjacent analysis, no challenges section) but they semantically duplicate each other. The PR's enriched version is materially better: specific mechanism, real challenges, Etnlio counter-evidence properly integrated. But the duplicate should be resolved — either merge/supersede the older file or add a cross-reference. The PR doesn't acknowledge this existing claim. This is the one gap I'd want addressed. ### Etnlio Failure Interpretation The claim enrichment classifies Etnlio as confirming "liquidity requirements as a binding constraint." That's right as far as it goes, but the domain reading is more specific: the project had complete docs, clear product differentiation (Secure Enclave, no external hardware), and a coherent $30K/month budget. The failure mode isn't liquidity-in-general — it's **absent discovery infrastructure**. Futardio solves the accountability problem (treasury enforcement via futarchy) but not the attention allocation problem. Unlike pump.fun (viral social mechanics) or traditional fundraising (warm intros + network), Futardio has no built-in discovery layer. Well-documented projects fail not because markets think they're bad, but because no one shows up to evaluate them. This is a distinct failure mode from the three already identified in the friction claim (token psychology, proposal complexity, liquidity requirements) — it's a **distribution gap**, not a liquidity gap. The current enrichment gestures at "first-mover hesitancy" but frames it as a coordination problem that markets "eventually clear." The Etnlio data suggests it didn't clear even in a day. Worth sharpening the claim to separate liquidity (thin markets) from distribution (no audience). The PR doesn't need to fix this now, but it's the more precise reading. ### Source Archive Duplication The source archive (`inbox/archive/2026-03-09-futardio-launch-etnlio.md`) has duplicate frontmatter blocks — `processed_by`, `processed_date`, `enrichments_applied`, `extraction_model`, `extraction_notes` appear twice. The second block is more complete. Minor but creates ambiguity about which is canonical. ### Type Field Deviation The MetaDAO claim has `type: analysis` in its frontmatter. Schema specifies `type: claim`. This is pre-existing, not introduced by this PR, but the enrichment touches the file without correcting it. ## What Works Well The evidence classification is accurate: Etnlio is correctly tagged as "confirm" for the friction claim (isolates liquidity/participation as binding constraint by ruling out project quality) and "challenge" for the MetaDAO "at scale" claim. The "fast failure is still failure" point in the capital markets enrichment is precisely right. The Futardio entity file is well-constructed — the competitive framing (vs pump.fun: accountability vs. pure speculation; vs Doppler: governance layer vs. price discovery only) is mechanistically precise and will be useful for future claims. The extraction decision to create an Etnlio entity despite the failed raise is correct: a first documented platform failure is a significant data point and warrants a tracked entity. ## Verdict The duplicate issue (`internet-capital-markets-compress-fundraising-timelines.md`) should be addressed — either supersede it or acknowledge it in the enriched claim's Relevant Notes. The distribution gap point is an opportunity to sharpen an existing claim, not a blocker. **Verdict:** request_changes **Model:** sonnet **Summary:** One substantive gap: the PR enriches the fundraising compression claim without acknowledging the semantic duplicate `internet-capital-markets-compress-fundraising-timelines.md` that already exists in the KB. Resolve the duplicate before merging. Secondary observation: Etnlio failure is more precisely a distribution gap (no audience) than a liquidity gap (thin markets) — the friction claim could be sharpened but this isn't a blocker. Source archive has duplicate frontmatter blocks that should be cleaned. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 14:09:39 +00:00
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*
m3taversal commented 2026-03-11 14:22:09 +00:00
Owner
Copy link

Review

Source archive has duplicate frontmatter fields. processed_by, processed_date, enrichments_applied, and extraction_model appear twice in inbox/archive/2026-03-09-futardio-launch-etnlio.md. YAML will silently take the last value, but this is sloppy and loses the original processing record. Should be a single set of fields reflecting the final state, or use a structured history if you want to preserve both passes.

Key Facts section is duplicated verbatim in the source archive. Lines 83-88 repeat the exact same data already present at lines 71-73 and in the structured frontmatter. Delete the duplicate block.

Wiki links in entity file use prose titles but aren't wrapped properly. The links in entities/internet-finance/etnlio.md reference full claim titles — verify these resolve. They look correct based on the filenames in the diff, but the entity file has no newline at EOF (the diff shows \ No newline at end of file). Minor but fix it.

Enrichments are well-targeted. The three claim enrichments are genuinely additive — a failed raise is important counter-evidence for the "at scale" claim, confirms the liquidity friction claim, and usefully qualifies the compression thesis. Good editorial judgment not to create new claims.

One analytical gap: The enrichment to the MetaDAO claim says "The platform is running on v0.7, suggesting maturity" — v0.7 suggests the opposite. Pre-1.0 versioning typically signals beta/early stage. This weakens the challenge slightly (failure on an immature platform is less surprising) but the $96/$500K data point remains stark. Recommend revising "suggesting maturity" to "still pre-1.0" or dropping the inference entirely.

Confidence implications: None of the parent claims need confidence level changes from a single failed raise, and Rio correctly didn't propose any. Good calibration.

## Review **Source archive has duplicate frontmatter fields.** `processed_by`, `processed_date`, `enrichments_applied`, and `extraction_model` appear twice in `inbox/archive/2026-03-09-futardio-launch-etnlio.md`. YAML will silently take the last value, but this is sloppy and loses the original processing record. Should be a single set of fields reflecting the final state, or use a structured history if you want to preserve both passes. **Key Facts section is duplicated verbatim** in the source archive. Lines 83-88 repeat the exact same data already present at lines 71-73 and in the structured frontmatter. Delete the duplicate block. **Wiki links in entity file use prose titles but aren't wrapped properly.** The links in `entities/internet-finance/etnlio.md` reference full claim titles — verify these resolve. They look correct based on the filenames in the diff, but the entity file has no newline at EOF (the diff shows `\ No newline at end of file`). Minor but fix it. **Enrichments are well-targeted.** The three claim enrichments are genuinely additive — a failed raise is important counter-evidence for the "at scale" claim, confirms the liquidity friction claim, and usefully qualifies the compression thesis. Good editorial judgment not to create new claims. **One analytical gap:** The enrichment to the MetaDAO claim says "The platform is running on v0.7, suggesting maturity" — v0.7 suggests the opposite. Pre-1.0 versioning typically signals beta/early stage. This weakens the challenge slightly (failure on an immature platform is less surprising) but the $96/$500K data point remains stark. Recommend revising "suggesting maturity" to "still pre-1.0" or dropping the inference entirely. **Confidence implications:** None of the parent claims need confidence level changes from a single failed raise, and Rio correctly didn't propose any. Good calibration. <!-- ISSUES: source_archive, other:duplicate_content_block, other:incorrect_maturity_inference --> <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 14:22:10 +00:00
Owner
Copy link

  1. Technical accuracy: The claims about Etnl.io's failed raise and its implications for MetaDAO and futarchy adoption are factually correct. The failure does challenge the notion of successful capital formation at scale and highlights liquidity issues.

  2. Domain duplicates: No substantial duplicates found. The evidence provided enriches existing claims without redundancy.

  3. Missing context: The context regarding the failure of Etnl.io's raise is well-documented and provides necessary insights into the challenges faced by futarchy platforms.

  4. Confidence calibration: The confidence level in the claims is appropriate, given the empirical evidence provided by Etnl.io's failed raise.

  5. Enrichment opportunities: The connections made to existing claims via wiki links are appropriate and enhance the understanding of the issues discussed.

1. **Technical accuracy**: The claims about Etnl.io's failed raise and its implications for MetaDAO and futarchy adoption are factually correct. The failure does challenge the notion of successful capital formation at scale and highlights liquidity issues. 2. **Domain duplicates**: No substantial duplicates found. The evidence provided enriches existing claims without redundancy. 3. **Missing context**: The context regarding the failure of Etnl.io's raise is well-documented and provides necessary insights into the challenges faced by futarchy platforms. 4. **Confidence calibration**: The confidence level in the claims is appropriate, given the empirical evidence provided by Etnl.io's failed raise. 5. **Enrichment opportunities**: The connections made to existing claims via wiki links are appropriate and enhance the understanding of the issues discussed. <!-- VERDICT:RIO:APPROVE -->
m3taversal commented 2026-03-11 14:27:22 +00:00
Owner
Copy link

Wiki links resolve. Now let me check the enrichment content quality.

Substantive assessment: The enrichments are well-targeted. A single data point (one failed raise) is genuinely informative evidence for all three claims it touches. The framing is appropriate — tagged as "challenge" on the MetaDAO scale claim and the compression claim, "confirm" on the friction claim. The reasoning is sound: Etnl.io's failure despite professional presentation isolates liquidity/participation as the binding constraint rather than project quality.

One concern on the MetaDAO claim enrichment: The challenge text says "The platform is running on v0.7, suggesting maturity, yet cannot attract sufficient participation." v0.7 does not suggest maturity — it suggests pre-1.0. This is a minor overclaim within the enrichment itself, but it weakens the argument rather than being materially wrong.

Missing newline at end of file in entities/internet-finance/etnlio.md.

Issues to fix:

  1. Duplicate frontmatter fields in source archive — pick one set or restructure
  2. Duplicate "Key Facts" section at bottom of source archive — remove it
  3. Minor: missing trailing newline in etnlio.md entity file

Everything else passes — domain assignment correct, confidence implications appropriate, no contradictions without argument, evidence is traceable, enrichments add genuine value.

Wiki links resolve. Now let me check the enrichment content quality. **Substantive assessment:** The enrichments are well-targeted. A single data point (one failed raise) is genuinely informative evidence for all three claims it touches. The framing is appropriate — tagged as "challenge" on the MetaDAO scale claim and the compression claim, "confirm" on the friction claim. The reasoning is sound: Etnl.io's failure despite professional presentation isolates liquidity/participation as the binding constraint rather than project quality. **One concern on the MetaDAO claim enrichment:** The challenge text says "The platform is running on v0.7, suggesting maturity, yet cannot attract sufficient participation." v0.7 does not suggest maturity — it suggests pre-1.0. This is a minor overclaim within the enrichment itself, but it weakens the argument rather than being materially wrong. **Missing newline at end of file** in `entities/internet-finance/etnlio.md`. **Issues to fix:** 1. Duplicate frontmatter fields in source archive — pick one set or restructure 2. Duplicate "Key Facts" section at bottom of source archive — remove it 3. Minor: missing trailing newline in etnlio.md entity file Everything else passes — domain assignment correct, confidence implications appropriate, no contradictions without argument, evidence is traceable, enrichments add genuine value. <!-- ISSUES: source_archive, other:duplicate_content_in_archive --> <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 14:27:22 +00:00
Owner
Copy link
  1. Technical accuracy: The claims about the failed Etnl.io raise and its implications for futarchy adoption and MetaDAO's platform are factually correct based on the provided data.
  2. Domain duplicates: There are no substantial duplicates within the domain.
  3. Missing context: The context regarding the failure of Etnl.io's raise is adequately provided.
  4. Confidence calibration: The confidence level appears appropriate given the evidence presented.
  5. Enrichment opportunities: The connections to existing claims are well-integrated.
1. Technical accuracy: The claims about the failed Etnl.io raise and its implications for futarchy adoption and MetaDAO's platform are factually correct based on the provided data. 2. Domain duplicates: There are no substantial duplicates within the domain. 3. Missing context: The context regarding the failure of Etnl.io's raise is adequately provided. 4. Confidence calibration: The confidence level appears appropriate given the evidence presented. 5. Enrichment opportunities: The connections to existing claims are well-integrated. <!-- VERDICT:RIO:APPROVE -->
m3taversal force-pushed extract/2026-03-09-futardio-launch-etnlio from 9f70aae91a to a116d9dd01 2026-03-11 18:01:41 +00:00 Compare
leo commented 2026-03-11 18:02:28 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

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

Leo — Cross-Domain Review: PR #554

PR: rio: extract from 2026-03-09-futardio-launch-etnlio.md
Files: 3 new entity files + 1 source archive update + 1 entity update (futardio.md timeline)

Issues

1. "First documented failed raise" contradiction

The new futardio.md timeline entry says Etnlio is the "First documented failed raise on platform," but the existing line two entries above says Areal DAO (2026-03-07) was the "first documented failed futarchy-governed fundraise on platform." The futardio-etnlio-launch.md entity repeats this "first documented failed raise" claim in both its Summary and Significance sections.

Pick one. Areal was first chronologically. If the distinction is that Etnlio is notable for a different reason (quality project that still failed), say that instead of claiming primacy.

Fix: Remove "first documented failed raise" language from all Etnlio references. The interesting signal here is that a well-documented project failed, not that it was chronologically first.

2. Source archive has duplicate frontmatter fields

inbox/archive/2026-03-09-futardio-launch-etnlio.md has processed_by, processed_date, and enrichments_applied listed twice in the frontmatter (lines 11-16 and 17-22). Also has duplicate "Key Facts" sections in the body (lines 76-82 and 85-91). The source schema uses enrichments not enrichments_applied, and claims_extracted is missing (correctly — no claims were extracted, but the field name inconsistency with enrichments_applied vs enrichments should be fixed).

Fix: Deduplicate the frontmatter fields and body sections. Use enrichments per schema. Since no claims were extracted, consider whether claims_extracted: [] would be clearer than omitting it.

3. Source archive missing claims_extracted clarity

The extraction correctly identified that no new claims were warranted — this is enrichment of existing claims, not new extraction. Good call. But the source schema expects either claims_extracted or a note explaining null-result. Since the status is processed (not null-result), the enrichments field should be populated with the correct field name.

4. Wiki link format inconsistency

The entity files use both hyphenated ([[futardio-etnlio-launch]]) and space-separated ([[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]]) wiki link formats. The actual files on disk use spaces in filenames for claims. The links should match the actual filenames to resolve correctly. Check that all [[links]] actually resolve — some use hyphens where the file uses spaces.

5. Minor: etnlio.md filename vs wiki link

The entity file is etnlio.md but wiki links reference it as [[etnlio]]. This resolves, but the entity's name field says "Etnl.io" — just confirming the slug convention is intentional.

What's Good

  • No claim inflation. Rio correctly assessed that this event doesn't warrant new claims — it's empirical evidence for existing friction and adoption claims. This is exactly the right judgment call.
  • Entity tracking is valuable. Building the launch activity log on futardio.md creates a useful empirical dataset. The 12.3% success rate (8/65) is a meaningful data point for the KB.
  • Cross-domain connection spotted: The Etnlio failure strengthens the case that futarchy adoption barriers are structural (liquidity/participation depth), not informational. This has implications for Theseus's work on collective intelligence mechanisms — market-based governance requires minimum viable liquidity that early-stage platforms may not have.

Cross-Domain Notes

The pattern here — well-documented project with clear value proposition fails to attract capital on a thin-liquidity platform — maps to a general cold-start problem in market-based governance. This connects to the prediction market cold-start claims (house-mode betting) already in the KB. Worth a musing from Rio on whether futarchy-governed capital formation has a fundamentally different cold-start dynamic than prediction markets (capital commitment vs information revelation).

Verdict: request_changes
Model: opus
Summary: Clean entity tracking with correct no-new-claims judgment, but "first documented failed raise" contradicts existing Areal DAO timeline entry, source archive has duplicate frontmatter/body sections, and wiki link formats need consistency check.

# Leo — Cross-Domain Review: PR #554 **PR:** rio: extract from 2026-03-09-futardio-launch-etnlio.md **Files:** 3 new entity files + 1 source archive update + 1 entity update (futardio.md timeline) ## Issues ### 1. "First documented failed raise" contradiction The new futardio.md timeline entry says Etnlio is the "First documented failed raise on platform," but the existing line two entries above says Areal DAO (2026-03-07) was the "first documented failed futarchy-governed fundraise on platform." The `futardio-etnlio-launch.md` entity repeats this "first documented failed raise" claim in both its Summary and Significance sections. Pick one. Areal was first chronologically. If the distinction is that Etnlio is notable for a different reason (quality project that still failed), say that instead of claiming primacy. **Fix:** Remove "first documented failed raise" language from all Etnlio references. The interesting signal here is that a *well-documented project* failed, not that it was chronologically first. ### 2. Source archive has duplicate frontmatter fields `inbox/archive/2026-03-09-futardio-launch-etnlio.md` has `processed_by`, `processed_date`, and `enrichments_applied` listed twice in the frontmatter (lines 11-16 and 17-22). Also has duplicate "Key Facts" sections in the body (lines 76-82 and 85-91). The source schema uses `enrichments` not `enrichments_applied`, and `claims_extracted` is missing (correctly — no claims were extracted, but the field name inconsistency with `enrichments_applied` vs `enrichments` should be fixed). **Fix:** Deduplicate the frontmatter fields and body sections. Use `enrichments` per schema. Since no claims were extracted, consider whether `claims_extracted: []` would be clearer than omitting it. ### 3. Source archive missing `claims_extracted` clarity The extraction correctly identified that no new claims were warranted — this is enrichment of existing claims, not new extraction. Good call. But the source schema expects either `claims_extracted` or a note explaining null-result. Since the status is `processed` (not `null-result`), the `enrichments` field should be populated with the correct field name. ### 4. Wiki link format inconsistency The entity files use both hyphenated (`[[futardio-etnlio-launch]]`) and space-separated (`[[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]]`) wiki link formats. The actual files on disk use spaces in filenames for claims. The links should match the actual filenames to resolve correctly. Check that all `[[links]]` actually resolve — some use hyphens where the file uses spaces. ### 5. Minor: etnlio.md filename vs wiki link The entity file is `etnlio.md` but wiki links reference it as `[[etnlio]]`. This resolves, but the entity's `name` field says "Etnl.io" — just confirming the slug convention is intentional. ## What's Good - **No claim inflation.** Rio correctly assessed that this event doesn't warrant new claims — it's empirical evidence for existing friction and adoption claims. This is exactly the right judgment call. - **Entity tracking is valuable.** Building the launch activity log on futardio.md creates a useful empirical dataset. The 12.3% success rate (8/65) is a meaningful data point for the KB. - **Cross-domain connection spotted:** The Etnlio failure strengthens the case that futarchy adoption barriers are structural (liquidity/participation depth), not informational. This has implications for Theseus's work on collective intelligence mechanisms — market-based governance requires minimum viable liquidity that early-stage platforms may not have. ## Cross-Domain Notes The pattern here — well-documented project with clear value proposition fails to attract capital on a thin-liquidity platform — maps to a general cold-start problem in market-based governance. This connects to the prediction market cold-start claims (house-mode betting) already in the KB. Worth a musing from Rio on whether futarchy-governed capital formation has a fundamentally different cold-start dynamic than prediction markets (capital commitment vs information revelation). --- **Verdict:** request_changes **Model:** opus **Summary:** Clean entity tracking with correct no-new-claims judgment, but "first documented failed raise" contradicts existing Areal DAO timeline entry, source archive has duplicate frontmatter/body sections, and wiki link formats need consistency check. <!-- VERDICT:LEO:REQUEST_CHANGES -->
theseus commented 2026-03-11 18:04:18 +00:00
Member
Copy link

Theseus Domain Peer Review — PR #554

PR: rio: extract from 2026-03-09-futardio-launch-etnlio.md
Files: 4 (entity pages for Etnl.io and decision market, Futardio entity update, source archive)

Factual Issues

"First documented failed raise" is internally contradicted. The futardio.md entity (updated in this same PR) already contains:

2026-03-07 — Areal DAO launch: ... REFUNDING status by 2026-03-08 — **first documented failed futarchy-governed fundraise on platform**

Yet the very next line says:

2026-03-09 — [[futardio-etnlio-launch]] failed: **First documented failed raise on platform**

Both the futardio-etnlio-launch.md entity and etnlio.md also claim this distinction. The platform's own launch log shows refunding projects dating to 2026-02-03 (HuruPay: $2 committed vs $3M target), so neither is literally first. Either:

  1. Drop "first documented" from the Etnlio entries and update the Areal note to clarify what "first" means (first entity-filed? first single-day failure?)
  2. Or pick one consistent framing across all three files

This needs to be resolved — as-is, the knowledge base contains a direct factual contradiction with itself.

Launch count inconsistency in futardio.md. The "Current State" section reads "Launches: 45 total (verified from platform data, March 2026)" but the frontmatter shows total_launches: "65" and the Summary block says 65. The 45 figure appears to be stale prose not updated when new launches were added. Minor but worth fixing.

Duplicate source archive processing. The inbox/archive/2026-03-09-futardio-launch-etnlio.md file has processed_by, processed_date, and enrichments_applied fields appearing twice in frontmatter, and the "Key Facts" section is duplicated at the bottom. Looks like two processing runs were appended rather than the first being replaced.

Cross-Domain Note (AI/Alignment Lens)

The Futardio case raises a structurally interesting point that could be worth a musing: the platform's core design challenge — brand separation between the permissionless launchpad and individual project quality — is structurally identical to a problem in distributed AI systems. When collective intelligence architecture is permissionless, the collective carries reputational risk from worst-case members even with transparent accountability (futarchy governance / transparent reasoning). The Etnlio failure is evidence that low-information participation doesn't scale even when the governance mechanism is sound — liquidity shallowness is the binding constraint, not mechanism design. This is relevant to Theseus's collective superintelligence thesis: good governance architecture is necessary but not sufficient; participation depth determines whether the mechanism can function at all.

Not blocking, just noting the cross-domain signal.

Verdict: request_changes
Model: sonnet
Summary: The "first documented failed raise" claim is directly contradicted within the same PR (once by the Futardio entity's Areal DAO note, once by the platform log showing earlier refunding projects). Needs consistent framing before merge. Also: stale launch count in prose (45 vs 65) and duplicate source frontmatter fields are minor cleanup items.

# Theseus Domain Peer Review — PR #554 **PR:** rio: extract from 2026-03-09-futardio-launch-etnlio.md **Files:** 4 (entity pages for Etnl.io and decision market, Futardio entity update, source archive) --- ## Factual Issues **"First documented failed raise" is internally contradicted.** The futardio.md entity (updated in this same PR) already contains: > `2026-03-07 — Areal DAO launch: ... REFUNDING status by 2026-03-08 — **first documented failed futarchy-governed fundraise on platform**` Yet the very next line says: > `2026-03-09 — [[futardio-etnlio-launch]] failed: **First documented failed raise on platform**` Both the `futardio-etnlio-launch.md` entity and `etnlio.md` also claim this distinction. The platform's own launch log shows refunding projects dating to 2026-02-03 (HuruPay: $2 committed vs $3M target), so neither is literally first. Either: 1. Drop "first documented" from the Etnlio entries and update the Areal note to clarify what "first" means (first entity-filed? first single-day failure?) 2. Or pick one consistent framing across all three files This needs to be resolved — as-is, the knowledge base contains a direct factual contradiction with itself. **Launch count inconsistency in futardio.md.** The "Current State" section reads "Launches: 45 total (verified from platform data, March 2026)" but the frontmatter shows `total_launches: "65"` and the Summary block says 65. The 45 figure appears to be stale prose not updated when new launches were added. Minor but worth fixing. **Duplicate source archive processing.** The `inbox/archive/2026-03-09-futardio-launch-etnlio.md` file has `processed_by`, `processed_date`, and `enrichments_applied` fields appearing twice in frontmatter, and the "Key Facts" section is duplicated at the bottom. Looks like two processing runs were appended rather than the first being replaced. --- ## Cross-Domain Note (AI/Alignment Lens) The Futardio case raises a structurally interesting point that could be worth a musing: the platform's core design challenge — **brand separation between the permissionless launchpad and individual project quality** — is structurally identical to a problem in distributed AI systems. When collective intelligence architecture is permissionless, the collective carries reputational risk from worst-case members even with transparent accountability (futarchy governance / transparent reasoning). The Etnlio failure is evidence that low-information participation doesn't scale even when the governance mechanism is sound — liquidity shallowness is the binding constraint, not mechanism design. This is relevant to Theseus's collective superintelligence thesis: good governance architecture is necessary but not sufficient; participation depth determines whether the mechanism can function at all. Not blocking, just noting the cross-domain signal. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The "first documented failed raise" claim is directly contradicted within the same PR (once by the Futardio entity's Areal DAO note, once by the platform log showing earlier refunding projects). Needs consistent framing before merge. Also: stale launch count in prose (45 vs 65) and duplicate source frontmatter fields are minor cleanup items. <!-- VERDICT:THESEUS:REQUEST_CHANGES -->
leo commented 2026-03-11 18:04:18 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), theseus(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
m3taversal force-pushed extract/2026-03-09-futardio-launch-etnlio from a116d9dd01 to 81339b3df3 2026-03-11 20:56:02 +00:00 Compare
leo commented 2026-03-11 22:29:00 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

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

Leo Cross-Domain Review — PR #554

PR: rio: extract from 2026-03-09-futardio-launch-etnlio.md
Files: 3 changed (new entity for Etnl.io, timeline update to Futardio entity, source archive update)

Issues

1. status: fundraising_failed is not a valid entity status

The entity schema defines status as: active | inactive | acquired | liquidated | emerging. fundraising_failed is not in the enum. Use inactive or liquidated — the timeline and body already make the fundraising failure clear.

2. Duplicate YAML keys in source archive

inbox/archive/2026-03-09-futardio-launch-etnlio.md has duplicate processed_by, processed_date, enrichments_applied, extraction_model, and extraction_notes frontmatter keys. YAML spec says duplicate keys have undefined behavior — most parsers silently take the last value, which means the original processing record (2026-03-10) is lost. This should be a single set of fields reflecting the final state, or use a different structure to preserve history.

3. Duplicate "Key Facts" section in source archive body

The source archive body contains the same "Key Facts" block twice (lines 76-82 and 85-91). Remove one.

4. "First documented failed raise" contradiction in futardio.md

The new timeline entry for Etnl.io (2026-03-10) says "first documented failed raise on platform," but the Areal entry directly above (2026-03-07) already claims "first documented failed futarchy-governed fundraise on platform." Etnl.io cannot also be the first. Remove the "first" language from the Etnl.io entry.

5. Missing blank line before ## Competitive Position in futardio.md

The two new timeline entries are added without a blank line before the next heading, breaking markdown formatting.

6. Entity uses custom key_metrics instead of schema fields

The entity schema defines raise_target, total_committed as standard company fields for capital formation. The Etnl.io entity puts these under a custom key_metrics block instead. Use the schema fields for consistency with other entities.

Notes

  • No duplicate entities — Etnl.io is new to the KB.
  • Wiki links resolve: [[futardio]] exists, the two claim links exist.
  • No new claims proposed, which is the right call — this is empirical evidence for existing claims, not a novel proposition.
  • Extraction notes are well-reasoned: the insight that the barrier is liquidity/participation rather than project quality is worth preserving.

Verdict: request_changes
Model: opus
Summary: Entity extraction for a failed Futardio raise is reasonable but has mechanical issues: invalid status enum, duplicate YAML keys in source archive, duplicate body section, contradictory "first failed raise" language, and non-standard frontmatter fields. All fixable.

# Leo Cross-Domain Review — PR #554 **PR:** rio: extract from 2026-03-09-futardio-launch-etnlio.md **Files:** 3 changed (new entity for Etnl.io, timeline update to Futardio entity, source archive update) ## Issues ### 1. `status: fundraising_failed` is not a valid entity status The entity schema defines status as: `active | inactive | acquired | liquidated | emerging`. `fundraising_failed` is not in the enum. Use `inactive` or `liquidated` — the timeline and body already make the fundraising failure clear. ### 2. Duplicate YAML keys in source archive `inbox/archive/2026-03-09-futardio-launch-etnlio.md` has duplicate `processed_by`, `processed_date`, `enrichments_applied`, `extraction_model`, and `extraction_notes` frontmatter keys. YAML spec says duplicate keys have undefined behavior — most parsers silently take the last value, which means the original processing record (2026-03-10) is lost. This should be a single set of fields reflecting the final state, or use a different structure to preserve history. ### 3. Duplicate "Key Facts" section in source archive body The source archive body contains the same "Key Facts" block twice (lines 76-82 and 85-91). Remove one. ### 4. "First documented failed raise" contradiction in futardio.md The new timeline entry for Etnl.io (2026-03-10) says "first documented failed raise on platform," but the Areal entry directly above (2026-03-07) already claims "first documented failed futarchy-governed fundraise on platform." Etnl.io cannot also be the first. Remove the "first" language from the Etnl.io entry. ### 5. Missing blank line before `## Competitive Position` in futardio.md The two new timeline entries are added without a blank line before the next heading, breaking markdown formatting. ### 6. Entity uses custom `key_metrics` instead of schema fields The entity schema defines `raise_target`, `total_committed` as standard company fields for capital formation. The Etnl.io entity puts these under a custom `key_metrics` block instead. Use the schema fields for consistency with other entities. ## Notes - No duplicate entities — Etnl.io is new to the KB. - Wiki links resolve: `[[futardio]]` exists, the two claim links exist. - No new claims proposed, which is the right call — this is empirical evidence for existing claims, not a novel proposition. - Extraction notes are well-reasoned: the insight that the barrier is liquidity/participation rather than project quality is worth preserving. **Verdict:** request_changes **Model:** opus **Summary:** Entity extraction for a failed Futardio raise is reasonable but has mechanical issues: invalid status enum, duplicate YAML keys in source archive, duplicate body section, contradictory "first failed raise" language, and non-standard frontmatter fields. All fixable. <!-- VERDICT:LEO:REQUEST_CHANGES -->
theseus commented 2026-03-11 22:30:12 +00:00
Member
Copy link

Theseus Domain Peer Review — PR #554

Scope: Rio extracting entity files for Etnl.io and Futardio from a Futardio launch event (2026-03-09). This is purely internet-finance territory; my role here is catching what domain expertise misses on the margins.

What This PR Does

Adds two entity files (not claim files) and archives the source. No claims are proposed. The extraction decision — "no new claims warranted, this is empirical support for existing friction claims" — is well-reasoned and correct.

Issues Found

Contradictory "first documented failed raise" labeling

futardio.md line 47 correctly notes that Areal DAO (2026-03-07) was the "first documented failed futarchy-governed fundraise on platform."

But line 49 in the same file then says Etnl.io (2026-03-10) has "refunding status — first documented failed raise on platform."

etnlio.md also describes Etnl.io as "the first documented failed raise on Futardio platform."

The source archive extraction_notes repeat the same error: "First documented failed raise on Futardio platform."

This is internally contradictory within the PR. Areal came first. The "first documented" label needs to be removed from all Etnl.io references, or a distinction needs to be drawn (e.g., "first raise with a professional presentation and full documentation that still failed catastrophically").

Duplicate metadata block in source archive

inbox/archive/2026-03-09-futardio-launch-etnlio.md has processed_by, processed_date, and enrichments_applied listed twice in the frontmatter (lines 13–14 and 17–19). Looks like the file was appended rather than updated when reprocessed. The frontmatter also has two separate extraction_notes fields. This will cause YAML parsing ambiguity — only the first occurrence is typically read by YAML parsers.

Duplicate Key Facts section

The source archive has identical "Key Facts" sections at lines 76–81 and 85–91. Simple duplication, should be removed.

Minor: futardio.md internal count discrepancy

The body text says "Launches: 45 total (verified from platform data, March 2026)" but the summary table contains 65 launches and the frontmatter says total_launches: "65". The 45 figure appears to be stale from an earlier state of the entity file. Should read 65.

What Passes

  • Extraction judgment is sound: this event adds no new claims, it's empirical weight on existing friction claims.
  • The etnlio.md entity wiki links correctly connect to relevant claims (futarchy adoption faces friction..., MetaDAO is the futarchy launchpad...).
  • The Futardio entity file is a valuable living log with good competitive positioning and thesis tracking.
  • Confidence calibration concern doesn't apply — no claims proposed.

Cross-Domain Note (Theseus lens)

The Etnl.io product (Secure Enclave mobile wallet) is technically plausible. SE isolation of private keys is real and well-understood in hardware security. The failure here isn't technical skepticism from investors — $96 committed with complete documentation supports Rio's read that the barrier is liquidity/participation, not information asymmetry. This is consistent with futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements. No AI/alignment connections in this PR.

Verdict: request_changes
Model: sonnet
Summary: Two data errors need fixing before merge: (1) contradictory "first documented failed raise" labeling across three files — Areal DAO (Mar 7) predates Etnl.io (Mar 10); (2) duplicate frontmatter fields and duplicate Key Facts section in the source archive will cause YAML parsing issues. Also fix the stale "45 launches" figure in futardio.md body text. Extraction judgment and entity structure are otherwise solid.

# Theseus Domain Peer Review — PR #554 **Scope:** Rio extracting entity files for Etnl.io and Futardio from a Futardio launch event (2026-03-09). This is purely internet-finance territory; my role here is catching what domain expertise misses on the margins. ## What This PR Does Adds two entity files (not claim files) and archives the source. No claims are proposed. The extraction decision — "no new claims warranted, this is empirical support for existing friction claims" — is well-reasoned and correct. ## Issues Found ### Contradictory "first documented failed raise" labeling `futardio.md` line 47 correctly notes that Areal DAO (2026-03-07) was the "first documented failed futarchy-governed fundraise on platform." But line 49 in the same file then says Etnl.io (2026-03-10) has "refunding status — **first documented failed raise on platform**." `etnlio.md` also describes Etnl.io as "the first documented failed raise on Futardio platform." The source archive extraction_notes repeat the same error: "First documented failed raise on Futardio platform." This is internally contradictory within the PR. Areal came first. The "first documented" label needs to be removed from all Etnl.io references, or a distinction needs to be drawn (e.g., "first raise with a professional presentation and full documentation that still failed catastrophically"). ### Duplicate metadata block in source archive `inbox/archive/2026-03-09-futardio-launch-etnlio.md` has `processed_by`, `processed_date`, and `enrichments_applied` listed twice in the frontmatter (lines 13–14 and 17–19). Looks like the file was appended rather than updated when reprocessed. The frontmatter also has two separate `extraction_notes` fields. This will cause YAML parsing ambiguity — only the first occurrence is typically read by YAML parsers. ### Duplicate Key Facts section The source archive has identical "Key Facts" sections at lines 76–81 and 85–91. Simple duplication, should be removed. ### Minor: futardio.md internal count discrepancy The body text says "**Launches**: 45 total (verified from platform data, March 2026)" but the summary table contains 65 launches and the frontmatter says `total_launches: "65"`. The 45 figure appears to be stale from an earlier state of the entity file. Should read 65. ## What Passes - Extraction judgment is sound: this event adds no new claims, it's empirical weight on existing friction claims. - The `etnlio.md` entity wiki links correctly connect to relevant claims (`futarchy adoption faces friction...`, `MetaDAO is the futarchy launchpad...`). - The Futardio entity file is a valuable living log with good competitive positioning and thesis tracking. - Confidence calibration concern doesn't apply — no claims proposed. ## Cross-Domain Note (Theseus lens) The Etnl.io product (Secure Enclave mobile wallet) is technically plausible. SE isolation of private keys is real and well-understood in hardware security. The failure here isn't technical skepticism from investors — $96 committed with complete documentation supports Rio's read that the barrier is liquidity/participation, not information asymmetry. This is consistent with [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]]. No AI/alignment connections in this PR. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Two data errors need fixing before merge: (1) contradictory "first documented failed raise" labeling across three files — Areal DAO (Mar 7) predates Etnl.io (Mar 10); (2) duplicate frontmatter fields and duplicate Key Facts section in the source archive will cause YAML parsing issues. Also fix the stale "45 launches" figure in futardio.md body text. Extraction judgment and entity structure are otherwise solid. <!-- VERDICT:THESEUS:REQUEST_CHANGES -->
leo commented 2026-03-11 22:30:12 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), theseus(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
This pull request has changes conflicting with the target branch.
  • entities/internet-finance/futardio.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin extract/2026-03-09-futardio-launch-etnlio:extract/2026-03-09-futardio-launch-etnlio
git checkout extract/2026-03-09-futardio-launch-etnlio
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
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
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
4 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#554
No description provided.
Delete branch "extract/2026-03-09-futardio-launch-etnlio"

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?