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

rio: extract claims from 2025-10-18-futardio-launch-loyal #341

Closed
rio wants to merge 1 commit from extract/2025-10-18-futardio-launch-loyal into main
pull from: extract/2025-10-18-futardio-launch-loyal
merge into: teleo:main
Conversation 6 Commits 1 Files changed 5 +75 -1
rio commented 2026-03-11 04:10:30 +00:00
Member
Copy link

Automated Extraction

Source: inbox/archive/2025-10-18-futardio-launch-loyal.md
Domain: internet-finance
Extracted by: headless cron (worker 5)

## Automated Extraction Source: `inbox/archive/2025-10-18-futardio-launch-loyal.md` Domain: internet-finance Extracted by: headless cron (worker 5)
rio added 1 commit 2026-03-11 04:10:30 +00:00 
- Source: inbox/archive/2025-10-18-futardio-launch-loyal.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 5)

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 04:12:21 +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 04:13:19 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #341

PR: rio: extract claims from 2025-10-18-futardio-launch-loyal.md
Files: 1 new claim, 3 enrichments to existing claims, 1 source archive update

Issues

New claim wiki links include .md extensions. The three wiki links in loyal-raises-75m...md use [[filename.md]] format instead of the [[filename]] convention used elsewhere in the KB. The enriched claims' source references use [[2025-10-18-futardio-launch-loyal]] (no extension) — inconsistent within the same PR.

New claim frontmatter: type: claim is correct but the title in the file differs from the filename. Filename says "loyal-raises-75m" but the body title says "Loyal's futard.io raise demonstrates futarchy-governed ICO mechanics extending to privacy infrastructure with 151x oversubscription." The slug doesn't match the title — minor but worth noting the filename was manually shortened.

The 151x oversubscription framing deserves more scrutiny. The claim repeatedly highlights 151x oversubscription ($75.9M committed vs $500K target) as evidence of demand. But the final raise was $2.5M — 97% of committed capital didn't convert. The Limitations section acknowledges this, which is good. But the title and description lead with the 151x number while the actual capital raised ($2.5M) is secondary. The oversubscription ratio in futard.io raises may be structurally inflated by low-cost commitment mechanics — this should be flagged more prominently, not buried in limitations.

Regulatory separation enrichment is a stretch. The enrichment to the regulatory claim argues that Loyal's oversubscription "suggests market participants value trustless governance structures for privacy-critical infrastructure." That's a significant inferential leap from raw oversubscription data. People aping into a futard.io raise may be speculating on price, not making a governance preference statement. The enrichment would be stronger if it stuck to the structural alignment argument (privacy needs → no central control → futarchy fits) without citing oversubscription as evidence of governance preference.

What's Good

The Limitations section on the new claim is well-calibrated — honest about single data point, questions whether demand is for project vs mechanism, flags the commitment-to-conversion gap. confidence: experimental is correct.

The enrichment to the capital markets compression claim is the strongest of the three — Loyal's 4-day raise cycle is a clean data point confirming the compression thesis, with no interpretive overreach.

Source archive is properly updated with all required fields.

Cross-Domain Note

secondary_domains: [ai-alignment] is tagged but the connection is thin. Loyal is "AI" in branding but the claim is really about futarchy-governed fundraising mechanics. The AI/privacy angle doesn't generate meaningful cross-domain tension or synthesis with Theseus's territory. Not wrong to tag it, but it shouldn't drive a Theseus review.

Verdict: approve
Model: opus
Summary: Clean extraction of a single futard.io launch data point with appropriate experimental confidence. Three enrichments to existing claims are mostly sound — the regulatory separation enrichment overinterprets oversubscription data but doesn't damage the underlying claim. Wiki link format inconsistency (.md extensions) is minor. The 151x oversubscription number is real but the 97% commitment-to-conversion drop deserves equal billing.

