Formalizing Materials R&Dmodular reference
Home/Materials reference/Processing: the unit operations
Materials reference · Part 2 of 9

Processing: the unit operations

Paint-making as a pipeline of stateful operations on one mutable batch: mixing, dispersion, let-down, application, drying, curing — order-dependent and partly irreversible.

~15 min read P1P2

A finished coating is not built from its ingredients the way a sum is built from its terms. It is built the way a final program state is built from a trace of mutations: one batch is pushed through an ordered sequence of operations, each reading and rewriting a single hidden internal state. The recipe fixes only the starting arguments; the trajectory — what order, how hard, how hot, how long — is where the product is actually made or destroyed. This module treats each unit operation as a morphism on that state, and shows why two of those morphisms, drying and curing, have no inverse.

The pipeline: operations as morphisms on one hidden state

Think of the batch as a single large mutable object passed by reference down a pipeline. Each unit operation — a named processing step like mix, disperse, coat — is a function f: State → State that reads the current state and writes a new one. The finished material is the composite

\[\text{coating} = (f_n \circ \dots \circ f_2 \circ f_1)(\text{raw materials}),\]

read right-to-left: do \(f_1\), then \(f_2\), and so on. The catch is that these are nothing like pure functions: they have side effects on a state far richer than the ingredient list, many do not commute (\(f \circ g \neq g \circ f\)), and several have no inverse.

Intuition. The “state” is not the bill of materials. It is the full internal configuration: how far the pigment clumps have been broken apart, the spread of particle sizes, which molecules have stuck to which surfaces, how uniform the batch is at each length scale, the current temperature, and the accumulated mechanical and thermal history. Composition picks the initial values and bounds the reachable state space; processing chooses the path taken through it.

The figure below is the canonical route. Note its shape: the early steps are in principle re-runnable, but the last two — dry and cure — are drawn as one-way valves. Once the batch passes them, there is no morphism back.

WeighMixDisperseLet-downCoatDry⊝ one-wayCure⊝ one-waya pipeline of stateful operations on one mutable batchorder matters (non-commutative); drying & curing are irreversible (P1, P2)
Processing as a pipeline of stateful operations (“morphisms”). Order matters and drying/curing are one-way (P1, P2).

In the synthesis. Every property you later measure is a downstream read of a state these operations wrote. The true input to performance is therefore recipe + full processing trajectory, never the recipe alone. This is the structural origin of P1 (path-dependence) and P2 (irreversibility): two plants running byte-identical recipes can ship different products because they ran different trajectories. You cannot QC a coating by re-checking its composition — you are validating a process. See the effectful process category for the formal home of this claim.

Bridge — to the math reference. This whole module is the bench-level reading of two abstract objects. The composition law “\(\circ\), but do not assume you can undo” is a monoid, not a group — see monoids vs. groups, where order-sensitivity is non-commutativity and irreversibility is failure of cancellation. The “single hidden state every operation threads through” is the runtime wire of an effectful (premonoidal) category: because both of two “parallel” operations touch that one wire, they are secretly in series and may not be reordered. Here you see what the wire actually carries; there you see why touching it forbids reordering.

Order of addition: the purest non-commuting write

The first place order matters is the most banal-looking: weighing and charging — what goes into the vessel, and in what sequence. This is the textbook order-dependent writes to shared state problem: as with two threads writing the same variable, what a pigment or surfactant “sees” on entry depends on what is already in the pot.

The reason is physical and sharp: surfaces are a scarce, first-come-first-served resource. A dispersant (a molecule that coats fresh particle surface so particles repel rather than re-clump) added before the pigment can adsorb onto new surface as grinding exposes it; added after the particles have flocculated, it may never reach the now-buried surface. Likewise, adding water to concentrate versus concentrate to water can land on opposite sides of an emulsion’s phase inversion (the abrupt flip of which liquid is the continuous one). None of this is visible in the bill of materials.

Pitfall. The recipe is a set of ingredients; the process needs a sequence. You cannot safely re-derive the order from the ingredient list — order is an independent degree of freedom to be recorded, not inferred. “Add A, mix 10 min, then add B slowly over 5 min while cooling” is part of the answer, not packaging. This set→sequence map is P1 in its purest form (see the abelianization — “forget the order” — for exactly what gets thrown away).

