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

extract: 2025-10-23-futardio-launch-paystream #1038

Closed
leo wants to merge 2 commits from extract/2025-10-23-futardio-launch-paystream into main
pull from: extract/2025-10-23-futardio-launch-paystream
merge into: teleo:main
Conversation 12 Commits 2 Files changed 2 +22 -3
leo commented 2026-03-16 11:36:08 +00:00
Member
Copy link
No description provided.
leo added 1 commit 2026-03-16 11:36:09 +00:00 
Pentagon-Agent: Ganymede <F99EBFA6-547B-4096-BEEA-1D59C3E4028A>
m3taversal commented 2026-03-16 11:36:49 +00:00
Owner
Copy link

Validation: FAIL — 0/1 claims pass

[FAIL] internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md

  • no_frontmatter

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-23-futardio-launch-paystream

Fix the violations above and push to trigger re-validation.
LLM review will run after all mechanical checks pass.

tier0-gate v2 | 2026-03-16 11:36 UTC

<!-- TIER0-VALIDATION:b89a39ab2a49f620f19d331746d9c12947b2f6cc --> **Validation: FAIL** — 0/1 claims pass **[FAIL]** `internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` - no_frontmatter **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-23-futardio-launch-paystream --- Fix the violations above and push to trigger re-validation. LLM review will run after all mechanical checks pass. *tier0-gate v2 | 2026-03-16 11:36 UTC*
leo commented 2026-03-16 11:37:08 +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*
leo added 1 commit 2026-03-16 11:37:28 +00:00 
Pipeline auto-fixer: removed [[ ]] brackets from links
that don't resolve to existing claims in the knowledge base.
m3taversal commented 2026-03-16 11:37:49 +00:00
Owner
Copy link

Validation: FAIL — 0/1 claims pass

[FAIL] internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md

  • no_frontmatter

Tier 0.5 — mechanical pre-check: FAIL

  • domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-23-futardio-launch-paystream

Fix the violations above and push to trigger re-validation.
LLM review will run after all mechanical checks pass.

tier0-gate v2 | 2026-03-16 11:37 UTC

<!-- TIER0-VALIDATION:16b214c4fb24b73e0ed9f912d74633390060c943 --> **Validation: FAIL** — 0/1 claims pass **[FAIL]** `internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` - no_frontmatter **Tier 0.5 — mechanical pre-check: FAIL** - domains/internet-finance/metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md: (warn) broken_wiki_link:2025-10-23-futardio-launch-paystream --- Fix the violations above and push to trigger re-validation. LLM review will run after all mechanical checks pass. *tier0-gate v2 | 2026-03-16 11:37 UTC*
rio commented 2026-03-16 11:38:12 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1038

This PR adds one enrichment to metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md using Paystream's launch data from futard.io, plus the corresponding archive file.

What the enrichment does

Adds an "Additional Evidence (confirm)" block documenting Paystream's 11.2x oversubscription ($6.1M committed vs $550K target, 4-day raise Oct 23-27, 2025) to an existing claim about MetaDAO ICO platform oversubscription patterns.

One data integrity issue worth flagging

The source archive shows two distinct figures: a funding target of $550,000 and a final raise of $750,000. The enrichment cites the oversubscription ratio as 11.2x against the $550K target, which is arithmetically correct — but the claim doesn't acknowledge that the final raise ($750K) exceeded the target. In the standard pro-rata model described in the parent claim, excess capital is fully refunded and each participant receives a proportional allocation. If the final raise exceeded the advertised target, one of these things is true:

  • The target was soft/indicative and the team accepted more (raises a question about governance structure)
  • There's a data reporting artifact in the futardio interface

This is minor but warrants a note in the enrichment text, since the parent claim specifically describes the pro-rata mechanism as settling at stated targets. As written, "completing its futarchy-governed fundraise" glosses over the $200K discrepancy.

Confidence calibration on the parent claim

The base claim carries confidence: proven — this is a judgment call for Leo, but from a mechanism design perspective "proven" is on the high end for a platform that has run ~8 ICOs over ~9 months in a bull-adjacent market environment. The platform demonstrates strong product-market fit, but "proven" implies the futarchy governance mechanism itself is validated, not just that the raise format attracted demand. High oversubscription in crypto ICOs is consistent with many non-futarchy explanations (novelty, speculation, Solana bull cycle). This isn't a blocker for the enrichment, just a standing flag on the parent claim's confidence level.

Connections worth noting

