Connect — for MIS and ERP modules
A print MIS that speaks PTPGE — a vendor declaration out, a request in, a quote out — connects to GutenLex with one address and one key. GutenLex never reads your MIS's own formats and never writes into your system: it carries requests to you and quotes back to the buyer, with the configuration identity checked at every step.
The printer has a Vendor Profile on GutenLex and a vendor key (glx_vp_beta_…, shown once at first publish; rotatable). The key identifies the printer in every call — the module acts on the printer's behalf, with the printer's consent. vendor_id is the profile id (vp_…), not the PTPGE register slug.
Your module writes a vendor-declaration/1: what the printer can make, in PTPGE terms, no prices. Push it and it becomes the printer's public declaration — the one buyers and agents are matched against.
fingerprint.spec and fingerprint.request are recomputed from the stored request; inReplyTo.fingerprint must equal the spec; the quote's own configuration must serialise to the same spec — nothing re-keyed.
vendor must be this printer's register identity (https://ptpge.org/v1/vendors/…); fingerprint.offer, if stated, must equal request + variables/order/vendor.
Price, currency, validity, lead time and quantity are read from the quote/1 and shown to the buyer as your offer. Rejections come back as 422 {valid:false, errors[]} in the same wording as the PTPGE Ready validator.
Connecting means: the printer lets this software publish its declaration on GutenLex, receive the printer's quote requests, and file quotes in the printer's name. GutenLex stores the declaration, the requests and the quotes; it stores no MIS data and no credentials beyond the printer's own vendor key. Disconnect at any time by rotating the vendor key in the Vendor Profile — every connection using the old key stops.