Building the dispersion: mix, wet, grind

The heart of paint-making is converting dry pigment clumps into a stable suspension of fine particles. It is three distinct operations that are easy to conflate.

Mixing — uniformity at two length scales

Mixing distributes components so concentration becomes uniform — but “uniform” is scale-dependent, like coarse versus fine load-balancing. Macro-mixing is getting work onto every node: bulk circulation with no dead zones. Micro-mixing is interleaving at the finest granularity: molecular-scale contact, where any reaction or adsorption actually happens. Good macro- with poor micro-mixing looks globally balanced yet starves at the hot path. A reaction fast relative to mixing becomes mixing-limited — its outcome is set by the stirring, not the stoichiometry. Crucially, blending (making it uniform) is not dispersing (breaking particles apart): you can blend without dispersing.

Wetting — establish the connection before transmitting

Wetting is replacing the air and adsorbed-gas layer on a solid surface with the surrounding liquid. It is the handshake before any data flows: no wetting, no mechanical coupling between liquid and particle. Dry pigment is an agglomerate — a loose cluster full of air pockets. Before mechanical force can pull particles apart, liquid (helped by wetting agents that lower interfacial tension) must penetrate the pores and displace the air. Wetting is the prerequisite of dispersion, not a synonym; a deliberate “wetting-out” hold before high-shear grinding is a real step, and skipping it sabotages the next stage.

Dispersion / grinding / milling — the energy-input step

Dispersion (equivalently grinding or milling) is intense mechanical energy applied to break agglomerates toward their primary particles (the smallest indivisible grains) and to stabilize them against re-clumping. This is the costly, non-idempotent transform that irreversibly rewrites the data structure — re-running it does not return you to the same place.

Equipment imposes the distribution. Mills differ by intensity, and each imposes its own shear-rate spectrum and residence-time distribution, hence a different particle-size distribution (PSD). A high-speed disperser (a sawtooth blade in turbulent flow) suits pre-mixes and easy pigments; a bead / media mill (energy delivered by bead-on-bead collisions) tackles hard agglomerates; a three-roll mill (very high, controlled shear in the roll gaps) handles stiff pastes and inks. The outcome is a distribution, not a number, and it trades off against color strength, gloss, transparency, and stability.

Pitfall. “Grind harder / longer = better” is false. Past an optimum, over-grinding degrades the very state you were building — excess heat, broken structure, damaged pigment. And the result is not portable: “disperse to fineness X” bundles equipment, intensity, and endpoint, and does not carry over to a different mill unchanged. That non-transferability is P7.

Millbase, let-down, and the histories the batch remembers

Dispersion is deliberately run as a two-phase build. You first grind a millbase — a concentrated pigment dispersion — then perform the let-down, a controlled dilution of that millbase into the rest of the formulation. The analogy is compiling one hot module under aggressive optimization, then linking it into the larger program.

You grind concentrated on purpose: a stiff, highly loaded millbase transmits shear to agglomerates far better, so particles actually collide and rupture. The let-down must then not destroy what grinding achieved — a wrong solvent balance or a shock dilution can cause flocculation (re-clumping of dispersed particles) or shock (sudden incompatibility), undoing the expensive step. Millbase composition and let-down sequence are first-class processing parameters, separate from the overall formula.

Two of the state variables the batch carries deserve naming, because they are memory.

Shear and shear history. Shear is the mechanical deformation rate the material experiences; shear history is the accumulated record of it. This is hysteresis and rate-dependent response: viscosity depends not only on the present shear rate but on recent shear, like a stateful filter whose output depends on past inputs. The signature phenomenon is thixotropy — viscosity falls under sustained shear and recovers slowly (often incompletely) at rest, so an up/down sweep traces a loop, not a line. The same formula taken to the same nominal endpoint under gentle versus intense shear ends in a different microstructure.

Pitfall. Treating viscosity as a single constant. Because the material has memory, when you measure matters; a viscosity reading without its shear rate and recent shear history is ambiguous and not reproducible.