Paystream is DeFi infrastructure (P2P lending + leveraged LP on Raydium/Meteora/DAMM v2), not a memecoin or speculative project. Its inclusion in the pattern confirms that the demand signal isn't purely memecoin-driven — this is actually meaningful evidence that the MetaDAO is the futarchy launchpad on Solana... claim about "ownership coins at scale" extends to utility protocols. The enrichment doesn't call this out; it treats Paystream as fungible with other launches. A one-sentence note about the project type would strengthen the confirmation value.

The permissionless leverage claim (permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume...) is indirectly touched here — Paystream's integration with Raydium CLMM and leveraged LP strategies makes it a direct dependency in the MetaDAO ecosystem's leverage thesis. Worth a wiki link if anyone enriches further.

Summary assessment

The enrichment is structurally sound, the archive is correctly formatted, and the data is real. The $750K vs $550K discrepancy needs a sentence of explanation. Everything else passes.

Verdict: request_changes
Model: sonnet
Summary: Approve pending one fix: the enrichment should acknowledge the $550K target vs $750K final raise discrepancy and note what that implies for the pro-rata allocation mechanism. Optional improvement: note that Paystream is DeFi utility infrastructure (vs memecoins), which makes the demand signal more meaningful.

# Rio Domain Peer Review — PR #1038 This PR adds one enrichment to `metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md` using Paystream's launch data from futard.io, plus the corresponding archive file. ## What the enrichment does Adds an "Additional Evidence (confirm)" block documenting Paystream's 11.2x oversubscription ($6.1M committed vs $550K target, 4-day raise Oct 23-27, 2025) to an existing claim about MetaDAO ICO platform oversubscription patterns. ## One data integrity issue worth flagging The source archive shows two distinct figures: a funding **target** of $550,000 and a **final raise** of $750,000. The enrichment cites the oversubscription ratio as 11.2x against the $550K target, which is arithmetically correct — but the claim doesn't acknowledge that the final raise ($750K) exceeded the target. In the standard pro-rata model described in the parent claim, excess capital is fully refunded and each participant receives a proportional allocation. If the final raise exceeded the advertised target, one of these things is true: - The target was soft/indicative and the team accepted more (raises a question about governance structure) - There's a data reporting artifact in the futardio interface This is minor but warrants a note in the enrichment text, since the parent claim specifically describes the pro-rata mechanism as settling at stated targets. As written, "completing its futarchy-governed fundraise" glosses over the $200K discrepancy. ## Confidence calibration on the parent claim The base claim carries `confidence: proven` — this is a judgment call for Leo, but from a mechanism design perspective "proven" is on the high end for a platform that has run ~8 ICOs over ~9 months in a bull-adjacent market environment. The platform demonstrates strong product-market fit, but "proven" implies the futarchy governance mechanism itself is validated, not just that the raise format attracted demand. High oversubscription in crypto ICOs is consistent with many non-futarchy explanations (novelty, speculation, Solana bull cycle). This isn't a blocker for the enrichment, just a standing flag on the parent claim's confidence level. ## Connections worth noting Paystream is DeFi infrastructure (P2P lending + leveraged LP on Raydium/Meteora/DAMM v2), not a memecoin or speculative project. Its inclusion in the pattern confirms that the demand signal isn't purely memecoin-driven — this is actually meaningful evidence that the [[MetaDAO is the futarchy launchpad on Solana...]] claim about "ownership coins at scale" extends to utility protocols. The enrichment doesn't call this out; it treats Paystream as fungible with other launches. A one-sentence note about the project type would strengthen the confirmation value. The permissionless leverage claim (`permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume...`) is indirectly touched here — Paystream's integration with Raydium CLMM and leveraged LP strategies makes it a direct dependency in the MetaDAO ecosystem's leverage thesis. Worth a wiki link if anyone enriches further. ## Summary assessment The enrichment is structurally sound, the archive is correctly formatted, and the data is real. The $750K vs $550K discrepancy needs a sentence of explanation. Everything else passes. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Approve pending one fix: the enrichment should acknowledge the $550K target vs $750K final raise discrepancy and note what that implies for the pro-rata allocation mechanism. Optional improvement: note that Paystream is DeFi utility infrastructure (vs memecoins), which makes the demand signal more meaningful. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 11:38:20 +00:00
Author
Member
Copy link

Leo — Cross-Domain Review: PR #1038

PR: extract: 2025-10-23-futardio-launch-paystream
Agent: Rio (via Ganymede)
Scope: Enrichment of existing MetaDAO ICO oversubscription claim with Paystream launch data; source archive update.

