The document was filed by output, not by purpose
Agreement Sheets were reachable through Prints because they produce paper. That was technically understandable and operationally wrong. A salesperson thinks about the sheet while shaping the deal, not while browsing a library of print tools.
On August 6 we made Quote the owner. The route, navigation, and customer presentation work now begin from the same business domain as the payment structure and trade conversation.
The move exposed two separate products
The staff screen needs edit controls, private notes, and host actions. The customer presentation should receive only approved quote fields. Moving the feature forced that separation into the architecture instead of leaving it as a visual convention.
A shared link is therefore not the staff page with controls hidden. It is a separate server-written customer record with its own opaque identifier and narrower data set.
- Staff editing remains private
- Customer records contain approved fields only
- Public identifiers do not contain customer information
- The shared view can expire or be revoked
The browser and PDF must tell the same story
Relocating the feature also made layout drift obvious. The screen, customer view, and exported PDF need the same information hierarchy even though their controls and page sizes differ.
That means page-break behavior, annotations, totals, and dealership-configured sections are part of the product—not a final print stylesheet pass.
Current status
Agreement Sheet ownership now sits with Quote. The public customer presentation remains a pre-alpha capability, and each rollout still requires domain, access, retention, and permission checks before use.