Task 2: Construction Contract Pack & Contractor Estimate App - #114
Open
shivansh193 wants to merge 2 commits into
Open
Task 2: Construction Contract Pack & Contractor Estimate App#114shivansh193 wants to merge 2 commits into
shivansh193 wants to merge 2 commits into
Conversation
Built against the real, hosted SuperDocs product: uploads a Master Subcontract Agreement, opens a Change Order/RFI/Payment Application into the same multi-document session, and drafts each with targeted chat instructions that read the base agreement's actual content rather than guessing its clause numbers. Verified programmatically, not asserted: the exported Change Order and Payment Application cite the base agreement's real Article numbers, checked against the base agreement's own text after export. Built with a script, not a GUI -- this card's minimum contract (upload, chat, approve, export) is fully demonstrated by a machine driving the flow end to end, which is the stronger proof for "a machine can drive it" anyway.
A small FastAPI + form UI -- this card's site-visit data entry genuinely wants a form, unlike Build 1's script-only flow. Site notes plus a photo and caption per issue in; SuperDocs uploads each photo, drafts a branded itemized estimate against the letterhead template, and exports. Each priced line item embeds the exact photo that justified it, not just a mention -- verified against a real run where both photos (only one was required) landed correctly. Also fixes an export-time durability gap found after shipping: SuperDocs' image upload returns a 24h signed URL, so the draft's embedded image reference could go stale by the time of export. Export now re-uploads the original photo bytes fresh immediately beforehand, decoupling export correctness from how long ago the photo was first uploaded. See PROGRESS.md for the full investigation, including a wrong assumption caught before it shipped and corrected by direct inspection instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Shivansh Kalra
Two builds against the real, hosted SuperDocs product for Task 2 of the hiring round.
use-cases/shivansh193/construction-contract-pack) -- drafts a Change Order, RFI response, and Payment Application against a base agreement, with terms traced back to their source document rather than invented.use-cases/shivansh193/contractor-estimate-app) -- generates a branded, itemized estimate where each priced line item genuinely embeds the site photo that justified it, verified by unzipping the exported.docxand confirming real embedded image bytes (not a link to SuperDocs' 24h signed URL).Each folder has its own README with setup instructions, SuperDocs features used, and verified results.