One Floor, Many Lines

Introducing Polymorphic Records Management

Walk onto almost any modern factory floor and you won't find one all-purpose machine that builds everything. You'll find lines — one line per product, each a specific sequence of stations bolted together in a specific order.

Look closer, though, and something interesting shows up: the individual stations are almost never built from scratch for each new product. They're pulled from a shared inventory of stations already designed, tested, and proven on other lines, then arranged into a new sequence and watched by the same kind of gauges the rest of the floor already trusts.

We call this pattern Polymorphic Records Management: one records lifecycle, built once, that behaves correctly no matter what kind of record is moving through it — a lease, a change order, an enrollment form, an invoice — without being rebuilt for each new domain. Everything below is really just what that means in practice.

A line for every vertical

Every industry we support — real estate, construction, a school co-op, a SaaS company running its own back office — gets its own line. We call that line a Domain App Pack. It's the boundary of the work: where this line starts, where it ends, and what counts as part of it versus part of some other line down the floor.

The routing is what makes each line different

A line isn't just a name — it's a specific path a record has to travel. A lease and a change order both roll off their own lines, but the routing through each one is different: different stations, different order, different people who have to sign off before the product moves to the next stage. We call that routing a Flow Pack. It's the actual sequence — the choreography — that a record follows from the moment it's created to the moment it's filed away.

The stations are shared across lines

Here's the part that would surprise most people watching a real factory floor: the stations themselves get reused constantly. A welding station doesn't get rebuilt for every new car model — it gets repositioned onto whichever line needs welding this quarter.

We call our version of that a Capability Pack: scheduling, CRM, accounting-lite, and others. The same scheduling station that handles showings on the real estate line also handles class scheduling on the school-coop line. The same accounting-lite station that tracks rent for a property manager tracks tuition for a school. Nobody re-engineers the station. It just gets bolted onto whichever line needs it.

The gauges tell you the truth

Every real factory floor is covered in gauges and dashboards — pressure readouts, throughput counters, alert lights — that don't move the product themselves but tell the people running the floor what's happening and where to look.

We call that an Intelligence Pack: a feedback loop sitting on top of a line, watching what moves through it — how many records are stuck at a particular station, where this week's bottleneck is, what needs a human's attention before it becomes a problem. The gauges don't touch the product. They tell you the truth about the line.

Same floor, two different lines

Here's what all four pieces look like side by side, across two industries we actually support:

Notice what's actually different between the two rows: the words. Everything else — the discipline of building a line out of shared stations, the fact that the same scheduling and accounting stations show up in both rows, the way gauges get mounted the same way on every line — is floor infrastructure we built exactly once.

Why this is a business advantage, not just an engineering one

• Speed. A new vertical rarely means inventing new stations. Most of the time it means arranging stations that already exist — scheduling, CRM, accounting-lite — into a new routing, and building only the pieces genuinely new to that world.
• Reliability. A station gets battle-tested on every line it's installed on. Fix a bug in the scheduling station because a construction crew found it, and the school-coop line gets that fix for free — it's the same station.
• Visibility. Because every line reports through the same kind of gauge, a brand-new industry is never a blind spot. Its dashboard looks and works like the dashboard for a line we've run for years, because it's built from the same pattern.

The objection, and the honest answer to it

"A school enrollment form really isn't a real estate lease." Correct — and that was never the claim. The routing is genuinely different for each vertical, because the work genuinely is different. What's shared is the discipline of building any line out of the same kind of stations, and the gauges that watch every line the same way. The parts that are actually novel about a new industry are usually smaller than people assume, because most of what a line needs is already sitting in the parts bin.

The line to remember

You don't build a new factory every time a new product shows up. You build a new line — using stations you already have, watched by gauges you already trust.

That's Polymorphic Records Management. If you want the fuller architectural picture behind it — the systems-thinking model underneath the factory floor, plus a full case study walking the same pattern through legal, education, construction, and membership organizations — it's covered in Volume 6 of our book series, Composable Systems Architecture.

Richard Roberts is the founder of DataPublisher LLC. He's spent thirty years building the kind of shared infrastructure this piece describes — the parts bin every new vertical gets to pull from instead of starting over. He lives and works in McKeesport, Pennsylvania.