The Registration Architecture
How independent layers produce one coherent experience.
In screen printing, registration is the alignment of independent color plates into one coherent image. Each plate carries its own ink, its own screen angle, its own density. You build them separately. You print them in sequence. The image only exists when the plates combine. If one plate shifts, even slightly, you see the gap between what was intended and what printed.
I’ve worked with this principle since USA Tees in Brooklyn, where I did color separation and production in the art department. Halftone screens at specific angles, registration dialed by hand, ink density controlled plate by plate. You never work on the image. You work on a channel. One color at a time, decomposing a whole into discrete layers that reconstruct it when they register.
That’s how I’ve built everything since.
The registration architecture is the principle applied across domains. Independent layers, built and maintained separately, producing one coherent experience when they combine. Misalignment between any two layers is visible to the person receiving the result, even if they can’t name what’s wrong.
At Aiden Jae, four layers register: photography (proving the quality through honest light), identity (visual language derived from the materials), platform (Shopify architecture that serves the brand instead of overriding it), and packaging (physical materials that continue the story the photography started). Each layer is independent in construction. The photography can be updated without rebuilding the platform. The identity can evolve without changing the packaging. But they’re interdependent in experience. A customer who receives the package feels the same brand they saw on the screen, because the layers register.
At Encore, three layers register: back-end logic (decades of recruiting intelligence), front-end presentation (modular JS framework and SCSS design system), and information architecture (how a recruiter navigates the platform). Each layer evolves at its own speed. The back-end adds capabilities. The front-end presents them. The IA bridges both. Twelve years of maintaining registration across three independently evolving layers.
At New City, three layers register in prose: story (what happens), narrative structure (what the structure is doing to the reader’s understanding), and reader experience (what the reader’s body does). Misregistration between layers produces the same result as misregistration between color plates: the reader feels something is off before they can name it. A claustrophobic story moment rendered in expansive prose sends a contradictory signal.
The architecture is medium-independent. Photography and code. Front-end and back-end. Plot and rhythm. Different materials, same structural principle: independent layers, built separately, registered together, misalignment visible.
The value of thinking in registration instead of coordination is the diagnostic it provides. Coordination asks: did the teams communicate? Registration asks: do the layers produce one coherent experience? A project can be well-coordinated (all departments talked, all deliverables shipped on time) and still misregister (the photography contradicts the platform, the voice says one thing and the code says another). Registration is the test. Coordination is just the process.
Every project I evaluate through the Formwork Protocol is a registration problem. The structural plate and the narrative plate are independent layers. They run separately. They produce independent verdicts. The convergence mapping is where I check the registration: do the plates align, or is there a gap between what the structure says and what the identity says?
The whole only exists when the layers register. The plates have to line up.