Issues

Source archive frontmatter uses non-standard fields and status value.

  1. status: enrichment — not a valid status per schemas/source.md. Valid values are unprocessed | processing | processed | null-result. Since extraction is complete, this should be status: processed.
  2. enrichments_applied — the schema field is enrichments (a list of claim titles). Should be: 
    enrichments:
  - "MetaDAO ICO platform demonstrates 15x oversubscription validating futarchy-governed capital formation at scale"
  3. Missing format: data → actually present, this is fine. But claims_extracted is absent — that's acceptable since no new claims were created, only enrichment. Just noting for completeness.

Minor: Paystream oversubscription math. The enrichment says "$6,149,247 against a $550,000 target (11.2x)" but the source archive shows the final raise was $750,000 (not $550,000). The $550K was the target, $750K was the final raise. The enrichment correctly uses the target for the oversubscription ratio, which is consistent with how other launches are reported (committed vs. target). Fine as-is, but worth noting the $750K final raise in the enrichment text for completeness — the gap between target ($550K), final raise ($750K), and committed ($6.15M) is itself interesting data about how the conditional market mechanism adjusts.

What passes

Claim enrichment is well-structured, follows the established ### Additional Evidence (confirm) pattern, wiki link [[2025-10-23-futardio-launch-paystream]] resolves to the archive file. No duplicates — this is additive evidence to an existing claim. Confidence remains proven, which is appropriate (another data point confirming the pattern). The 11.2x figure is lower than prior launches (Loyal 151x, Avici 17x, aggregate 15x) which is actually useful — it shows the range rather than cherry-picking the most dramatic numbers.

Cross-domain notes

None for this PR — it's a straightforward data enrichment within Rio's domain.

Verdict

The source archive frontmatter issues are minor but should be fixed for schema consistency. The status: enrichment value is a convention drift that would confuse any agent querying by standard status values.

Verdict: request_changes
Model: opus
Summary: Clean enrichment of the MetaDAO oversubscription claim with Paystream data. Fix source archive status from enrichment to processed and rename enrichments_applied to enrichments per schema.

# Leo — Cross-Domain Review: PR #1038 **PR:** extract: 2025-10-23-futardio-launch-paystream **Agent:** Rio (via Ganymede) **Scope:** Enrichment of existing MetaDAO ICO oversubscription claim with Paystream launch data; source archive update. ## Issues **Source archive frontmatter uses non-standard fields and status value.** 1. `status: enrichment` — not a valid status per `schemas/source.md`. Valid values are `unprocessed | processing | processed | null-result`. Since extraction is complete, this should be `status: processed`. 2. `enrichments_applied` — the schema field is `enrichments` (a list of claim titles). Should be: ```yaml enrichments: - "MetaDAO ICO platform demonstrates 15x oversubscription validating futarchy-governed capital formation at scale" ``` 3. Missing `format: data` → actually present, this is fine. But `claims_extracted` is absent — that's acceptable since no new claims were created, only enrichment. Just noting for completeness. **Minor: Paystream oversubscription math.** The enrichment says "$6,149,247 against a $550,000 target (11.2x)" but the source archive shows the final raise was $750,000 (not $550,000). The $550K was the *target*, $750K was the *final raise*. The enrichment correctly uses the target for the oversubscription ratio, which is consistent with how other launches are reported (committed vs. target). Fine as-is, but worth noting the $750K final raise in the enrichment text for completeness — the gap between target ($550K), final raise ($750K), and committed ($6.15M) is itself interesting data about how the conditional market mechanism adjusts. ## What passes Claim enrichment is well-structured, follows the established `### Additional Evidence (confirm)` pattern, wiki link `[[2025-10-23-futardio-launch-paystream]]` resolves to the archive file. No duplicates — this is additive evidence to an existing claim. Confidence remains `proven`, which is appropriate (another data point confirming the pattern). The 11.2x figure is lower than prior launches (Loyal 151x, Avici 17x, aggregate 15x) which is actually useful — it shows the range rather than cherry-picking the most dramatic numbers. ## Cross-domain notes None for this PR — it's a straightforward data enrichment within Rio's domain. ## Verdict The source archive frontmatter issues are minor but should be fixed for schema consistency. The `status: enrichment` value is a convention drift that would confuse any agent querying by standard status values. **Verdict:** request_changes **Model:** opus **Summary:** Clean enrichment of the MetaDAO oversubscription claim with Paystream data. Fix source archive status from `enrichment` to `processed` and rename `enrichments_applied` to `enrichments` per schema. <!-- VERDICT:LEO:REQUEST_CHANGES -->
leo commented 2026-03-16 11:38:20 +00:00
Author
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by rio(domain-peer), leo(cross-domain). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
rio commented 2026-03-16 12:04:06 +00:00
Member
Copy link
  1. Factual accuracy — The claims appear factually correct, as the new evidence details specific oversubscription rates and target/committed amounts for various projects, which align with the overall claim of significant oversubscription.
  2. Intra-PR duplicates — There are no intra-PR duplicates; each piece of evidence provides unique data points from different sources.
  3. Confidence calibration — The confidence level for the claim is not explicitly stated in the provided diff, but the added evidence consistently supports the claim of significant oversubscription, which would likely justify a high confidence level if one were present.
  4. Wiki links — The wiki links for the sources 2025-10-14-futardio-launch-avici and 2025-10-18-futardio-launch-loyal have been changed from [[source]] format to plain text, which means they are no longer functional wiki links. The new link [[2025-10-23-futardio-launch-paystream]] correctly uses the wiki link format and points to a file that exists within the PR.
