<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — oasis questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New oasis design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>flovenet apps vs oasis — overall stance?</title>
      <link>https://flove.org/making-of.html#nety-spec_q48</link>
      <guid isPermaLink="false">nety-spec_q48</guid>
      <category>nety-spec</category>
      <category>oasis</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• flovenet INDEPENDENT; oasis as optional add-on — flovenet apps implement everything natively, LEARNING oasis's good patterns; oasis is an opt-in add-on (SSB federation, '42' AI). flovenet works fully without it.
• oasis as the upper layer — Build the apps layer on oasis/SSB directly; a hard dependency.
• Merge into one stack — Fuse flovenet + oasis into a single codebase.

★ decided: flovenet INDEPENDENT; oasis as optional add-on</description>
    </item>
    <item>
      <title>flovenet has ONE score; spec wants four facets — reconcile?</title>
      <link>https://flove.org/making-of.html#nety-spec_q49</link>
      <guid isPermaLink="false">nety-spec_q49</guid>
      <category>nety-spec</category>
      <category>oasis</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Derive four facets as views — Keep the working engine; expose four facets as derived views over inputs it already has. Least churn.
• Refactor reputation_engine into 4 facets — Properly re-model into four stored scores; cleanest, most churn.
• UI-only four facets — Single score under the hood; four facets only in the frontend.

★ decided: Derive four facets as views</description>
    </item>
    <item>
      <title>The invite layer (absent in flovenet) — build where/when?</title>
      <link>https://flove.org/making-of.html#nety-spec_q50</link>
      <guid isPermaLink="false">nety-spec_q50</guid>
      <category>nety-spec</category>
      <category>oasis</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Frontend mock now + adapt oasis pub-invites later — nety page mocks the whole invite web now; real path extends oasis pub-invites with lineage. Native build is a later milestone.
• Start the flovenet invite module now — Begin a real Rust invite layer in parallel.
• Adapt oasis pub-invites — Base it on SSB invites from the start.

★ decided: Frontend mock now + adapt oasis pub-invites later</description>
    </item>
    <item>
      <title>Recovery realism (SSB can't rotate identity)?</title>
      <link>https://flove.org/making-of.html#nety-spec_q51</link>
      <guid isPermaLink="false">nety-spec_q51</guid>
      <category>nety-spec</category>
      <category>oasis</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Accept 'no recovery' for now — Mock recovery in the frontend; real social recovery is an acknowledged hard future milestone, not a blocker.
• Commit to a social-recovery sidechain — Plan a real rotation/recovery layer beside the append-only identity.
• Self-backup only for now — Ship only self-custody backup; defer social recovery.

★ decided: Accept 'no recovery' for now</description>
    </item>
  </channel>
</rss>