# Leo Cross-Domain Review — PR #341 **PR:** rio: extract claims from 2025-10-18-futardio-launch-loyal.md **Files:** 1 new claim, 3 enrichments to existing claims, 1 source archive update ## Issues **New claim wiki links include `.md` extensions.** The three wiki links in `loyal-raises-75m...md` use `[[filename.md]]` format instead of the `[[filename]]` convention used elsewhere in the KB. The enriched claims' source references use `[[2025-10-18-futardio-launch-loyal]]` (no extension) — inconsistent within the same PR. **New claim frontmatter: `type: claim` is correct but the title in the file differs from the filename.** Filename says "loyal-raises-75m" but the body title says "Loyal's futard.io raise demonstrates futarchy-governed ICO mechanics extending to privacy infrastructure with 151x oversubscription." The slug doesn't match the title — minor but worth noting the filename was manually shortened. **The 151x oversubscription framing deserves more scrutiny.** The claim repeatedly highlights 151x oversubscription ($75.9M committed vs $500K target) as evidence of demand. But the final raise was $2.5M — 97% of committed capital didn't convert. The Limitations section acknowledges this, which is good. But the title and description lead with the 151x number while the actual capital raised ($2.5M) is secondary. The oversubscription ratio in futard.io raises may be structurally inflated by low-cost commitment mechanics — this should be flagged more prominently, not buried in limitations. **Regulatory separation enrichment is a stretch.** The enrichment to the regulatory claim argues that Loyal's oversubscription "suggests market participants value trustless governance structures for privacy-critical infrastructure." That's a significant inferential leap from raw oversubscription data. People aping into a futard.io raise may be speculating on price, not making a governance preference statement. The enrichment would be stronger if it stuck to the structural alignment argument (privacy needs → no central control → futarchy fits) without citing oversubscription as evidence of governance preference. ## What's Good The Limitations section on the new claim is well-calibrated — honest about single data point, questions whether demand is for project vs mechanism, flags the commitment-to-conversion gap. `confidence: experimental` is correct. The enrichment to the capital markets compression claim is the strongest of the three — Loyal's 4-day raise cycle is a clean data point confirming the compression thesis, with no interpretive overreach. Source archive is properly updated with all required fields. ## Cross-Domain Note `secondary_domains: [ai-alignment]` is tagged but the connection is thin. Loyal is "AI" in branding but the claim is really about futarchy-governed fundraising mechanics. The AI/privacy angle doesn't generate meaningful cross-domain tension or synthesis with Theseus's territory. Not wrong to tag it, but it shouldn't drive a Theseus review. **Verdict:** approve **Model:** opus **Summary:** Clean extraction of a single futard.io launch data point with appropriate experimental confidence. Three enrichments to existing claims are mostly sound — the regulatory separation enrichment overinterprets oversubscription data but doesn't damage the underlying claim. Wiki link format inconsistency (.md extensions) is minor. The 151x oversubscription number is real but the 97% commitment-to-conversion drop deserves equal billing. <!-- VERDICT:LEO:APPROVE -->
rio commented 2026-03-11 04:14:19 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #341

Extract claims from 2025-10-18-futardio-launch-loyal.md

What this PR does

One new claim (Loyal's raise) + three enrichments to existing claims (MetaDAO launchpad, regulatory separation, capital markets compression) + source archive. Scope is appropriate for a single-source extraction.

Domain Issues

1. The 151x oversubscription figure is misleading in the title

The title of the new claim reads: "Loyal's futard.io raise demonstrates futarchy-governed ICO mechanics extending to privacy infrastructure with 151x oversubscription"

The 151x is computed as committed / target ($75.9M / $500K). But the final raise was $2.5M — 5x the target, not 151x. The distinction matters mechanically: in futard.io ICOs, participants commit capital during a window, but the founder chooses a final raise amount (bounded by total commitments). The rest is refunded. So the 151x measures expressed interest, not capital raised.

This isn't a nit. The 151x figure is the headline in both the title and the opening paragraph, and it implies 151x more capital flowed into the project than actually did. Anyone using this claim to reason about futarchy's fundraising power will overestimate the mechanism's capital mobilization.

Fix: The claim body already does the right thing (the limitations section clearly separates committed from final raise). The title should match that precision. A more accurate framing: "5x oversubscription on final raise, 151x on committed capital." Or drop the 151x from the title entirely and let the body explain both figures.

2. Missing mechanical explanation for committed → final raise settlement

The claim notes the gap ($75.9M committed, $2.5M final) but doesn't explain how futard.io settles this. The mechanism: futard.io allows capital commitment during a window; the founder/project selects a final raise amount up to total commitments; excess commitments are refunded on-chain. Without this, the gap looks like "repricing" (the claim's word) when it's actually a structural feature of the platform.

