Proofs Now

A shop publishes its customer a versioned proof of the artwork and specs. The customer reviews it on a shareable page and approves or rejects, and has to explicitly accept any flagged acknowledgments before an approval is allowed. Every published version is frozen as an immutable record, so there is never a question about what the customer actually signed off on.

That last part is the whole point. Most proofing disputes aren't really about the artwork; they're about what was understood at the moment of approval. Production caveats and standing terms get buried in fine print, and "I didn't see the disclaimer" stays permanently available as an answer. Making acceptance a gate instead of a footer closes that door.

Delivery is deliberately hybrid. The shop-facing workflow runs entirely through a Model Context Protocol server, where the tools are the product, so an agent can run a shop's proofing end to end. The customer-facing surfaces are real web UIs over that same service layer. One source of truth, many front ends.

I'm building it against FASTSIGNS of Irvine first, because a tool for sign shops should be shaped by a sign shop rather than by a guess about one.