Glages: What the Model Factory Produces
A factory is defined by what comes out of it. Glages produces reusable formal models of business processes and business domains for AI automation.
That sentence matters because the product is not an agent, a workflow, or a consulting project. The product is a model that can be checked, reused, connected to different companies, and used as a software foundation.
The factory produces three connected layers: reusable process models, composed business-domain models, and company connections.
Reusable Process Models
A reusable process model describes a process that appears in many industries. Payment, refund, reservation, approval, shipment, delivery, claim handling, invoicing, repair, and document verification are examples.
The model defines the stable meaning of the process. It identifies the participating Entities, relevant states and relationships, required facts, applicable conditions, permitted actions, allowed changes, valid results, and stopping conditions.
A refund model, for example, must distinguish a refundable payment from an unrelated transaction. It must define whether the requested amount is available, whether a refund has already been completed, whether authority exists, and what results may be returned. Those questions arise in retail, hospitality, equipment rental, insurance, logistics, and many other markets.
The process remains recognizably the same even when companies use different databases, payment providers, policies, and field names. That common structure is what makes the model reusable.
Composed Business-Domain Models
A business is not one process. It is a connected system of processes whose states and results affect one another.
Glages composes reusable process models into larger business-domain models. An e-commerce model may connect order, payment, inventory reservation, shipment, delivery, modification, return, refund, claim handling, and customer service.
The value of the composition is not the presence of several models in one package. The value lies in their defined relationships.
A payment result may determine whether an order can continue. A shipment state may determine whether an order can still be modified. Delivery begins after shipment has handed the item over for transport and then tracks movement, attempts, and final delivery results. A refund may depend on both the payment history and the state of the order.
When these relationships are modeled together, the buyer receives a coherent foundation for an entire class of business rather than a collection of disconnected automations.
Company Connections
The common model must still operate inside a real organization. A company connection maps the reusable or composed model to the company’s systems, data, roles, parameters, and execution mechanisms.
It identifies which records represent model Entities, which systems are authoritative, which fields represent states, which APIs perform permitted changes, and which local parameters affect the rules.
The company connection does not redefine the process. It explains how the common process exists in one operating environment.
This separation is important. Without it, every implementation becomes a new version of the process, and reuse disappears. With it, the same model can serve companies that have different applications and technical infrastructures.
One Connected Product Hierarchy
The complete hierarchy is:
base concepts and relationships
→ reusable process models
→ composition of processes
→ composed business-domain model
→ company connection
The base layer gives models compatible meanings and relationships. Reusable process models define common activities. Composition creates a coherent business-domain model. Company connection makes that model operational in a specific organization.
The factory maintains these layers as software assets. Each verified model can be licensed, reused, combined, tested, and improved.
This is what the Glages Model Factory produces.