memopop-orchestrator/issues

Path
issues/index.md

Issues

  • A Finished Memo Could Not Be Revised - The hosted connector only moved forward. Once a section was drafted, no tool could reopen it, so a colleague holding the latest PDF couldn’t add new research or a new angle.
  • A Stale Enhancement Outranked a Newer Draft - A section’s current text was picked by step order, not save order, so an old citations pass would have won over a freshly revised draft.
  • Agent Sequencing for Deals We Already Have Content On - The graph runs every stage from dataroom forward on every invocation, and caching is the only thing standing between a re-run and an hour of re-extraction. Every cache is keyed on content that ordinary maintenance changes, so the caches keep silently missing and the pipeline keeps redoing settled work. What is needed is an explicit entry point — resume at web research, or resume at writing — with additive semantics at each, rather than a graph that always starts at the beginning and hopes a hash still matches.
  • Dead ChatAnthropic Import in Socials Enrichment - The socials enrichment agent imports ChatAnthropic and never instantiates it — it is a Tavily-only agent. The import is inert at runtime but it is not harmless: it put the file on the CLI-first-provider refactor’s work list, where it would have cost a reader the time to open it and discover there was nothing to route. Deleting one line closes it.
  • Diagram SVGs Made Every Recompile a New Version - compile versions a memo by its content, and the market-sizing diagram rendered to different bytes every time, so an unchanged memo with a diagram never compiled as unchanged.
  • Funding Terms Invented Against the Deck Analysis - A final draft stated a priced round three times the real raise; its own deck analysis had the right figure. Nothing caught it before it shipped.
  • One Source, Cited Once — Not Fifty-Six Times - The exported memo lists 101 numbered sources for 17 distinct documents. The pitch deck alone appears 56 times, each as its own entry. And every one of them reads Published: N/A | Updated: N/A while the deck’s own PDF metadata carries 2026-09-08.
  • Route Every Claude Call Through the CLI-First Provider - A provider layer exists that tries the local Claude Code seat first and falls back to the metered API, printing a warning when it does. Ten files use it. Nineteen do not — they construct ChatAnthropic or an Anthropic client directly and bill the API unconditionally, which is why a run with a zero credit balance died on the deck analyst while the dataroom extractors beside it were routing correctly.
  • The Sidecar Cannot See the Claude CLI on PATH - A Tauri app launched from Finder gets the macOS GUI PATH — /usr/bin:/bin:/usr/sbin:/sbin — and the FastAPI sidecar inherits it. shutil.which(‘claude’) returns None there, so every memo generated from the desktop app billed the metered API no matter how many agents route through the provider. bun run dev:native inherits the terminal’s PATH, so it never reproduces in development.
  • Validation and Fact-Checker Not Using Research - Both quality gates score the memo without reading the research the writer was constrained to. The fact-checker looks up claims in a 16.5 KB legacy blob while the codified corpus sits unread in 1-research/; the validator sees only the memo and a style guide, so it cannot tell a dataroom-grounded citation from a missing one. The scores they emit measure citation mechanics, not truth — and the validator’s headline finding on ProfileHealth v0.0.3 is false of the memo that actually shipped.
  • jj Fails Under railway ssh Without HOME - An operator script that drops from root to the memopop user over railway ssh can’t start a firm’s jj history, because HOME still points at /root.