<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Cross-cutting questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Cross-cutting design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>How does nety standing carry into the apps?</title>
      <link>https://flove.org/making-of.html#nety-spec_q43</link>
      <guid isPermaLink="false">nety-spec_q43</guid>
      <category>nety-spec</category>
      <category>Cross-cutting</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Portable base + per-app overlay — Your four facets/stage/presence port everywhere as the baseline; each app can add its own context reputation on top.
• One global score everywhere — Apps read one standing; consistent but flattens kinds of merit.
• Per-community scoped — Each app weights/holds its own trust; less portable.

★ decided: Portable base + per-app overlay</description>
    </item>
    <item>
      <title>MyWizy autonomy (the finetuner)?</title>
      <link>https://flove.org/making-of.html#nety-spec_q44</link>
      <guid isPermaLink="false">nety-spec_q44</guid>
      <category>nety-spec</category>
      <category>Cross-cutting</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• You set policy, agent optimizes within it — You set goals + hard budgets/privacy; MyWizy optimizes peering/relay/recs within bounds and explains its choices.
• Fully manual, agent only suggests — You set everything; it just recommends.
• Fully autonomous, you set a vibe — Pick a mode; it handles the rest.

★ decided: You set policy, agent optimizes within it</description>
    </item>
    <item>
      <title>Key loss recovery?</title>
      <link>https://flove.org/making-of.html#nety-spec_q45</link>
      <guid isPermaLink="false">nety-spec_q45</guid>
      <category>nety-spec</category>
      <category>Cross-cutting</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Self-backup + social fallback — You hold a backup to rotate yourself; if lost, a quorum of your MyNet/vouchers co-signs to rebind.
• Social recovery only — Always a trusted-quorum rebind; nothing to store, depends on peers.
• Self-custody only — You alone hold a backup; lose it, lose everything.

★ decided: Self-backup + social fallback</description>
    </item>
    <item>
      <title>Standing transfer on recovery?</title>
      <link>https://flove.org/making-of.html#nety-spec_q46</link>
      <guid isPermaLink="false">nety-spec_q46</guid>
      <category>nety-spec</category>
      <category>Cross-cutting</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Carries forward, brief probation — All standing transfers, but a short probation after SOCIAL recovery guards against a hijacked recovery.
• Carries forward fully — New key inherits everything immediately; key-change shown on the tree.
• Lineage yes, scores partial — Identity+lineage survive, some scores re-accrue.

★ decided: Carries forward, brief probation</description>
    </item>
    <item>
      <title>How does the Verify trust section render?</title>
      <link>https://flove.org/making-of.html#nety-spec_q47</link>
      <guid isPermaLink="false">nety-spec_q47</guid>
      <category>nety-spec</category>
      <category>Cross-cutting</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Concentric scope rings — Nested rings Personal(core)→Local→Social→Global; arcs fill by score, Activity pulses on the outer ring. Literally draws 'concentric scope'.
• Stacked meters + boards — Four labeled bars + ladder + stage board; clearest, least designed.
• Orbiting facet constellation — You at center, facet-nodes orbiting; beautiful but busier.

★ decided: Concentric scope rings</description>
    </item>
  </channel>
</rss>
