A few caveats / current limitations (so expectations are clear):
- It’s an MVP and currently optimized for drafting workflow structure, not final donor submission formatting.
- Donor coverage is mixed: some donors have specialized strategy behavior, others use shared generic logic with catalog aliases.
- RAG ingestion is intentionally simple right now (PDF ingest + namespace isolation); deeper citation traceability is on the roadmap.
- Multi-tenant auth/permissions is not implemented yet (API key is service-level).
What I’d love feedback on:
- API design for async + HITL workflows
- where donor-specific logic should live vs generic strategy prompts
- ingestion/RAG ergonomics for real proposal teams
- whether this is useful as a standalone API vs embedded library
A few caveats / current limitations (so expectations are clear):
- It’s an MVP and currently optimized for drafting workflow structure, not final donor submission formatting. - Donor coverage is mixed: some donors have specialized strategy behavior, others use shared generic logic with catalog aliases. - RAG ingestion is intentionally simple right now (PDF ingest + namespace isolation); deeper citation traceability is on the roadmap. - Multi-tenant auth/permissions is not implemented yet (API key is service-level).
What I’d love feedback on: - API design for async + HITL workflows - where donor-specific logic should live vs generic strategy prompts - ingestion/RAG ergonomics for real proposal teams - whether this is useful as a standalone API vs embedded library