Gnomon is the venture inside Pragticality Ltd that holds a continuous reading of where in-house trade teams' classified portfolios sit against the regulatory record. The metaphor is the design brief.
A gnomon (from the Greek γνώμων, "one who knows" or "indicator") is the part of a sundial that casts the shadow. It does not announce the hour. The reader reads the dial and tells the time.
The name describes the product exactly. Gnomon shows where the regulatory shadow falls on a customer's portfolio. The customer's compliance team reads what that means and decides what to do.
The name was settled in May 2026 after a wide-ranging search through Latin and Greek roots in four naming territories — continuity, truthfulness, custody, and navigation. Gnomon was the only finalist whose etymology mapped exactly to the refined positioning: the trade governance support layer for global enterprises. A support layer points; it does not decide.
A continuous regulatory monitor and portfolio mirror for in-house trade teams. The product holds two things side by side — the live regulatory record (BIS, CBP, WCO, FTAs, sanctions lists, dual-use registers) and an in-house team's classified product portfolio — and surfaces every place the two have drifted apart.
It covers three streams in one workflow: Harmonised System (HS) classification, Country of Origin (COO), and Export Control Classification Number (ECCN). It treats jurisdictional layering as structural truth — multiple regulatory regimes evaluated in parallel against the same physical product — rather than as a feature added later.
It is decision support, not a decision engine. The compliance work — the verdict, the change request, the audit trail — remains with the customer's team, as it must.
The result, for the compliance director who owns the portfolio: less uncertainty about where it stands between audits.
Not a faster classifier. Most AI classification tools optimise for speed on a single new product. Gnomon is built for the opposite problem: keeping a portfolio that has already been classified right, as the regulations around it move.
Not an autonomous compliance system. Gnomon never amends a classification on its own. Every change goes through the customer's review and change-control. If the system claims a code without a human approving it, the audit defence collapses — so the system doesn't do that.
Not a broker tool. Customs brokers file shipments. Gnomon is for the in-house compliance director who owns the portfolio and gets audited later.
Not a master-data system. Gnomon does not replicate the customer's ERP or PLM. It holds the classification-relevant attributes — the ones that drive HS / COO / ECCN determinations — and reads the rest from the customer's existing systems through defined ingestion paths.
Not selling certainty. Regulatory drift is a probabilistic surface, not a binary one. Gnomon flags grey-edge classifications for expert review rather than pretending to know.
Gnomon is a venture inside Pragticality Ltd — a UK private limited company, registered in England and Wales (No. 17207406), privately held and independently capitalised. The company holds and operates a focused portfolio of ventures; each carries its own brand, its own customer relationship, and its own commercial logic. Gnomon is Pragticality Ltd's trade compliance support solution.
Customer contracts and revenue belong to Pragticality Ltd. The Gnomon brand stands on its own. The two coexist as parent and venture with deliberate separation.
For context on the operating principles that shape what we build and how — sustainable economics, family-bandwidth as a constraint, helping-people as the prime mover, no venture capital, no growth pressure that distorts the work — see pragticality.com/about.
Gnomon is in customer-validation phase. The application runs on Pragticality-managed infrastructure for demo and design-partner work. Design-partner conversations are open with mid-market trade compliance directors who recognise the problem and want to shape what gets built. As the product matures, deployment will follow customer demand — including options where Gnomon runs inside the customer's own environment for the most security-sensitive cases.
Most established trade-compliance tools default to one of two assumptions — either the EU regime is the master and everything else is a satellite (typical of EU-built tools), or the US regime is the master (typical of US-built tools). A manufacturer with operations across multiple jurisdictions — GB, Northern Ireland, EU, US, or any other parallel combination — lives in a reality that neither assumption serves.
Gnomon treats jurisdictional layering as structural truth, not as a customisation. One product. Multiple regulatory frameworks evaluated in parallel against the same physical product. The architecture was sharpened in the four-track post-Brexit reality because that is the daily picture for the customers we know best — and the same design extends naturally to any combination of regimes a manufacturer needs to satisfy.