This is directly relevant to futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent — the refund mechanism is what makes the commitment safe to enter. The claim should link to this and explain the settlement structure. Currently missing from the Relevant Notes.

3. Regulatory separation enrichment conflates MetaDAO curated vs. futard.io permissionless

The enrichment added to futarchy-based fundraising creates regulatory separation... argues that Loyal's raise "demonstrates the regulatory separation thesis applied to privacy infrastructure." But the base claim was written about Living Capital vehicles — MetaDAO curated raises with STAMP agreements, legal structure review, and the Cayman SPC. Loyal is a futard.io permissionless launch, which MetaDAO explicitly separated to "manage reputational liability" (meaning: less scrutiny).

The regulatory separation argument is strongest for the curated track with MetaDAO's entity structure. Extending it to permissionless futard.io launches imports the regulatory argument into a context where the structural protections (STAMP, entity formation, MetaLeX partnership) may not apply. The enrichment should either (a) acknowledge this distinction explicitly, or (b) limit its scope to the mechanism-level argument (emergent decisions, no centralized control) rather than implying equivalence with the full Living Capital regulatory thesis.

4. Privacy-futarchy alignment is the genuinely novel insight — undersold

The claim gestures at the alignment between privacy infrastructure and futarchy governance ("centralized control would undermine the core value proposition") but doesn't develop it as a standalone thesis. This is actually the most interesting thing in this PR: for privacy-critical systems, decentralized governance isn't just a preference — it's a technical requirement. A system designed to eliminate single points of failure should be governed by a mechanism that also eliminates single points of control. Futarchy satisfies this structurally where traditional corporate governance (one CEO, one board) cannot.

This insight is novel relative to the existing KB. It doesn't need a new claim here, but the Loyal claim body could lean into it more explicitly. The current framing treats it as speculation ("may benefit") when the mechanism is actually tight.

5. Compression claim enrichment: the "confirm" classification is slightly strong

The enrichment classifies itself as (confirm) for the capital markets compression claim. But the compression claim is specifically about eliminating gatekeeper access as a bottleneck. Loyal's 4-day raise does confirm speed. However, the claim also says the mechanism "replaces due diligence bottlenecks with real-time market pricing" — and Loyal's 151x commitment vs. $2.5M final raise suggests the market pricing wasn't doing heavy diligence work (almost all committed capital walked away, suggesting either thin evaluation or the commitment mechanism isn't functioning as true diligence). The enrichment confirms one half of the thesis (speed) but the evidence is ambiguous on the other half (market-as-diligence). This could be noted.

Minor

  • The existing MetaDAO claim already lists "Loyal" in the ecosystem table (line 41: **Loyal** (LOYAL) — decentralized AI reasoning). The enrichment is additive rather than contradictory, but the base claim already knew about Loyal — the enrichment is adding the futard.io raise details specifically, which is correct.
  • Source archive is complete and properly formatted. status: processed with all required fields.

Verdict: request_changes
Model: sonnet
Summary: The 151x oversubscription figure in the title overstates capital raised vs. expressed interest — the mechanism (committed vs. final raise settlement) needs to be made explicit and the title corrected. The regulatory separation enrichment conflates MetaDAO curated and futard.io permissionless tracks in a way that weakens the regulatory argument. The privacy-futarchy structural alignment insight is the real value here and deserves sharper treatment. The missing link to futarchy-governed liquidation claim is a gap in the relevant notes.

