<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Plan questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Plan design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>Implement first?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q17</link>
      <guid isPermaLink="false">talk2web-refine_q17</guid>
      <category>Plan</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Gitea fully operating (provenance + push) — Make links + push real before anything else.
• making-of design polish — Finalise the page UX first.
• Sharing backend (replies / debate) — Stand up the shared layer first.
• Publishing skill (C) — Start whole-conversation publishing first.

★ decided: Gitea fully operating (provenance + push) · ◇ recommended: Gitea fully operating (provenance + push)</description>
    </item>
    <item>
      <title>Milestone size?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q18</link>
      <guid isPermaLink="false">talk2web-refine_q18</guid>
      <category>Plan</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• One coherent commit per block (A→E) — Ship each block as a unit; reviewable.
• Tiny incremental commits — Many small steps; the current cadence.
• Big-bang — All at once; risky.

★ decided: One coherent commit per block (A→E) · ◇ recommended: One coherent commit per block (A→E)</description>
    </item>
  </channel>
</rss>
