Model accepted entities, relationships, state, source identity, and the operational context needed for a decision.
An illustrative operational model
Accepted records and relationships show which customer, order, inventory, and response options matter to the situation.
Illustrative workflow view. Controls and integrations depend on deployment.
Describe the entities, accepted relationships, and current state that a workflow needs. Begin with enough context for one complete operating loop.
Keep identity candidates, conflicts, and lineage visible. Proposed relationships go through review before becoming accepted operational context.
Supply the records, visibility constraints, and action context needed to evaluate a response and understand what that response could affect.
In practice
An isolated record rarely explains the whole decision. Lattice connects accepted objects, relationships, and state so operators can see the relevant commitments and constraints.
Connect a delayed shipment to its order, customer, carrier, and inventory. The decision begins with the affected commitment and available alternatives, rather than a carrier event viewed on its own.
Link an equipment condition to the production work and maintenance responsibility around it. Give the reviewer the relationships needed to assess a response and the work that response may affect.
Model the resources and handoffs involved in an operating workflow. For a capacity exception, show the accepted state and relevant relationships before teams compare reassignment or escalation options.
How it works
Begin with the objects and relationships the chosen workflow requires. Expand the model as additional operating decisions make the need clear.
Define the records that matter, such as orders, shipments, resources, and commitments. Establish how each source record refers to an accepted business object.
Resolve identity candidates and conflicts before treating them as accepted context. Proposed relationships remain subject to review rather than silently becoming operating truth.
Bring the relevant state, relationships, visibility constraints, and action context into the decision. Keep a path back to source identity and accepted evidence.
Common questions
The product role is accepted operational context: objects, identity, relationships, and state used by decisions. A visualization can help people inspect that context, but the operating model is the foundation.
No. Relationship proposals go through the review boundary before becoming accepted context. A finding can inform review without changing the underlying operating model.
Strata governs datasets and their use. Lattice models the accepted business objects and relationships those records describe, then supplies the scoped context a decision needs.
Explore further
Adoption starts with one workflow, the systems around it, the approvals it needs, and the outcome your team wants to improve.
Design a decision loop