Greenfield, server-authoritative. A new deployable for the retailer side and the transmission network. HelmDocs integrates later across an API/MCP boundary.
Why. The existing monorepo is client-first by architecture: PGlite on every client with ElectricSQL sync, Yjs documents, an Electron desktop app. That design replicates data down to clients — precisely wrong for a system whose core promise is that a vendor's bid never reaches another vendor's machine. Fighting that grain would be a permanent tax.
What this costs. Auth, org model, and billing get rebuilt. The two sides stay separate products until deliberately joined.
What is still reusable. The prompts and the thinking in packages/ai/src/agents/ (intake-classifier, go-no-go, compliance-matrix-builder, section-drafter, negative-rfp-review) and packages/core/src/solicitation-extraction/. Proven against real federal solicitations (NSF 26-510). Lift the design, not the runtime.
## Resolution
**Greenfield, server-authoritative.** A new deployable for the retailer side and the transmission network. HelmDocs integrates later across an API/MCP boundary.
**Why.** The existing monorepo is client-first by architecture: PGlite on every client with ElectricSQL sync, Yjs documents, an Electron desktop app. That design replicates data down to clients — precisely wrong for a system whose core promise is that a vendor's bid never reaches another vendor's machine. Fighting that grain would be a permanent tax.
**What this costs.** Auth, org model, and billing get rebuilt. The two sides stay separate products until deliberately joined.
**What is still reusable.** The prompts and the thinking in `packages/ai/src/agents/` (intake-classifier, go-no-go, compliance-matrix-builder, section-drafter, negative-rfp-review) and `packages/core/src/solicitation-extraction/`. Proven against real federal solicitations (NSF 26-510). Lift the design, not the runtime.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Question
Greenfield, or inside the existing
novelpad-desktopmonorepo that already holds the bidder-side proposal engine?Parent: #1
Resolution
Greenfield, server-authoritative. A new deployable for the retailer side and the transmission network. HelmDocs integrates later across an API/MCP boundary.
Why. The existing monorepo is client-first by architecture: PGlite on every client with ElectricSQL sync, Yjs documents, an Electron desktop app. That design replicates data down to clients — precisely wrong for a system whose core promise is that a vendor's bid never reaches another vendor's machine. Fighting that grain would be a permanent tax.
What this costs. Auth, org model, and billing get rebuilt. The two sides stay separate products until deliberately joined.
What is still reusable. The prompts and the thinking in
packages/ai/src/agents/(intake-classifier, go-no-go, compliance-matrix-builder, section-drafter, negative-rfp-review) andpackages/core/src/solicitation-extraction/. Proven against real federal solicitations (NSF 26-510). Lift the design, not the runtime.