6 entries tagged Interchange.
Nobody marks a Secure Job Envelope traveler "ready." The file earns each level by containing what that level needs, and both implementations compute the same answer. The rulebook — what each level requires, the four guards on quoting and awarding, what an amendment does, why an awarded job locks, and what a level is not.
A fingerprint is only useful if every program computes the same one, and JSON gives you a dozen ways to write the same data. The Secure Job Envelope's canonical form, rule by rule — key order, the number range, cents instead of decimals, strict dates — and the real bug one shared test file caught on its first run.
Earlier posts called it a fingerprint. This one opens the hood — exactly which fields of a job go into the Secure Job Envelope's hash, which are deliberately kept out, why a quote survives an award but not an amendment, and the three things a hash is not.
The Secure Job Envelope, walked through one job from the public examples — a CNC bracket composed by a buyer, quoted by one shop, amended, re-quoted by another, awarded, and locked. What each side sees at each step, and why a change as small as the shipping terms sends the first quote back to the start.
Why a job between two shops should be a file both of them can check — not a portal, not a network, not a PDF. Five design decisions behind the Secure Job Envelope, each one a problem we kept seeing on the order desk, and what each one costs.
Every rung of this ladder stops at your wall. The plater, the heat treater, the shop that takes your overflow — the job still leaves as an email, a PDF, and a phone call. The Secure Job Envelope is our answer — an open file format for a job, with the honest list of what it does and doesn't do yet.