Upload the RFI PDF above and this panel fills in automatically — topic, page count, due date, and what's still missing from your checklist.
Reading PDF…
—
Pattern-matched from pasted/extracted text — not the live API yet. Verify before relying on it.
Paste Q&A answers into the checklist and this fills in automatically — question types, and any answers that read as binding guidance.
Pattern-matched from the pasted Q&A text — question types are keyword-guessed, not verified.
Our approach decomposes the targeting stack into three independently testable modules — sensor fusion, engagement scoring, and weaponeering handoff — each exposed through a documented, government-owned interface. This modular, open-systems architectureused in 4 wins shortens the integration timeline for downstream primes and satisfies WOSA compliance without a full stack rewrite. Phase I validates the sensor fusion module against a recorded target set; Phase II demonstrates the full stack in a representative embedded environment with a live over-the-air weapons interface.
We propose a three-module targeting stack — sensor fusion, engagement scoring, and weaponeering handoff — connected through open, government-owned interfaces. Phase I proves out sensor fusion against a recorded target set; Phase II fields the complete stack in an embedded, WOSA-compliant environment with a live weapons interface.
Real excerpts pulled from PDFs in your Private RFI/RFP Archive. Nothing here is ever sent to the AI automatically — check specific documents on the Reference Documents page (marked "SELECTED" below), and you'll be asked to confirm exactly which ones before each generation actually sends them.
Pick up where you left off — resume any of these to reload its topic into New Draft.
No drafts saved yet — use "Save Draft" on the New Draft page to add one here.
General-purpose reference material — capability statements, boilerplate paragraphs, diagrams — kept separate from Historic Submissions, which tracks actual submitted proposals and their outcomes.
Protected four ways: the folder is git-ignored (never committed, pushed, or deployed); it's chmod 700 (only your OS user account can read it); the local server binds to 127.0.0.1 only, so nothing else on your network can reach it; and it's behind a real login enforced by that server (a session cookie set only after the password checks out server-side) — there's no page-level trick that bypasses it, because the check happens before the server ever responds.
Wrong password.
File and folder names below are visible without logging in — opening a file or a folder's contents requires this.
✓ Folder created
✓ File uploaded successfully
private-rfi-archive/ yet. Drop files into that folder on disk, then reload this page.Pick a topic. Paste an RFI manually, or pull one live from the DoD SBIR/STTR feed.
Generate a draft. The Generation Engine assembles a prompt from the topic, the Template Library, and any proven wording Trend Analysis has surfaced, then calls Claude Fable and/or Gemini.
Review & edit. Compare drafts from each model, edit sections, regenerate as needed.
Export. Download the finished draft as a Word doc or Google Doc.
Tag the outcome. Once you hear back, mark the submission won, lost, or no reply in Historic Submissions.
Learn from it. That outcome lands in the Memory Store, and Trend Analysis mines it for wording that correlates with wins — it'll show up highlighted in your next draft.
Tentative: a Topic Poller could run step 1 automatically, on a schedule, instead of waiting for you to check.