Hi HN,
I’m a Research Student for Physics, not a full-time software engineer. I built PreFlight out of personal frustration with manuscript prep: checking whether cited papers have been quietly retracted, verifying claim sentences against Crossref/OpenAlex, and catching unhedged assertions before peer review.
Because research drafts often contain unpublished findings or patent-sensitive data, the core design priority was Zero Data Retention (ZDR):
- Manuscript text never leaves your browser during editing. Tokenization, AST equation isolation, and BibTeX extraction run locally in Web Workers and WASM.
- Ephemeral API calls are only made when explicitly verifying claims (querying Retraction Watch, Crossref, and OpenAlex).
- Zero manuscript persistence and zero model training.
You can test it directly in the workbench without signing up (click "Load Sample Manuscript" to see how it flags retractions): https://preflightai.tech/workbench
As someone coming from research rather than full-time software engineering, I'd really appreciate feedback from developers and academics here on:
1. How the local parser handles edge-case LaTeX environments in your papers.
2. Edge performance or UX issues you notice.
Happy to answer questions!
I’m a Research Student for Physics, not a full-time software engineer. I built PreFlight out of personal frustration with manuscript prep: checking whether cited papers have been quietly retracted, verifying claim sentences against Crossref/OpenAlex, and catching unhedged assertions before peer review.
Because research drafts often contain unpublished findings or patent-sensitive data, the core design priority was Zero Data Retention (ZDR): - Manuscript text never leaves your browser during editing. Tokenization, AST equation isolation, and BibTeX extraction run locally in Web Workers and WASM. - Ephemeral API calls are only made when explicitly verifying claims (querying Retraction Watch, Crossref, and OpenAlex). - Zero manuscript persistence and zero model training.
You can test it directly in the workbench without signing up (click "Load Sample Manuscript" to see how it flags retractions): https://preflightai.tech/workbench
As someone coming from research rather than full-time software engineering, I'd really appreciate feedback from developers and academics here on: 1. How the local parser handles edge-case LaTeX environments in your papers. 2. Edge performance or UX issues you notice.
Happy to answer questions!