Oral history from the architects. Touch engineering. The path to emptiness.
This is not from documentation. It's from conversations with the people who built these systems -- first-hand oral history from Joey Castillo, who sat with these architects, worked with their code, and shipped on their platforms for 20+ years.
Four sources. Four engineering disciplines. One truth.
"Manny was all about counting touches. That's why servers loved Aloha. He was a satellite engineer. He was an engineer."
-- Norman Campbell, Javelin Era
Manny Negreiro (Emmanuel) came from satellite engineering before building Aloha at IPC/Aloha Technologies. Satellite engineering is about one thing: signal path efficiency. Every signal has a cost -- power, latency, error rate. You minimize the path between transmit and receive. You eliminate every unnecessary hop.
Manny applied satellite signal-path thinking to POS. The touch is the signal. The action is the receive. Every touch between the server and the completed action is latency. Every unnecessary touch is wasted signal. Every extra screen is a hop that degrades throughput.
This is why servers loved Aloha. Not because of the colors. Not because of the layout. Because it took fewer touches to do the same thing. A server who saves 1 touch per item across 200 items per shift saves 200 touches. That's 200 moments they're looking at a screen instead of looking at a guest.
| Design Decision | Touch Cost | Signal Logic |
|---|---|---|
| Seat-based ordering | +1 per seat change | But eliminates re-asking "who had the salmon?" at delivery -- saves touches downstream |
| Modifier popups | +1 per modifier | But captures the conversation in real-time. No return trip to the table |
| Floor as home screen | 0 (default view) | The server's most frequent action is "which table needs me?" -- make it the zero-touch view |
| Color = status | 0 (visual, no touch) | Red/green is processed pre-consciously. No reading, no thinking, no touching to check status |
Manny's genius: he counted touches end-to-end, not per-screen. Adding a touch on the order screen that eliminates 3 touches at delivery is a net savings of 2. Satellite engineer math -- total path cost, not per-hop cost.
| Workflow | Aloha TS | Aloha QS |
|---|---|---|
| New order + 1 item + pay | 5 | 3 |
| 4 items + fire + pay | 11 | 7 |
| Void last item | 1 | 1 |
Soul: Minimize total path cost. Every touch must justify its existence across the entire service lifecycle, not just the moment it happens.
MICROS came from a different world. Where Manny was a satellite engineer and Peter was a C programmer, MICROS was a systems company. Founded by A.L. Giannopoulos in the late 1970s, MICROS Systems built the 3700 series as enterprise hardware+software. The terminal WAS the product. The software served the terminal.
MICROS's insight was different: the operator shouldn't make decisions. The system should be pre-configured so the operator just follows the path. Function keys are pre-programmed. SLU (Screen Look Up) grids are pre-built by management. The operator doesn't navigate -- they execute.
This is a different kind of touch optimization. Manny minimized touches for the server who thinks. Peter eliminated latency for the operator who needs speed. MICROS eliminated decisions for the operator who follows procedure.
| Design Decision | Operator Impact | Configuration Logic |
|---|---|---|
| Function key rail | Every action is 1 touch | Management pre-assigns actions to positions. The operator doesn't search -- the function key IS the vocabulary. |
| SLU grid | Items are where management put them | Not alphabetical, not by category -- by workflow frequency. A management-designed fast path. |
| Gray palette | No emotional response | The screen is a tool. Neutral colors mean the operator reads function, not feeling. |
| Chain sequences | Multi-step in 1 trigger | Fire, print, advance -- chained into a single function key. Manager programs once. Operator triggers forever. |
| Workflow | MICROS TS | Simphony QS |
|---|---|---|
| New order + 1 item + pay | 4 | 3 |
| 4 items + fire + pay | 8 | 7 |
| Void last item | 1 | 1 |
Soul: The operator is a signal in a pre-designed circuit. Management designs the circuit. The operator flows through it. Speed comes from eliminating decisions, not touches.
"He was obsessed to make the entire thing work on a single screen. I love this guy. We want him too."
-- Joey Castillo
Jim Melvin -- the architect behind Compris, specifically the McDonald's implementation -- came from a different obsession than the others. Where Manny counted touches, Peter eliminated abstraction, and MICROS pre-configured workflows, Melvin asked a more radical question: why does a POS need more than one screen?
McDonald's serves billions. Every fraction of a second matters. Every screen transition is a context switch. Every page is a moment the operator's eyes leave the queue. Melvin's answer: eliminate all of it. One screen. Everything visible. Everything reachable. Always.
Compris's single-screen philosophy is a form of spatial compression. Instead of organizing by category and spreading across pages, Melvin compressed the entire operation into one viewport. The operator's eyes never leave. The brain never needs to remember what was on the previous screen because there is no previous screen.
At McDonald's scale, this is engineering genius. A crew member working a lunch rush processes hundreds of orders. Every screen change is cognitive load. Every page transition is a half-second of reorientation. Multiply that by a million McDonald's transactions per hour worldwide, and the single-screen obsession saves years of cumulative human attention every day.
| Design Decision | Operator Impact | Single-Screen Logic |
|---|---|---|
| Everything visible at once | Zero page transitions | Order, queue, totals, tender -- all on one screen. No hidden state. |
| Dense grid layout | Small targets, max density | Sacrifice target size for visibility. Muscle memory replaces target size. |
| Queue as position | Left-to-right order flow | The screen IS the queue. Position communicates progress. |
| Context through proximity | Related items are neighbors | No categories, no tabs. Spatial relationship IS the organization. |
Melvin's genius: he realized that at fast-food scale, the screen transition is the bottleneck, not the touch count. Manny optimized touches. Peter optimized dispatch. MICROS optimized decisions. Compris optimized attention. One screen means the operator's attention never has to move, reload, or reorient.
| Workflow | Compris QS |
|---|---|
| New order + 1 item + pay | 2 |
| 4 items + fire + pay | 5 |
| Void last item | 1 |
Touch count is low but the real metric is zero screen transitions. Every action happens in-place.
Soul: One screen. Zero transitions. The entire operation compressed into a single viewport. Speed comes from eliminating context switches, not touches. The operator's eyes never leave. The brain never reloads.
"Peter Lipman -- the first POSDRVR was pure C and he literally mapped every touch in memory to an action. That is why POSitouch is the fastest system on earth in the double DOS days."
-- Joey Castillo, from conversations with Peter Lipman in Rhode Island
Peter Lipman at Restaurant Data Concepts (RDC) wrote POSDRVR -- the POS driver -- in pure C. Not C++. Not a framework. Pure C. In the double DOS era, memory was the constraint. Every byte mattered. Every cycle mattered.
Peter's approach was radical in its directness: every touch on the screen was literally mapped in memory to an action. No event queue. No message bus. No abstraction layer between the finger and the function. Touch location → memory address → action. Hardware-level routing written in software.
This is why POSitouch was the fastest system on earth in the DOS era. The competition was processing events through layers of abstraction. Peter eliminated the layers. The touch WAS the action. There was nothing between them.
| Design Decision | Performance Impact | Memory Logic |
|---|---|---|
| Pure C, no abstraction | Zero overhead | The function pointer IS the button. The screen IS the dispatch table. |
| 3 service modes | 3 different memory maps | Quick Service, Fast Casual, Fine Dining each get their own optimized dispatch table. No runtime branching. |
| Quantity multiplier | N items in 2 touches | Touch "4", touch "Coke" = 4 cokes. 2 touches instead of N. |
| Fast cash buttons | 1 touch to close | $5/$10/$20/EXACT -- single memory-mapped action that fires tender + close + receipt. |
| 120 order screens | Pre-computed layouts | Every screen is a pre-built dispatch table. No dynamic rendering. |
Peter's genius: he treated the screen as hardware. Not a UI framework rendering widgets. A memory-mapped device where each pixel region is a function pointer. The speed came from eliminating everything between the touch and the truth.
Peter designed POSitouch for single-unit operators. Lean. Fast. One restaurant, one terminal, one dispatch table. But he designed it knowing someone would build the enterprise wrapper. When Joey asked permission to build NorthStar Enterprise for POSitouch, Peter said he designed it that way on purpose -- he wanted Joey to do exactly this.
Joey built the entire enterprise layer: multi-unit management, centralized menu deployment, chain-wide configuration, and all delivery aspects. Kris Maher (Maherware) owned reports and BI -- the reporting and business intelligence product owner for NorthStar Enterprise. Rom Krupp (now CEO of OneDine) was product owner for NCM -- NorthStar Change Management for POSitouch. That's how they captured The Cheesecake Factory on POSitouch and IBM. Peter built the fastest single-unit engine on earth. Joey handled delivery. Kris handled intelligence. The engine never changed -- it didn't need to. Peter's architecture was so clean that enterprise was additive, not invasive.
NorthStar Recipe Viewer: Rick Smith at The Cheesecake Factory handed Joey an Access database. Two weeks later Joey returned a working prototype in ASP.NET 1.0/2.0. Bill Lyons knew data and added good constraints. The prototype became production -- as usual. Free for life, they buy hardware from us. Another deal closed.
That's the POSitouch story: the fastest POS ever built (Peter's pure C dispatch table) + the enterprise wrapper that scaled it to chains (Joey's delivery + Kris's BI). Three architects, one system.
| Workflow | Posi QS | Posi FC | Posi FD |
|---|---|---|---|
| New order + 1 item + pay | 3 | 3 | 5 |
| 4 items + fire + pay | 6* | 6 | 11 |
| Void last item | 1 | 1 | 1 |
*With qty multiplier: qty(4) + item + fire + pay = 4 touches for identical items
Soul: The screen is a dispatch table. Every touch is a function call. Eliminate everything between the finger and the action. Speed is not optimization -- it's the absence of abstraction.
Four different engineers. Four different backgrounds. Four different decades. Same truth:
| Architect | Background | What They Eliminated | What Remained |
|---|---|---|---|
| Manny Negreiro (Aloha) | Satellite engineering | Unnecessary signal hops | The minimum path from intent to action |
| Peter Lipman (POSitouch) | Pure C / systems | Abstraction layers between touch and function | Memory-mapped dispatch -- touch IS action |
| A.L. Giannopoulos (MICROS) | Enterprise hardware | Operator decision-making | Pre-configured circuits -- operator flows, doesn't think |
| Jim Melvin (Compris) | High-volume fast food | Screen transitions / context switches | One screen -- entire operation in a single viewport |
They were all subtracting. Not adding features. Removing latency. Removing abstraction. Removing decisions. Removing screens. Each one asked: "what can I take away so there's less between the human and the food?"
That's why Soul 5 is emptiness. They were all heading there. Manny subtracted touches. Peter subtracted abstraction. MICROS subtracted decisions. Compris subtracted screens. The logical end is subtracting the system itself.
Joey's requirement: each UI must give users the same feel but next level. That means:
| System | Same Feel | Next Level |
|---|---|---|
| Aloha | Touch count discipline. Seat-based ordering. Floor as home. Color as status. | Predictive touches -- the system knows what the server will do next. Touch count approaches 1 for repeated workflows. |
| POSitouch | Memory-mapped speed. Qty multiplier. Mode-based identity. Fast cash. | The dispatch table learns. Frequently-ordered combos surface. The 120 screens reorganize by velocity. |
| MICROS | Configured workflow. Function keys. SLU grids. Chain sequences. | Self-configuring. The system observes usage and reconfigures the function key rail and SLU layout to match. |
| Compris | Single screen. Dense grid. Queue as position. Zero page transitions. | Adaptive density. Zones brighten and dim based on what matters now. Rush compresses. Lull breathes. |
Next level is the same engineering discipline applied to itself. Manny counted touches -- next level counts them automatically. Peter mapped touches to memory -- next level lets the map evolve. MICROS configured the workflow -- next level lets the workflow configure itself. Compris compressed to one screen -- next level makes that screen adapt.
| Era | Touch Count | What Was Removed |
|---|---|---|
| Pre-POS (paper) | ~50 per order | Nothing -- all manual |
| First POS (1970s) | ~20 per order | Paper, arithmetic, rewriting |
| Manny / Peter era | 3-6 per order | Unnecessary hops, abstraction, latency |
| Current skins | 3-6 per order | Vendor lock-in (same backend, any skin) |
| Next level | 1-2 per order | Predictable touches (system anticipates) |
| Soul 5 | 0 | The system itself. Voice, gesture, presence. The POS disappears. |
"The only thing better is no system at all." -- jc
The trajectory is clear. Every great POS architect was subtracting toward the same point. They just ran out of technology before they got there. We don't have that problem anymore.
Joey Castillo -- 1996-97 CBS. 1997-99 Javelin under Norman Campbell -- direct report. All things software. He handled the nonsense so the hardware engineers could do their job. In all his time there he can remember only one mistake he caught the hardware side on. The rest was pure ignorance and misunderstanding -- or disrespect to the hardware or operating system itself. Spec is everything.
During CBS Buena Park days, Joey left -- purely financial mismatch at the time, no choice of his own -- and went to Koo Koo Roo chicken. Reported to Kris Maher. Met Viet Ao -- IT grand master of simple. Joey built a rollout system for KKR: POSitouch on Javelin Wedges (Norman's design, latest and greatest). In 3 months he built and helped execute "Clucky" -- the manager opened the box, plug and play. Pick/tap the terminal position in the restaurant. Color-coded plug-and-play hardware -- power, internet. System installed by the manager, up and running in 15 minutes. Three months of focus to save 50% of the cost of a rollout using a VAR -- and certain quality with Joey. KKR was done quick. Then Norman called with impeccable timing and made him an offer he could not refuse -- and for which KKR would fully back, especially Kris Maher and Robert Fort the CIO.
Dec 1999 back to CBS -- CTO through 2022/23. All NorthStar products above -- Enterprise (delivery), Recipe Viewer, NCM -- plus their predecessors and numerous internal tools and deal-closing instruments. Scrum master and developer alongside Art Julian on the POS platform.
In all his time, Joey never had more fun than working with Andy Mai and Wesley. Wesley is pure simplicity driven -- his mental needlework reminds Joey of great Taiwanese gentleness and purity. Clearly a wizard.
And who can forget Johnny G. -- the other one, there's two. No filter, but what an amazing imagination. One of the best frontmen Joey ever worked with. Sometimes his words would push the ego of the next great Michelin-star owner/operator over the edge -- but that's what friends are for, right? JG is the inspiration you don't realize is inspiration until you're already done and beyond inspired. Good times.
Two grand master wizards for which Joey attributes the majority of his ability to call something exactly what it is. First, David Gonzales -- master of asking the same question 5 ways until he's satisfied with the answer. You had no idea and thought he forgot what you told him the last 5 times. And last but not least -- the man, myth, and humble legend Mark Heron. All Joey can say is: Mark is at least 33% of him in mind and spirit, and likely 77%, but it's pointless to measure. "If you think you are done designing, think again -- I'm sure Mark can identify about 100 problems you didn't know you even had." One of infinite skills of the great Heron.
Everything in "The Last System" -- the architecture, the code, the soul expression, the convergence toward emptiness -- is original work by Joey Castillo. Inspiration drawn from the architects above. Implementation, vision, and direction: his alone.
No company. Personal assets. His name. A human with 40 years of code.