Thermal history. The time–temperature path the batch follows — the materials analogue of annealing, where the path, not just the endpoints, sets the result. High-shear dispersion dumps mechanical energy as heat, so milling self-heats; uncontrolled, this thins the batch, degrades components, advances a reaction, or evaporates solvent. And thermal and shear histories are coupled: shear \(\to\) heat \(\to\) lower viscosity \(\to\) different shear. They cannot be tuned independently, and the coupling strength changes with scale — a clean instance of P8 (multi-component coupling).

From liquid to solid: application, film formation, drying, curing

Once the paint is made, it is laid down and frozen. Each step is its own morphism, and the last two are the irreversible ones.

Application / coating lays the liquid onto the substrate as a thin film, and each method has its own shear profile and geometry — an I/O path that also transforms the payload. Spray atomizes at very high shear, then levels; dip ties thickness to withdrawal speed and viscosity; roll transfers through a nip; spin-coat flings excess off a spinning wafer (the microelectronics method); blade / draw-down sets a controlled gap (the lab workhorse). Because rheology is shear- and history-dependent, the same paint behaves differently across methods — a coating qualified by draw-down may misbehave when sprayed (P7 again).

Film formation is the state transition from a flowable phase to a fixed one — the point at which the mutable object is about to be frozen and can no longer be edited in place. It can proceed by solvent loss alone, by particle coalescence (waterborne latex spheres deforming and fusing, typically only above a minimum temperature), and/or by chemical crosslinking. The order in which surface versus bulk solidify decides the final geometry and defects.

Definition (Drying). Loss of volatile liquid (solvent or water) from the film — physical drying, as distinct from chemical curing.

Drying is an irreversible, lossy map, like quantizing or hashing: the wet state is destroyed and adding solvent back does not restore it — you get a ruined film, not the original. A characteristic defect, skinning, is an artifact of the drying path: the surface dries faster than the bulk and traps solvent beneath (blisters, wrinkles, soft underneath). Drying rate is set by temperature, airflow, and thickness, so the same film dried two ways yields different structure.

Definition (Curing / crosslinking). Chemical reactions that bond polymer chains into a connected three-dimensional network, turning a liquid or soft film into a hard, insoluble solid.

Intuition (gelation = a percolation threshold). Picture the polymer chains as nodes in a connectivity graph and crosslinks as edges. Below a critical extent of reaction there are only finite clusters — the material still flows (a liquid, or sol). At the critical point a single connected component suddenly spans the whole sample — the gel point — and it stops flowing. This is exactly the giant-component transition of random-graph theory.

Curing forces a hard split between two material classes. A thermoset crosslinks into a permanent network: once cured it cannot re-melt or re-dissolve (heating only degrades it). A thermoplastic keeps its chains independent, so it softens and re-flows on heating. Curing also starts two countdown clocks, both triggered by an irreversible reaction: pot life (after mixing a two-part system, the working time before it gels) and open time (after application, how long the film stays workable). Miss the pot life and the batch is scrap — you cannot un-gel it.

Pitfall — two traps in one. First, “dry to the touch” (solvent largely gone) is not “fully cured” (network formed); they are different states. Second, more cure is not always better. Cure degree depends on the cure trajectory (temperature, time), and over-cure (embrittlement, discoloration) is a genuine failure, symmetric with under-cure — both hidden inside a recipe that merely lists the crosslinker.

Finally, aging and weathering is slow state drift after deployment: residual cure continues, and UV plus oxygen drive photo-oxidative chain scission and crosslinking, while moisture and thermal cycling stress the film — chalking, yellowing, gloss loss, cracking. “Initial” and “weathered” properties are different reads of an evolving state; specifying one does not pin the other.

Irreversibility, equipment dependence, and why scale-up breaks

Three consequences follow once you accept that operations are stateful, non-commuting morphisms.

Irreversibility (P2) — the points of no return. A step is irreversible when no operation restores the prior state: the map is many-to-one or destroys structure, so no inverse exists. The effectively non-invertible steps are drying (volatile phase and wet microstructure gone), curing / gelation (one-way sol→gel), skinning (surface-first artifact), and irreversible aggregation / coalescence (gentle stirring will not restore the dispersed distribution). Each discards a degree of freedom and lands in a state reachable from many priors — so the prior cannot be inferred from the result.

