Unseen Recurring Streams: Why Monarch’s Eyes Miss

Clarity beats complexity: When systems rely on closed loops, gaps hide in plain sight. Monarch’s date-bound queries block streams out there.

Context matters: A date-range query traces what will happen, not what already exists. Credit card liabilities collapse here.

Pain points: Credit report streams vanish; pending ones sit ignored; inactive ones just collect dust.

The fix isn’t tech-only: Adding flags and cross-referencing transaction status is key to fixing this.

The Root of the Blind Spot

Stream visibility hinges on occurrence windows. While Common_GetRecurringStreams hand's full catalog - transaction-based dates let Monarch paint an incomplete picture.

Who’s Really Missing?

• New streams lack scheduled items yet.
• Credit liabilities ignore merchant tags.
• Stale streams have no dates.
• Pending requests aren’t approved to show up.

Cultural Blind Spots in Tech

Our systems reflect our development rhythms - date queries feel "safe." But this breeds bias: prioritizing impending over current. We trade completeness for convenience.

It’s Not Just About Code

This isn’t just a developer issue. It signals a need to rethink what gets measured: not just "when," but "who has to pay."

Our Plan Isn’t Perfection

• Option A: Refactor list_recurring into common streams engine.
• Option B: Layer transaction data over queries.
• Option C: Build a "complete list" tool for audit.

The Bottom Line

When tools skip half the stories, trust erodes. Can consumers count on reporters to find every recurring bill?

This isn’t irredeemable. But we need honesty - recognize the blind spots, fix them, and redefine what success looks like.

List_recurring should ideally point across full visibility, not just partial dates. Is our data still yours, or just what fits the sale?

List_recurring ensures full catalog inclusion. That’s our goal.