Define the records, relationships, lifecycles, forms, and actions your organization needs. Keep shared meaning while extending what makes your operation specific.
Define identity, typed properties, units, and relationships that describe real concepts in your operation. A material, lot, result, and procedure can stay distinct while remaining connected.
Establish lifecycle states, allowed actions, review routes, and prerequisites alongside the record type. The rules shape what people can do, not just what a form looks like.
Build on common foundations and industry concepts, then add local terminology, properties, and governance. Keep the source of each extension visible.
Keep a draft model change separate from the active type and the records created under it. Assess its consequences for forms, actions, verification, and existing work.
A shared property carries its meaning, data type, unit, permitted sources, and validation rules. Map equivalent properties deliberately and surface potential duplicates without forcing different business concepts into one field.
This is the Material entity definition. It shapes material records and their forms; it is distinct from editing any one material record.
Interface reference · sample recordsRequiring a witness on every record is a type-level rule. Revising the instructions in one approved recipe changes that specific record. Helix keeps those layers explicit.
Choose a template, shape your workspace, and try the work for yourself. The sandbox is free forever.