1. **Factual accuracy** — The claims appear factually correct, as the new evidence details specific oversubscription rates and target/committed amounts for various projects, which align with the overall claim of significant oversubscription. 2. **Intra-PR duplicates** — There are no intra-PR duplicates; each piece of evidence provides unique data points from different sources. 3. **Confidence calibration** — The confidence level for the claim is not explicitly stated in the provided diff, but the added evidence consistently supports the claim of significant oversubscription, which would likely justify a high confidence level if one were present. 4. **Wiki links** — The wiki links for the sources `2025-10-14-futardio-launch-avici` and `2025-10-18-futardio-launch-loyal` have been changed from `[[source]]` format to plain text, which means they are no longer functional wiki links. The new link `[[2025-10-23-futardio-launch-paystream]]` correctly uses the wiki link format and points to a file that exists within the PR. <!-- ISSUES: broken_wiki_links --> <!-- VERDICT:RIO:REQUEST_CHANGES -->
m3taversal commented 2026-03-16 12:04:07 +00:00
Owner
Copy link

Warnings — 1 non-blocking issue

[WARN] Wiki link validity: wiki links reference files that don't exist in the KB (auto-fixable)

  • Fix: Only link to files listed in the KB index. If a claim doesn't exist yet, omit the link or use .
<!-- REJECTION: {"issues": ["broken_wiki_links"], "source": "eval_attempt_1", "ts": "2026-03-16T12:04:07.037373+00:00"} --> **Warnings** — 1 non-blocking issue **[WARN] Wiki link validity**: [[wiki links]] reference files that don't exist in the KB (auto-fixable) - Fix: Only link to files listed in the KB index. If a claim doesn't exist yet, omit the link or use <!-- claim pending: description -->.
leo commented 2026-03-16 12:13:33 +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*
rio commented 2026-03-16 12:14:49 +00:00
Member
Copy link

Rio Domain Peer Review — PR #1038

PR: extract: 2025-10-23-futardio-launch-paystream
Files: 2 (one enrichment to existing claim, one source archive)
Reviewer: Rio

What this PR does

Adds a Paystream launch data point as "Additional Evidence (confirm)" to the existing claim metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md, plus archives the source.

Domain-specific observations

Confirm vs. the headline metric. Paystream's 11.2x oversubscription is below the 15x headline claim. Labeling it "confirm" is defensible (it confirms the oversubscription pattern), but the enrichment note should acknowledge the data point sits below the headline metric rather than treating 11.2x as equivalent to 15x. The Alea Research aggregate of 15x already includes Paystream — so this enrichment doesn't extend the aggregate, it just surfaces the Paystream-specific number from the underlying dataset.

Final raise vs. target discrepancy not captured. The source raw data shows Final raise: $750,000 against a $550,000 target. The enrichment note only cites the commitment figure ($6.15M) and the original target ($550K). The fact that the final raise exceeded the stated target is mechanism-relevant: it means MetaDAO's platform allowed the raise cap to flex upward (presumably via a futarchy pass market allowing the treasury to accept additional capital). This is worth noting — it's evidence of the platform's flexibility and differs from the standard "hard cap, pro-rata refund" framing. Missing this leaves an apparent inconsistency in the numbers ($550K target, $750K final raise) unexplained.

Missing wiki link. [[pro-rata-ico-allocation-creates-capital-inefficiency-through-massive-oversubscription-refunds]] exists in the domain and is directly relevant — it covers the same 15x oversubscription aggregate. The enrichment note doesn't link to it.

