Digest · the push engine

Resurfaced for you today

Three tracks feed this: scheduled decay, stochastic resurfacing of the unprocessed, and relevance triggers that match what you are doing right now. Dig in before you judge — then let the verdict carry a reason, so the Well learns something a thumbs-down cannot teach it.

6 openof 8
scheduled · decaypriority scalar, re-sorted daily, auto-postpone stochasticcheap resurfacing of the unprocessed relevance triggersurfaced because it matches what you are doing now
  • relevance trigger you asked about the retention figure twice this week

    The 71% caveat was written down once and never carried forward

    The pilot-cohort caveat lives in a single Drive readout. Every downstream mention drops it. This is the shape of thing a compulsory lens exists for — it is a standard, not a note.

    open questionIs the account-wide retention rate ever going to be computed, or is the pilot cohort the standing definition?

    client/steadystars biz 20mo old priority 88
  • scheduled · decay due today on the decay schedule — third pass

    The embeddings decision is still deferred, not resolved

    Local model versus the API. The whole measured corpus costs about $2.58 to embed either way, so this was never a budget call — it is a quality check that has not been run. Every chunk in the Well still has a null embedding, which means semantic search does not exist yet.

    project/mimir ops/finance 26d old priority 74
    rising — back sooner
  • stochastic random draw from the unprocessed pile

    Boomerang went on hold and nobody wrote down why

    On hold since 2023-06-30. The tasks are still relevant, the sections are not. Nothing in the Well records the reasoning behind the pause, only its date — which is exactly the class of gap the resurfacing pass exists to surface.

    project/boomerang 3.1y old priority 41
    • unfruitfulparked deliberately, not forgotten — stop bringing it back monthlyFB-0142 · linked to A-311