Engineering basis
Record the source context, evaluation scope, supporting evidence, and unresolved questions.
02 / Evidence
A savings estimate is useful only when the decisions beneath it can be inspected. GaugeID connects management rollups to bounded engineering evidence without pretending that a technical result is already a financial outcome.
From record to operating value
GaugeID separates what is computed from what the business can act on. That makes both the engineering review and the management rollup more credible.
Record the source context, evaluation scope, supporting evidence, and unresolved questions.
The authorized engineer, quality lead, or configuration owner decides what action the evidence supports.
Customer-owned time, cost, demand, supplier, and lifecycle inputs translate decisions into planning value.
A defensible boundary
GaugeID supports a conclusion only within its declared policy and only when the recorded basis is sufficient for that scope.
An open question stays visible. Release, purchasing, source-of-record, and disposition actions remain with the people and systems that own them.
Technical contracts
This distinction matters to technical reviewers. GID2 and GID3 have separate purposes, and neither is allowed to inherit the other’s claims.
Public claim registry
These statements are deliberately narrower than the product’s long-term ambition. Their limits are part of the statement.
The public value model calculates illustrative potential from editable visitor assumptions; it does not establish customer savings or GaugeID performance.
planning_context_onlyimplemented_factThe browser component exposes every input and formula, stores nothing, and labels its output as potential value before program cost.
Generative and learned retrieval systems may produce or prioritize candidates, but those outputs do not independently establish an engineering identity conclusion.
bounded_evidence_onlygoverning_product_contractGaugeID product policy keeps generation and ranked retrieval outside the authority boundary for engineering identity and owner action.
GaugeID may organize engineering evidence for a medical-device comparison, but it does not decide whether the FDA substantial-equivalence standard is met or grant regulatory clearance.
bounded_evidence_onlygoverning_product_contractFDA’s 510(k) framework assigns the regulatory decision to FDA and calls for comparison of intended use, technological characteristics, performance, and other applicable device characteristics.
GID2 carries deterministic, policy-scoped engineering evidence and does not independently authorize an owner decision.
bounded_evidence_onlygoverning_product_contractGaugeID evidence policy requires each packet to state its scope, limits, and relationship to owner-controlled decisions.
GID3 is an archival reconstruction container for its declared exact contract, not an identity verifier.
archival_reconstruction_onlygoverning_product_contractThe GID3 contract separates source-byte or strict-mesh reconstruction from GID2 evidence and grants no owner-decision authority.
When available evidence does not support a bounded conclusion, GaugeID records an unresolved outcome rather than overstating certainty.
bounded_evidence_onlygoverning_product_contractThe product contract requires a visible unresolved state and keeps the next consequential action under owner control.
A SHA-256 digest can bind a file’s exact byte sequence.
content_commitment_onlycryptographic_propertyThe browser demo hashes the full local ArrayBuffer with Web Crypto SHA-256.
07 / PILOT
Start with the workflow, evidence question, decision owner, and customer-native business inputs. The pilot establishes what can be measured—not what must be claimed.
Scope a Pilot