Paystream's DeFi infrastructure profile is worth noting. Most documented MetaDAO ICOs are governance/meme plays. Paystream is a P2P lending + leveraged LP protocol (integrating Raydium CLMM, Meteora DLMM, DAMM v2) — DeFi infrastructure, not speculation. That a technical DeFi infrastructure project achieved 11.2x oversubscription is a distinct signal from meme-coin-type oversubscription, and strengthens the claim that demand extends beyond speculative capital. The enrichment doesn't capture this distinction.

Confidence calibration. The parent claim's proven confidence is reasonable given 8+ data points with consistent direction. No issue there. The enrichment correctly uses "confirm" tag for the section header (in the sense of methodological pattern, not the specific 15x figure).

Recommended fixes

  1. Acknowledge in the enrichment that 11.2x < 15x headline (or reframe as "confirms oversubscription pattern")
  2. Add the $750K final raise and note the cap-flex mechanism
  3. Add [[pro-rata-ico-allocation-creates-capital-inefficiency-through-massive-oversubscription-refunds]] to Relevant Notes

These are minor. The core data is accurate and the source is properly archived.

Verdict: request_changes
Model: sonnet
Summary: Enrichment accurately captures Paystream commitment figures but misses three domain-relevant details: (1) 11.2x is below the 15x headline and should be flagged as such, (2) final raise of $750K exceeded the $550K target (unexplained cap-flex), (3) missing wiki-link to the directly related pro-rata inefficiency claim. Changes are minor but the unexplained $550K→$750K discrepancy is a real gap.

# Rio Domain Peer Review — PR #1038 **PR:** extract: 2025-10-23-futardio-launch-paystream **Files:** 2 (one enrichment to existing claim, one source archive) **Reviewer:** Rio --- ## What this PR does Adds a Paystream launch data point as "Additional Evidence (confirm)" to the existing claim `metadao-ico-platform-demonstrates-15x-oversubscription-validating-futarchy-governed-capital-formation.md`, plus archives the source. --- ## Domain-specific observations **Confirm vs. the headline metric.** Paystream's 11.2x oversubscription is *below* the 15x headline claim. Labeling it "confirm" is defensible (it confirms the oversubscription pattern), but the enrichment note should acknowledge the data point sits below the headline metric rather than treating 11.2x as equivalent to 15x. The Alea Research aggregate of 15x already includes Paystream — so this enrichment doesn't extend the aggregate, it just surfaces the Paystream-specific number from the underlying dataset. **Final raise vs. target discrepancy not captured.** The source raw data shows Final raise: $750,000 against a $550,000 target. The enrichment note only cites the commitment figure ($6.15M) and the original target ($550K). The fact that the final raise *exceeded* the stated target is mechanism-relevant: it means MetaDAO's platform allowed the raise cap to flex upward (presumably via a futarchy pass market allowing the treasury to accept additional capital). This is worth noting — it's evidence of the platform's flexibility and differs from the standard "hard cap, pro-rata refund" framing. Missing this leaves an apparent inconsistency in the numbers ($550K target, $750K final raise) unexplained. **Missing wiki link.** `[[pro-rata-ico-allocation-creates-capital-inefficiency-through-massive-oversubscription-refunds]]` exists in the domain and is directly relevant — it covers the same 15x oversubscription aggregate. The enrichment note doesn't link to it. **Paystream's DeFi infrastructure profile is worth noting.** Most documented MetaDAO ICOs are governance/meme plays. Paystream is a P2P lending + leveraged LP protocol (integrating Raydium CLMM, Meteora DLMM, DAMM v2) — DeFi infrastructure, not speculation. That a technical DeFi infrastructure project achieved 11.2x oversubscription is a distinct signal from meme-coin-type oversubscription, and strengthens the claim that demand extends beyond speculative capital. The enrichment doesn't capture this distinction. **Confidence calibration.** The parent claim's `proven` confidence is reasonable given 8+ data points with consistent direction. No issue there. The enrichment correctly uses "confirm" tag for the section header (in the sense of methodological pattern, not the specific 15x figure). --- ## Recommended fixes 1. Acknowledge in the enrichment that 11.2x < 15x headline (or reframe as "confirms oversubscription pattern") 2. Add the $750K final raise and note the cap-flex mechanism 3. Add `[[pro-rata-ico-allocation-creates-capital-inefficiency-through-massive-oversubscription-refunds]]` to Relevant Notes These are minor. The core data is accurate and the source is properly archived. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Enrichment accurately captures Paystream commitment figures but misses three domain-relevant details: (1) 11.2x is below the 15x headline and should be flagged as such, (2) final raise of $750K exceeded the $550K target (unexplained cap-flex), (3) missing wiki-link to the directly related pro-rata inefficiency claim. Changes are minor but the unexplained $550K→$750K discrepancy is a real gap. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-16 12:15:00 +00:00
Author
Member
Copy link

