TruePage & Scrutiny Engine

During my legal internship, I watched associates spend precious hours right before a filing deadline caught in a midnight scramble manually hunting down page numbers with 'Ctrl+F', re-typing cross-references in draft petitions because a single page shifted, and dealing with the dread of a Registry rejection days later over a minor formatting defect. TruePage & Scrutiny Engine was built to solve this exact operational bottleneck. It acts as an all-in-one pre-filing suite that takes a raw draft petition and messy annexures, uses natural language prompts to place documents, automatically refactors text references and continuous pagination, physically stitches the master bundle, and runs a High Court compliance audit before submission. The major problem is that compiling heavy court bundles (petitions, synopses, affidavits, and dozens of annexures like P-1, P-2) is entirely manual. Last-minute edits by senior partners cause page numbers to shift downstream. Associates waste hours manually re-typing page ranges inside the petition body and regenerating the index. Secondly, even after manual stitching, filings are submitted blind to the Court Registry. When minor formatting, margin, or index-pleading defects are caught days later, limitation keeps running, wasting critical client time. The solution to this is that Instead of manual cross-referencing, the lawyer simply inputs instructions (e.g., "Embed the lease deed as Annexure P-1 after paragraph 12"). The tool automatically updates the petition text body, injects the exact final page numbers, generates a master index, and physically merges the annexure PDFs into a unified master bundle. Before downloading the final package, the tool runs an automated compliance check against common High Court rules (margins, scanned resolutions, index-pleading mismatches) to ensure the filing is clear to submit on next day. This also saves registry timing

Key Featues include:-

1. It drops the draft petition and raw annexure files into the workspace, then uses simple text instructions (like "place the lease agreement as Annexure P-1 after paragraph 12") to dictate placement without manual file sorting.
2. It automatically hunts down placeholder brackets and outdated cross-references inside the main petition body, replacing them with exact, updated page numbers so you never have to manually "Ctrl+F" through a draft after a last-minute edit.
3. It merges the refactored petition, regenerated index, and all physical annexure PDFs into a single, continuous, sequentially numbered bundle ready for court submission.
4. It runs an automated check of the compiled bundle against standard registry objection checklists, flagging formatting errors, missing verifications, and index-pleading mismatches before the court ever sees them. This saves registry time as well.
5. It keeps the heavy lifting focused on predictable document layout and statutory rule matching, ensuring clean execution of margins, pagination numbering, and defect detection without relying on black-box guesswork.

I am looking for a tenchnical collaborators to help build out the backend infrastructure, as well as generate feedback on the user flow. While a fully scaled, production-grade automated PDF stitching and refactoring engine requires robust backend server infrastructure and heavy document-processing APIs (which involve significant cloud and processing costs beyond a weekend student budget), this prototype successfully demonstrates the complete end-to-end user workflow, natural language prompt binding, and registry audit architecture envisioned for modern Indian law chambers. As a law student, I successfully "vibe-coded" this high-fidelity frontend UI prototype to demonstrate the exact workflow.. If you are interested in partnering to connect this frontend to a functional backend, or if you have any doubts or questions about how the legal scrutiny works, please ask me!