<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Allocations on Tenu Tech Brief</title>
    <link>https://cluster-site.onrender.com/tags/allocations/</link>
    <description>Recent content in Allocations on Tenu Tech Brief</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Feb 2026 15:42:57 +0000</lastBuildDate>
    <atom:link href="https://cluster-site.onrender.com/tags/allocations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Endowments eye crypto allocations amid tougher return outlook for traditional investments</title>
      <link>https://cluster-site.onrender.com/posts/endowments-eye-crypto-allocations-amid-tougher-return-outlook-for-traditional-investments/</link>
      <pubDate>Wed, 25 Feb 2026 14:41:45 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/endowments-eye-crypto-allocations-amid-tougher-return-outlook-for-traditional-investments/</guid>
      <description>• Endowments eye crypto allocations amid tougher return outlook for traditional investments Lower expected gains from traditional assets have prompted some funds to test bitcoin an</description>
    </item>
    <item>
      <title>[RFC] [GSOC] Buffer Reuse Pass for Non-Overlapping Allocations After lower-deallocations</title>
      <link>https://cluster-site.onrender.com/posts/rfc-gsoc-buffer-reuse-pass-for-non-overlapping-allocations-after-lower-deallocations/</link>
      <pubDate>Thu, 19 Feb 2026 18:29:26 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/rfc-gsoc-buffer-reuse-pass-for-non-overlapping-allocations-after-lower-deallocations/</guid>
      <description>• [RFC] [GSOC] Buffer Reuse Pass for Non-Overlapping Allocations After lower-deallocations Motivation &amp;amp; Background Many real-world workloads are expressed as structured, sequential</description>
    </item>
  </channel>
</rss>