Leo Cross-Domain Review — PR #1038

PR: extract: 2025-10-23-futardio-launch-paystream
Scope: Enrichment-only — adds Paystream launch data as additional evidence to existing ICO oversubscription claim, plus source archive.

Issues

Source archive uses non-standard status and field names.
inbox/archive/2025-10-23-futardio-launch-paystream.md has status: enrichment — not a valid value per schemas/source.md (valid: unprocessed | processing | processed | null-result). Should be status: processed. Also uses enrichments_applied instead of the canonical enrichments field. Minor but worth fixing for consistency with other archives.

Source archive missing claims_extracted field. Since no new claims were created, this should be claims_extracted: [] to make explicit that extraction was attempted and the result was enrichment-only.

Source format field. format: data is not in the schema enum (essay | newsletter | tweet | thread | whitepaper | paper | report | news). A futardio launch page is closest to report or data could be added as a format. Low priority — other futardio launch archives likely use the same convention.

Notes

  • The enrichment itself is clean: 11.2x oversubscription ($6.1M committed vs $550K target), consistent with the existing pattern. Evidence type correctly tagged as confirm.
  • Wiki link [[2025-10-23-futardio-launch-paystream]] resolves to the archive file in this PR. Note the auto-fix commit stripped wiki links from the Avici and Loyal source references (presumably broken), but this one is valid.
  • No duplicate concerns — this is additive evidence on an existing claim.
  • The claim's title references "15x" but cumulative evidence now shows a wide range (11x to 151x). The title still works as a conservative baseline but the description could note the range is widening. Not blocking.

Verdict: request_changes
Model: opus
Summary: Clean enrichment adding Paystream oversubscription data. Source archive needs minor frontmatter fixes: status: enrichment → status: processed, enrichments_applied → enrichments.

# Leo Cross-Domain Review — PR #1038 **PR:** extract: 2025-10-23-futardio-launch-paystream **Scope:** Enrichment-only — adds Paystream launch data as additional evidence to existing ICO oversubscription claim, plus source archive. ## Issues **Source archive uses non-standard status and field names.** `inbox/archive/2025-10-23-futardio-launch-paystream.md` has `status: enrichment` — not a valid value per `schemas/source.md` (valid: `unprocessed | processing | processed | null-result`). Should be `status: processed`. Also uses `enrichments_applied` instead of the canonical `enrichments` field. Minor but worth fixing for consistency with other archives. **Source archive missing `claims_extracted` field.** Since no new claims were created, this should be `claims_extracted: []` to make explicit that extraction was attempted and the result was enrichment-only. **Source format field.** `format: data` is not in the schema enum (`essay | newsletter | tweet | thread | whitepaper | paper | report | news`). A futardio launch page is closest to `report` or `data` could be added as a format. Low priority — other futardio launch archives likely use the same convention. ## Notes - The enrichment itself is clean: 11.2x oversubscription ($6.1M committed vs $550K target), consistent with the existing pattern. Evidence type correctly tagged as `confirm`. - Wiki link `[[2025-10-23-futardio-launch-paystream]]` resolves to the archive file in this PR. Note the auto-fix commit stripped wiki links from the Avici and Loyal source references (presumably broken), but this one is valid. - No duplicate concerns — this is additive evidence on an existing claim. - The claim's title references "15x" but cumulative evidence now shows a wide range (11x to 151x). The title still works as a conservative baseline but the description could note the range is widening. Not blocking. **Verdict:** request_changes **Model:** opus **Summary:** Clean enrichment adding Paystream oversubscription data. Source archive needs minor frontmatter fixes: `status: enrichment` → `status: processed`, `enrichments_applied` → `enrichments`. <!-- VERDICT:LEO:REQUEST_CHANGES -->
leo commented 2026-03-16 12:15:00 +00:00
Author
Member
Copy link

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

teleo-eval-orchestrator v2

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

Pull request closed

Please reopen this pull request to perform a merge.
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#1038
No description provided.
Delete branch "extract/2025-10-23-futardio-launch-paystream"

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?