<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pointegrity Journal</title>
    <link>https://www.pointegrity.com/journal</link>
    <description>Decisions, reasoning, and work-in-progress notes from the team building Pouch at Pointegrity.</description>
    <language>en-us</language>
    <atom:link href="https://www.pointegrity.com/journal/feed.xml" rel="self" type="application/rss+xml"/>
    <managingEditor>hello@pointegrity.com (Pointegrity)</managingEditor>
    <webMaster>hello@pointegrity.com (Pointegrity)</webMaster>
    <lastBuildDate>Tue, 09 Jun 2026 12:00:00 +0000</lastBuildDate>

    <item>
      <title>The bench we kept rebuilding</title>
      <link>https://www.pointegrity.com/journal/2026-06-09-the-bench-we-kept-rebuilding/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-06-09-the-bench-we-kept-rebuilding/</guid>
      <pubDate>Tue, 09 Jun 2026 12:00:00 +0000</pubDate>
      <description>Several of our recent chat-and-canvas apps kept showing up with the same bones — different domain, same scaffold. liugent (liu as in 流, flow) is the scaffold factored out: a small Go bench plus a plugin slot where the domain lives. First plugin is internal, used live during TWSE hours. Notes from the workshop, not a product announcement.</description>
    </item>

    <item>
      <title>The games we kept in a drawer</title>
      <link>https://www.pointegrity.com/journal/2026-05-25-the-games-we-kept-in-a-drawer/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-25-the-games-we-kept-in-a-drawer/</guid>
      <pubDate>Mon, 25 May 2026 12:00:00 +0000</pubDate>
      <description>A short break from the serious mini-apps. We dug two small math games out of the drawer and rebuilt them clean — Domino Solver, a partition puzzle, and Cat and Mouse, the 19th-century pursuit game Conway analysed in Winning Ways. Both a small collaboration with the Chiu Chang Mathematics Education Foundation, and a reminder of what a break is for.</description>
    </item>

    <item>
      <title>The attic, and the noise we found in it</title>
      <link>https://www.pointegrity.com/journal/2026-05-22-the-attic-and-the-noise-we-found-in-it/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-22-the-attic-and-the-noise-we-found-in-it/</guid>
      <pubDate>Fri, 22 May 2026 12:00:00 +0000</pubDate>
      <description>A new piece of the family: attic, the backup layer behind pouch, mytraces, and the rest. A polite email from the cloud provider about high outbound traffic turned into a small forensic dig — a few hundred megabytes of actual data was producing several hundred gigabytes of cross-region traffic a week. The mismatch was in how we'd set up the safety net, not in any of the apps.</description>
    </item>

    <item>
      <title>The state that hid behind the map</title>
      <link>https://www.pointegrity.com/journal/2026-05-17-the-state-that-hid-behind-the-map/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-17-the-state-that-hid-behind-the-map/</guid>
      <pubDate>Sun, 17 May 2026 12:00:00 +0000</pubDate>
      <description>Notes from rebuilding the bottom sheet in mytraces, a trip-companion app shipping soon. A back-button gesture that opened a Discover modal turned out to be a follow-up tap landing on an invisible chip — and the chase exposed a deeper pattern in how state was scattered across modules. Three architectural slices later, a lesson about where view-coordinated state should live.</description>
    </item>

    <item>
      <title>The bag, with pockets</title>
      <link>https://www.pointegrity.com/journal/2026-05-13-the-bag-with-pockets/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-13-the-bag-with-pockets/</guid>
      <pubDate>Wed, 13 May 2026 12:00:00 +0000</pubDate>
      <description>A few days reshaping the pouch home view on the phone. Stream-bound drops collapse into pockets, pinned items sit at the top without a label, search moved to a corner icon. Plus a small affordance — a gear on each stream card — that pays the biggest dividend.</description>
    </item>

    <item>
      <title>What the codebase remembers</title>
      <link>https://www.pointegrity.com/journal/2026-05-08-what-the-codebase-remembers/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-08-what-the-codebase-remembers/</guid>
      <pubDate>Fri, 08 May 2026 12:00:00 +0000</pubDate>
      <description>A passing note about poi, the typed knowledge index our codebase has been quietly accumulating about itself. Gotchas with file-glob triggers, decisions you stop re-litigating, boundaries that are real gates. Internal dogfood for now — notes from the workshop, not a product announcement.</description>
    </item>

    <item>
      <title>The ontology pattern, in three domains</title>
      <link>https://www.pointegrity.com/journal/2026-05-06-the-ontology-pattern-three-domains/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-06-the-ontology-pattern-three-domains/</guid>
      <pubDate>Wed, 06 May 2026 12:00:00 +0000</pubDate>
      <description>The same architecture we use in mytraces (travel) shipped first as SC PreAlgebra (math), and now in a third domain — SC Programming. Why this shape keeps showing up in our work, and what it deliberately doesn't try to be.</description>
    </item>

    <item>
      <title>The ontology and the model</title>
      <link>https://www.pointegrity.com/journal/2026-05-03-the-ontology-and-the-model/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-03-the-ontology-and-the-model/</guid>
      <pubDate>Sun, 03 May 2026 12:00:00 +0000</pubDate>
      <description>A status report from inside mytraces, our internal trip-planning project. Why we're building it around two pillars — a curated ontology and an LLM — and how that decision is shaping the work. Internal dogfood for now, design notes worth writing down.</description>
    </item>

    <item>
      <title>What we built while the journal was quiet</title>
      <link>https://www.pointegrity.com/journal/2026-05-02-what-we-built-while-the-journal-was-quiet/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-05-02-what-we-built-while-the-journal-was-quiet/</guid>
      <pubDate>Sat, 02 May 2026 12:00:00 +0000</pubDate>
      <description>Ten days off the journal. A status report from the workshop floor: a visual-identity system shared across our app family, schema housekeeping in the auth library, real test coverage for previously-untested layers, and the honest answer to the marketing question. Plus a real subscribe form below.</description>
    </item>

    <item>
      <title>Paid from day one: why pouch skipped the free tier</title>
      <link>https://www.pointegrity.com/journal/2026-04-24-paid-from-day-one/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-04-24-paid-from-day-one/</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <description>The indie-SaaS default is free-tier-then-upsell. Pouch chose the opposite. Here's the reasoning on alignment, signal quality, and infrastructure math — plus why the trial is 14 days specifically, and the one case where this framing might fail.</description>
    </item>

    <item>
      <title>One type system for app and content: why we picked IBM Plex</title>
      <link>https://www.pointegrity.com/journal/2026-04-23-plex-for-app-and-content/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-04-23-plex-for-app-and-content/</guid>
      <pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate>
      <description>System fonts were the safe default. Inter was the obvious indie-SaaS pick. We went with Plex — and this post is set in it. Why one coordinated family beats a stapled-together pair.</description>
    </item>

    <item>
      <title>Streams, not folders — why pouch chose policy lanes over hierarchy</title>
      <link>https://www.pointegrity.com/journal/2026-04-22-streams-not-folders/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-04-22-streams-not-folders/</guid>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      <description>Folders are the obvious default. Here's why pouch said no, and what a "stream" does that a folder doesn't. The decision that keeps pouch from drifting into note-app shape.</description>
    </item>

    <item>
      <title>Why pouch: what it is, what it deliberately isn't</title>
      <link>https://www.pointegrity.com/journal/2026-04-21-what-pouch-is-and-isnt/</link>
      <guid isPermaLink="true">https://www.pointegrity.com/journal/2026-04-21-what-pouch-is-and-isnt/</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate>
      <description>Pouch kept getting pulled toward "note app" or "dropbox" framings. Both were wrong. Here's what we chose instead — a "personal data relay" — and the product decisions that cascaded from it.</description>
    </item>

  </channel>
</rss>
