Glages: Company Connection Makes a Common Model Operational
A reusable model cannot assume that every company stores the same data, uses the same software, or names the same states in the same way. At the same time, company differences should not force the process itself to be redefined for every implementation.
Company connection separates these two problems.
The Common Model
The reusable model defines the stable meaning of the activity.
A delivery model, for example, may define a shipment handed over for transport, movement toward a recipient, intermediate carrier states, delivery attempts, and final delivery results. Those meanings remain common even when carriers, tracking formats, and internal databases differ.
The model should not depend on a field called delivery_status or a particular carrier code. Those are local representations.
The Mapping Layer
A company connection identifies how the model exists in one organization.
It defines:
- which records represent the model Entities;
- which system is authoritative for each fact;
- which fields represent relevant states;
- which API performs a permitted change;
- which roles possess authority;
- which local parameters affect rules;
- which execution mechanisms are available.
The connection may map several company records to one model Entity or one local field to a more precise modeled state. It may also reveal that the company does not currently possess a required fact or execution mechanism.
Connection Is Not Custom Redefinition
This distinction protects reuse.
When the local implementation is allowed to redefine the process, every customer receives a different model and corrections cannot easily return to a common library. The asset becomes a collection of consulting projects.
A company connection may supply parameters and mappings, but it does not change the common meaning without an explicit model revision.
If a company has a genuinely different process, that difference must be represented deliberately. It may require a domain extension, a permitted variation, or a new model. It should not be hidden inside an integration.
A Readiness Test
Company connection is also a practical way to test automation readiness.
The common model may require an authoritative delivery attempt record, but the company may only store free-form notes. It may require a defined refund authority, but the organization may rely on informal employee judgment. It may require an API for a permitted change, but the current system may only support manual entry.
These findings are valuable. They show exactly what prevents controlled automation.
The Operational Path
The complete path is:
licensed model
→ company connection
→ product implementation
→ verification
→ controlled execution
→ traceable result
The buyer does not receive a generic document and then reconstruct the domain again. The buyer receives a formal model and maps it to the real environment.
Once connected and verified, different execution mechanisms can operate inside the model: conventional code, external services, bounded LLM tasks, or approved human steps.
Company connection makes a common model operational without turning every company into a new definition of the process.