In the synthesis. Irreversibility is P2, and it is why order (P1) is consequential: an irreversible step locks in whatever the preceding order produced. There is no rollback, no checkpoint-restore mid-pipeline — a mistake before an irreversible step is permanent, and you cannot reverse-engineer the process from the finished film alone. Knowing which steps are points of no return is what tells you where tolerances must be tightest and where rework is impossible. Algebraically this is the failure of cancellation of the process monoid: a step that drives every input to the same finished state erases the distinctions before it, exactly as drying-to-completion does. This is also why the right model is a monoid, not a group — and why “performance is a functor” (RD1) must be defined on the effectful process category, which carries the hidden state on its runtime wire, rather than on a commutative one.

Equipment dependence. The outcome depends on the specific apparatus — its geometry, intensity, and transfer characteristics — not only the nominal recipe and setpoints. This is the “works in sim, fails on hardware” problem: identical code (recipe) and config (setpoints) behave differently on a different mill or impeller because the hidden dynamics differ. The same millbase reaches different PSDs on a disperser versus a bead mill versus a three-roll mill. Setpoints like rpm and time are not transferable; the achieved internal state is what matters, and it is machine-specific. The process record must therefore name the equipment class (or its transfer characteristics), not just the dial readings.

Scale-up (lab → pilot → plant). Transferring a process to larger scale while preserving the product is the controller-tuned-in-sim-fails-on-hardware failure, driven by physics that scale with size. The core problem: different physical quantities scale with different powers of size, so you cannot hold them all constant at once. Volume grows as \(L^3\) but surface area only as \(L^2\), so heat transfer per unit volume falls as \(L^{-1}\) — a reaction that stayed cool in a flask can run away in a reactor. Mixing balance shifts (a step not mixing-limited in the lab becomes so in the plant). Shear becomes non-uniform — intense near the impeller, weak far away — so the distribution of shear histories broadens. Holding tip speed constant changes power per volume; holding power per volume constant changes tip speed. You must choose which invariant to preserve, and the others drift.

In the synthesis. Because heat, mixing, and shear scale differently, the trajectory — and thus the hidden microstructure and performance — changes even with recipe and setpoints fixed. That is P1 (different trajectory), P7 (non-transferability), and P8 (coupled effects) at once, and it is precisely why “it worked in the lab” is not a guarantee. Scale-up is not a copy operation: it is a re-derivation of the trajectory needed to hit the same internal state on bigger hardware — the most concrete possible demonstration that recipe alone never specifies a product (RD1/RD2).

Recap

  • Operations are morphisms on one hidden, mutable state. The product is the composite over the full trajectory; composition sets initial values, processing sets the path. The true input to performance is recipe plus trajectory.
  • Order matters (P1). Charging order, mixing, and shear/thermal history are independent, order-sensitive writes to shared state — surfaces are first-come-first-served, and the set→sequence map is where performance is made or lost. Record the order; do not infer it.
  • Drying and curing are one-way (P2). Drying is a lossy map; curing crosses a percolation threshold to a spanning network (the gel point) and a thermoset cannot return. There is no mid-pipeline rollback, so an irreversible step locks in whatever order produced.
  • Two histories are memory. Shear history (thixotropy, hysteresis) and thermal history (annealing-like) are coupled state variables — viscosity without its shear history is meaningless.
  • Equipment and scale are part of the process. Setpoints are not transferable (P7); quantities scale with different powers of size (P8), so scale-up re-derives the trajectory rather than copying it.
  • The math. Processing is a monoid, not a group (compose, do not assume undo); the hidden state is the runtime wire of an effectful process category, the home of P1, P2, and “performance is a functor” (RD1).

Part of a four-document set: the ARiSE draft (problem + AI solution), this modular Materials-science reference, the companion math reference, and the synthesis. Generated from modular Markdown with a custom static-site builder.

Mathematics is typeset with MathJax (loaded once from a CDN with Subresource Integrity; needs network on first view). Diagrams are inline SVG and follow the light/dark theme. Keyboard: / search · [ ] prev/next · t theme.