<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>tofu-web on BonsAI Documentation</title>
    <link>/docs/tofu-web/</link>
    <description>Recent content in tofu-web on BonsAI Documentation</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/docs/tofu-web/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>tofu-web Architecture Plan</title>
      <link>/docs/tofu-web/architecture/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/tofu-web/architecture/</guid>
      <description>&lt;h1 id=&#34;tofu-web-architecture-plan&#34;&gt;&#xA;  tofu-web Architecture Plan&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#tofu-web-architecture-plan&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Classification: Restricted (describes source code structure, infrastructure and auth flows).&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Status: the architecture is agreed, and the scaffold of section 7 is implemented in this PR.&#xA;Sections 8 and 9 remain design notes, not work in this plan. Deviations the implementation had to&#xA;make are recorded in 7.8. Owners: @wadwax, @kenkanai-tofu, @adamtofu and&#xA;@deepanshugautamtofu (&lt;code&gt;.github/CODEOWNERS&lt;/code&gt; for &lt;code&gt;/apps/tofu-web/&lt;/code&gt; and this docs section).&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Read with &lt;a href=&#34;./decisions&#34;&gt;Platform Decisions&lt;/a&gt;.&lt;/strong&gt; That document fixes the security model (replacing&#xA;the safety argument in 6.6), adds a non-silenceable boundaries gate to 6.8, bounds the tool&#xA;surface, settles model access on AWS, and sets the dependency policy. It keeps 6.3&amp;rsquo;s preference&#xA;design and states the costs that come with it. Its section 9 lists exactly what here it&#xA;supersedes; everything else below is current as written.&lt;/p&gt;</description>
    </item>
    <item>
      <title>tofu-web Platform Decisions</title>
      <link>/docs/tofu-web/decisions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/tofu-web/decisions/</guid>
      <description>&lt;h1 id=&#34;tofu-web-platform-decisions&#34;&gt;&#xA;  tofu-web Platform Decisions&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#tofu-web-platform-decisions&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Classification: Restricted (describes source code structure, infrastructure and auth flows).&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Status: proposed. This document fixes the platform decisions for &lt;code&gt;apps/tofu-web&lt;/code&gt; — the security&#xA;model, where preferences live, how layer boundaries are enforced, how the tool surface is bounded,&#xA;how the app reaches Claude on AWS, and how the dependency set is held stable. §8 records the&#xA;alternatives that were evaluated and rejected, with the evidence for each. §9 names the sections of&#xA;&lt;a href=&#34;./architecture&#34;&gt;the architecture plan&lt;/a&gt; these decisions supersede.&lt;/p&gt;</description>
    </item>
    <item>
      <title>tofu-web Chat Runtime Spike</title>
      <link>/docs/tofu-web/chat-runtime-spike/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/tofu-web/chat-runtime-spike/</guid>
      <description>&lt;h1 id=&#34;tofu-web-chat-runtime-spike&#34;&gt;&#xA;  tofu-web Chat Runtime Spike&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#tofu-web-chat-runtime-spike&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Classification: Internal-Only&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Recommendation superseded.&lt;/strong&gt; §1 below recommends assistant-ui.&#xA;&lt;a href=&#34;./decisions&#34;&gt;Platform Decisions&lt;/a&gt; §8 retires &lt;em&gt;both&lt;/em&gt; candidates, for a better reason than either of&#xA;mine: CopilotKit&amp;rsquo;s &lt;code&gt;AnthropicAdapter&lt;/code&gt; never calls its injected client, so SigV4 cannot work, and&#xA;its &lt;code&gt;BedrockAdapter&lt;/code&gt; takes no &lt;code&gt;sessionToken&lt;/code&gt;, which rules out STS credentials and therefore IRSA on&#xA;EKS. The tool runtime stays &lt;code&gt;@tanstack/ai&lt;/code&gt;. Everything measured here still stands — the SSE numbers&#xA;in §2 are why §8 also retires &lt;em&gt;dropping Start&amp;rsquo;s server&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
