The word type comes from an Indo-European root meaning “to mark,” “to stamp,” “or to make an impression.”
This is precisely how the practice should be understood in the many ways we continue to implement it as a vast “technological” civilization, up to the present day.
Typecasting is simply the scaling up of the outputs from a given workflow system, usually a manual one.
The internal steps of casting any given type in a given type system can be broken down into any number of stages, which is just a set of ordered steps.
Each internal stage type can then be broken into at least two substages: with at least one being analytic, the other synthetic. One of evaluation. or typing, the other of assertion, or casting.
The evaluative and assertive substages can then be split up and broken out across the typecaster’s overall type system, which then executes them in the specified order.
To outside observers, the casting (or “printing” or “output”) of a given object of a given type in that type system will always appear as one item or unit. A singular object, produced out of whole cloth.
Only the typecasters themselves know all the tricks and turns, all the stages and steps that click and flow together in order to make everything work underneath.
(Aside: you can also substitute the given type systems within an entire type flow, or surject entirely different type flows in their place! But of course, this level of abstract typecasting is only for highly advanced typecasters.)