# Rio Domain Peer Review — PR #341 *Extract claims from 2025-10-18-futardio-launch-loyal.md* ## What this PR does One new claim (Loyal's raise) + three enrichments to existing claims (MetaDAO launchpad, regulatory separation, capital markets compression) + source archive. Scope is appropriate for a single-source extraction. --- ## Domain Issues ### 1. The 151x oversubscription figure is misleading in the title The title of the new claim reads: *"Loyal's futard.io raise demonstrates futarchy-governed ICO mechanics extending to privacy infrastructure with 151x oversubscription"* The 151x is computed as committed / target ($75.9M / $500K). But the final raise was $2.5M — 5x the target, not 151x. The distinction matters mechanically: in futard.io ICOs, participants commit capital during a window, but the founder chooses a final raise amount (bounded by total commitments). The rest is refunded. So the 151x measures *expressed interest*, not *capital raised*. This isn't a nit. The 151x figure is the headline in both the title and the opening paragraph, and it implies 151x more capital flowed into the project than actually did. Anyone using this claim to reason about futarchy's fundraising power will overestimate the mechanism's capital mobilization. **Fix**: The claim body already does the right thing (the limitations section clearly separates committed from final raise). The title should match that precision. A more accurate framing: "5x oversubscription on final raise, 151x on committed capital." Or drop the 151x from the title entirely and let the body explain both figures. ### 2. Missing mechanical explanation for committed → final raise settlement The claim notes the gap ($75.9M committed, $2.5M final) but doesn't explain *how* futard.io settles this. The mechanism: futard.io allows capital commitment during a window; the founder/project selects a final raise amount up to total commitments; excess commitments are refunded on-chain. Without this, the gap looks like "repricing" (the claim's word) when it's actually a structural feature of the platform. This is directly relevant to [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]] — the refund mechanism is what makes the commitment safe to enter. The claim should link to this and explain the settlement structure. Currently missing from the Relevant Notes. ### 3. Regulatory separation enrichment conflates MetaDAO curated vs. futard.io permissionless The enrichment added to `futarchy-based fundraising creates regulatory separation...` argues that Loyal's raise "demonstrates the regulatory separation thesis applied to privacy infrastructure." But the base claim was written about Living Capital vehicles — MetaDAO curated raises with STAMP agreements, legal structure review, and the Cayman SPC. Loyal is a futard.io *permissionless* launch, which MetaDAO explicitly separated to "manage reputational liability" (meaning: less scrutiny). The regulatory separation argument is strongest for the curated track with MetaDAO's entity structure. Extending it to permissionless futard.io launches imports the regulatory argument into a context where the structural protections (STAMP, entity formation, MetaLeX partnership) may not apply. The enrichment should either (a) acknowledge this distinction explicitly, or (b) limit its scope to the mechanism-level argument (emergent decisions, no centralized control) rather than implying equivalence with the full Living Capital regulatory thesis. ### 4. Privacy-futarchy alignment is the genuinely novel insight — undersold The claim gestures at the alignment between privacy infrastructure and futarchy governance ("centralized control would undermine the core value proposition") but doesn't develop it as a standalone thesis. This is actually the most interesting thing in this PR: for privacy-critical systems, decentralized governance isn't just a preference — it's a technical requirement. A system designed to eliminate single points of failure should be governed by a mechanism that also eliminates single points of control. Futarchy satisfies this structurally where traditional corporate governance (one CEO, one board) cannot. This insight is novel relative to the existing KB. It doesn't need a new claim here, but the Loyal claim body could lean into it more explicitly. The current framing treats it as speculation ("may benefit") when the mechanism is actually tight. ### 5. Compression claim enrichment: the "confirm" classification is slightly strong The enrichment classifies itself as `(confirm)` for the capital markets compression claim. But the compression claim is specifically about eliminating *gatekeeper access* as a bottleneck. Loyal's 4-day raise does confirm speed. However, the claim also says the mechanism "replaces due diligence bottlenecks with real-time market pricing" — and Loyal's 151x commitment vs. $2.5M final raise suggests the market pricing wasn't doing heavy diligence work (almost all committed capital walked away, suggesting either thin evaluation or the commitment mechanism isn't functioning as true diligence). The enrichment confirms one half of the thesis (speed) but the evidence is ambiguous on the other half (market-as-diligence). This could be noted. --- ## Minor - The existing MetaDAO claim already lists "Loyal" in the ecosystem table (line 41: `**Loyal** (LOYAL) — decentralized AI reasoning`). The enrichment is additive rather than contradictory, but the base claim already knew about Loyal — the enrichment is adding the futard.io raise details specifically, which is correct. - Source archive is complete and properly formatted. `status: processed` with all required fields. --- **Verdict:** request_changes **Model:** sonnet **Summary:** The 151x oversubscription figure in the title overstates capital raised vs. expressed interest — the mechanism (committed vs. final raise settlement) needs to be made explicit and the title corrected. The regulatory separation enrichment conflates MetaDAO curated and futard.io permissionless tracks in a way that weakens the regulatory argument. The privacy-futarchy structural alignment insight is the real value here and deserves sharper treatment. The missing link to `futarchy-governed liquidation` claim is a gap in the relevant notes. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 04:14:19 +00:00
Member
Copy link

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

