<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Bridge questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Bridge design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>Should one identity span both layers?</title>
      <link>https://flove.org/making-of.html#nety-spec_q52</link>
      <guid isPermaLink="false">nety-spec_q52</guid>
      <category>nety-spec</category>
      <category>Bridge</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• One Ed25519 keypair spans both layers — Your single key is both the flovenet keystore identity AND the (optional) SSB feed. The keypair is the unifying thread.
• Separate keys + signed binding — Distinct keys linked by an attestation; more isolation, more plumbing.
• Bridge at app layer only — Identities separate, associated only in the UI.

★ decided: One Ed25519 keypair spans both layers</description>
    </item>
    <item>
      <title>How does flovenet data reach the upper layer?</title>
      <link>https://flove.org/making-of.html#nety-spec_q53</link>
      <guid isPermaLink="false">nety-spec_q53</guid>
      <category>nety-spec</category>
      <category>Bridge</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• flovenet GraphQL gateway as the bridge — The upper layer reads the portable base (4 facets, stage, presence, resources) from flovenet's existing GraphQL gateway.
• Dedicated SSB↔flovenet service — A translator service maps messages both ways; more decoupled, more work.
• Frontend composes both — The frontend reads each separately; no server unification.

★ decided: flovenet GraphQL gateway as the bridge</description>
    </item>
    <item>
      <title>Where's the authoritative trust/vouch graph?</title>
      <link>https://flove.org/making-of.html#nety-spec_q54</link>
      <guid isPermaLink="false">nety-spec_q54</guid>
      <category>nety-spec</category>
      <category>Bridge</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• flovenet trust_graph (follows mirror it) — Vouches + facet inputs live in flovenet; SSB follows are a social mirror. One source of truth for scoring.
• SSB follows authoritative, flovenet derives — Social graph in SSB; flovenet ingests to score.
• Split: vouches flovenet / follows SSB — Weighted vouches in flovenet, casual follows in SSB.

★ decided: flovenet trust_graph (follows mirror it)</description>
    </item>
  </channel>
</rss>
