memopop-orchestrator
ai-labs/memopop-ai/apps/memopop-orchestrator/context-v/
34 files here
specs/7
MemoPop Connector API
Ten tools, one step registry, and the docs and tests that ship with each. What we build so a partner's Claude can write a MemoPop memo.
Introducing a Content Density Mode System
A system-level content mode toggle (redundant vs concise) that alters the behavior of the writer, table generator, and quality agents to match different firm preferences for information density and repetition.
Introducing a Diagram Generator Agent
Add a diagram_generator.py agent that identifies opportunities to create visual diagrams explaining complex business concepts, starting with TAM/SAM/SOM market sizing and expanding to common finance and consulting visuals.
PDF Parser Agent Specification
A small specification for an agent and script to parse PDFs and convert them to markdown with properly formatted citations.
Multi-Agent Orchestration for Investment Memo Generation
An exploration into using AI supervisors and specialized agents to generate high-quality content and documents.
Portfolio Listing Agent and Current Portfolio Section
Design notes for the portfolio_listing_agent that builds a Current Portfolio subsection and structured JSON for LP-commit emerging manager fund memos.
memopop-orchestrator/specs
plans/9
MemoPop Connector API, Phase 7: The Plugin and Real Claude
A thin skill that keeps Claude on the method, packaged with the connector, and a test where real Claude writes the fixture memo.
MemoPop Connector API, Phase 1: Foundation
The registry, errors, auth, storage, five tools, the docs generators, the ledger, and CI. Every later phase builds on this one.
MemoPop Connector API, Phase 2: Deploy
A container with every system tool the memo needs, running on Railway at memopop.didi.sh, watched by a health check every 30 minutes.
MemoPop Connector API, Phase 4: Materials
Decks, datarooms, notes, and links reach the server three ways, become text the steps can read, and never block the memo.
MemoPop Connector API, Phase 5: Enhancements, Compile, and the Full Flow
Every enhancement becomes a step that can skip, compile turns sections into a branded PDF, and a scripted client walks the whole memo.
MemoPop Connector API, Phase 6: History and Snapshots
Every saved artifact becomes a jj change the client never sees, and one save backs the firm's whole workspace up to its bucket.
Reconciling Perplexity Citations Against Retrieved Sources
Sonar hands us the sources it actually retrieved on every call, and we throw them away — so every URL in every memo is a guess.
Migrate `studies/open-specs-and-standards/` into its own pseudo-monorepo
memopop-orchestrator/plans
prompts/1
blueprints/1
reminders/5
Every Step Writes Its Output To File
A run's destination folder is decided before the first step, and every step writes its result there as it finishes. Nothing lives only in memory.
Normalize Labels Gradually
One company says Total Revenue, another says Gross Revenue, a third says Top Line. One reports monthly, another quarterly, another H1/H2, another only annually. Collection never touches any of it. Normalization is a later, corpus-level act — a cluster of labels that mean the same thing, one chosen default, and an alias map — built by a person from real analysis across real portfolios, never by an agent guessing from what the words sound like.
Round-Closing Timeline Nuances
Wires arrive before and after the close they belong to, rounds close later than anyone planned, and a fund and its SPV subscribe months apart on identical terms. None of that is an anomaly. Record every date as the document states it, never revise one to make a sequence tidy, and confine anomaly-noticing to the handful of series that are actually real at this stage — money spent, web traffic, signed contracts, billed subscription revenue. Everything else is a claim or a projection, and instinctive concerns about it belong in anomalies.json rather than in the memo or the conversation.
Long-Running Is Not a Reason to Fan Out
Duration is not the variable that decides whether work should be split across agents. Continuity is. Ask before parallelizing anything whose quality depends on what came before it.
memopop-orchestrator/reminders
agent-skills/1
explorations/1
issues/1
loops/2
handoffs/1
floaters/1
issue-resolution/3
Research Agent Concatenates Multiple Sources Under One Citation ID — And No Validator Catches It
`research_enhanced.py` writes several sources onto one `[^N]:` line, so downstream parsers keep the first and silently drop the rest.
Section Citations Orphaned When Definitions Live in 1-research/
`consolidate_citations.py` reads `### Citations` only inside section files, so defs living in `1-research/` become orphans.
memopop-orchestrator/issue-resolution