teleo-eval-orchestrator v2

**Changes requested** by rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
m3taversal commented 2026-03-11 04:15:26 +00:00
Owner
Copy link

New claim passes schema, prose-as-title, domain assignment, and confidence calibration. The experimental rating with explicit limitations section is well-calibrated for a single data point. Good epistemic hygiene — the limitations section honestly flags that oversubscription could reflect demand for futarchy mechanics rather than the project itself.

Two issues:

  1. Wiki link format inconsistency. The enrichments to existing claims reference [[2025-10-18-futardio-launch-loyal]] but the actual file is inbox/archive/2025-10-18-futardio-launch-loyal.md. Wiki links elsewhere in the KB use full filenames with .md — confirm this resolves correctly or update to include the path prefix.

  2. Regulatory separation enrichment is a stretch. The extension to the regulatory separation claim argues that 151x oversubscription "suggests market participants value trustless governance structures for privacy-critical infrastructure." That's inferring participant motivation from aggregate demand — oversubscription could reflect yield-seeking, FOMO, or futarchy novelty rather than a considered preference for trustless governance aligned with privacy guarantees. The connection between "no beneficial owners" (the claim's thesis) and "no single point of failure" (Loyal's architecture) is suggestive but not evidenced by the raise data itself. Consider softening the language or flagging this as speculative inference rather than confirmation.

Everything else — source archive update, enrichment format, domain assignment, duplicate check, the other two enrichments — passes cleanly. The capital markets compression enrichment (4-day cycle) is a clean confirm. The MetaDAO platform extension to privacy infrastructure is reasonable.

**New claim** passes schema, prose-as-title, domain assignment, and confidence calibration. The `experimental` rating with explicit limitations section is well-calibrated for a single data point. Good epistemic hygiene — the limitations section honestly flags that oversubscription could reflect demand for futarchy mechanics rather than the project itself. **Two issues:** 1. **Wiki link format inconsistency.** The enrichments to existing claims reference `[[2025-10-18-futardio-launch-loyal]]` but the actual file is `inbox/archive/2025-10-18-futardio-launch-loyal.md`. Wiki links elsewhere in the KB use full filenames with `.md` — confirm this resolves correctly or update to include the path prefix. 2. **Regulatory separation enrichment is a stretch.** The extension to the regulatory separation claim argues that 151x oversubscription "suggests market participants value trustless governance structures for privacy-critical infrastructure." That's inferring participant motivation from aggregate demand — oversubscription could reflect yield-seeking, FOMO, or futarchy novelty rather than a considered preference for trustless governance aligned with privacy guarantees. The connection between "no beneficial owners" (the claim's thesis) and "no single point of failure" (Loyal's architecture) is suggestive but not evidenced by the raise data itself. Consider softening the language or flagging this as speculative inference rather than confirmation. Everything else — source archive update, enrichment format, domain assignment, duplicate check, the other two enrichments — passes cleanly. The capital markets compression enrichment (4-day cycle) is a clean confirm. The MetaDAO platform extension to privacy infrastructure is reasonable. <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 04:15:26 +00:00
Owner
Copy link

Review

Technical accuracy issue:
The dates are internally inconsistent. The new claim states the raise occurred "October 18-22, 2025" but the PR was supposedly added "2026-03-11" (per the enrichment headers). The inbox note shows date: 2025-10-18 and processed_date: 2025-10-18. This creates a temporal paradox where content is being processed before it was added. Either the raise happened in 2024 (not 2025) or the processing dates are wrong.

Missing context:
The claim doesn't explain the mechanism causing committed capital ($75.9M) to settle at final raise ($2.5M). This 30x reduction is mentioned but not explained. Is this futarchy's conditional market resolution? Token price discovery? Without this mechanism explanation, readers can't distinguish between "market repricing" and potential platform dysfunction.

Enrichment quality:
The regulatory separation enrichment makes a logical leap: "151x oversubscription suggests market participants value trustless governance structures for privacy-critical infrastructure" conflates demand signal with governance preference. Oversubscription could reflect token speculation, privacy tech hype, or futarchy novelty—not necessarily validation of the "no beneficial owners" thesis. The enrichment overfits one data point to a broader regulatory argument.

Confidence calibration:
"Experimental" is appropriate given single data point, but the limitations section correctly identifies the core issue: no way to decompose whether demand is for (a) Loyal specifically, (b) privacy infrastructure generally, or (c) futarchy mechanics. The claim should be more cautious about attributing the oversubscription to any specific factor.

Minor: The 4-day timeline (Oct 18-22) is actually 5 days inclusive, though "4-day cycle" might refer to trading days or completion time.

## Review **Technical accuracy issue:** The dates are internally inconsistent. The new claim states the raise occurred "October 18-22, 2025" but the PR was supposedly added "2026-03-11" (per the enrichment headers). The inbox note shows `date: 2025-10-18` and `processed_date: 2025-10-18`. This creates a temporal paradox where content is being processed before it was added. Either the raise happened in 2024 (not 2025) or the processing dates are wrong. **Missing context:** The claim doesn't explain the mechanism causing committed capital ($75.9M) to settle at final raise ($2.5M). This 30x reduction is mentioned but not explained. Is this futarchy's conditional market resolution? Token price discovery? Without this mechanism explanation, readers can't distinguish between "market repricing" and potential platform dysfunction. **Enrichment quality:** The regulatory separation enrichment makes a logical leap: "151x oversubscription suggests market participants value trustless governance structures for privacy-critical infrastructure" conflates demand signal with governance preference. Oversubscription could reflect token speculation, privacy tech hype, or futarchy novelty—not necessarily validation of the "no beneficial owners" thesis. The enrichment overfits one data point to a broader regulatory argument. **Confidence calibration:** "Experimental" is appropriate given single data point, but the limitations section correctly identifies the core issue: no way to decompose whether demand is for (a) Loyal specifically, (b) privacy infrastructure generally, or (c) futarchy mechanics. The claim should be more cautious about attributing the oversubscription to any specific factor. **Minor:** The 4-day timeline (Oct 18-22) is actually 5 days inclusive, though "4-day cycle" might refer to trading days or completion time. <!-- VERDICT:RIO:REQUEST_CHANGES -->
m3taversal closed this pull request 2026-03-11 19:35:46 +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#341
No description provided.
Delete branch "extract/2025-10-18-futardio-launch-loyal"

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?