The Pipe Car Problem
By Nelson McKeeby
A Vehicle Defined by the Cylinder
The Pipe Car began with a restriction, not with an image of the vehicle I wanted. The Negentropic Cylinder could carry a person and only a limited amount of equipment into the future, so useful mobility had to be fitted into the same physical system that constrained everything else the Project sent. I wanted the Troubleshooters to emerge with a vehicle, but I also wanted the vehicle to remain subordinate to the Cylinder instead of quietly redefining how large the Cylinder had to be. That requirement made the Pipe Car a packing problem before it became an automotive problem. A road vehicle normally spreads its structure across a wide footprint because the wheels must stand apart and the passenger space occupies the volume between them. A Negentropic Cylinder presents a very different cargo shape. The car therefore had to be designed around the shape available for transport and then recover its useful road geometry only after emergence.
The modern Logistics material makes the consequence of the Cylinder especially clear. Its walls are extremely thin, so most of the volume implied by the exterior shape is usable, but that volume remains finite and elongated. Nothing inside needs a sleeping compartment or a life-support system during the sealed interval because no biological or mechanical process continues after closure. The interior can therefore be treated almost entirely as a protected cargo envelope whose contents are restrained for opening. That efficiency does not make the Cylinder spacious. Every piece of Project equipment must physically fit within the cylinder capacity allocated to the mission, and a vehicle competes for that capacity with every other capability the team might want to preserve. The Project can dedicate cargo Cylinders to a mission, but doing so still consumes a scarce transport asset. The Pipe Car consequently had to justify not only its mass but the shape of every component that occupied transport volume.
Packing a complete car would use the Cylinder badly even if the vehicle could somehow be made short enough. The track width that gives a car stability on the road becomes empty volume when the car is placed inside a long cylindrical container, while the cabin preserves a large volume of air that serves no purpose during negentropic transport. A complete vehicle also fixes the wheels at their operating width, which is exactly the dimension most likely to conflict with the cargo envelope. The solution was to stop treating the car as a single object during transport. The Project vehicle could exist as a set of modules whose packed dimensions were much smaller than the dimensions of the operating machine. The Cylinder carried the parts in the arrangement that used space efficiently. The Troubleshooters created the automobile after opening by putting those modules back into their working relationship.
This principle eventually became explicit in Project vehicle doctrine. Vehicles are not delivered through the Cylinders as complete road-ready machines. They are transportable assemblies intended to be put into service by the team with the same field tools that will later be used to maintain them. That requirement drives the Pipe Car toward a simple frame because the team must understand how its structure goes together before they ever need to repair it under pressure. I like this because assembly and maintenance become versions of the same knowledge. A teammate who has practiced joining the vehicle after emergence already knows where the major structural interfaces are and has handled the connections that will later need inspection. The initial assembly is therefore part of familiarization with the machine. The Project is not giving the team a sealed automobile and then asking them to learn its construction only after something fails.
Building the Car After Emergence
The modern pipe-frame design gives a practical way to accomplish that assembly. The team begins by establishing the long structural rails that carry the major loads through the vehicle. Crossmembers then lock those rails into the width required for operation, converting a narrow transport package into a stable road chassis. Sleeve couplers can preserve alignment at the joints while gusseted connections transfer load through the completed structure. I would not make the team perform precision fabrication during this process. Alignment-sensitive work belongs to the Project workshop before deployment, where jigs and controlled welding can establish the dimensions that must remain exact. Field assembly should bring prepared structural units together at designed interfaces. The Troubleshooters are assembling a vehicle from modules, not manufacturing a vehicle from raw stock beside an open Cylinder.
Once the basic frame is stable, the suspension assemblies can be attached at prepared mounting points. The steering system then has a fixed chassis from which its relationship to the front wheels can be checked. This sequence lets the team build outward from a structure whose dimensions are already controlled, so errors can be caught before heavy power components are installed. The wheel itself became an important part of this logic in the modern design. The 35x12.5R16 standard radial tire was selected as the largest practical wheel assembly that could be stored efficiently within normal Cylinder cargo architecture without being taken apart. That means the team does not have to mount tires onto rims during initial vehicle assembly. Complete wheel assemblies can emerge ready to bolt onto the suspension, which removes a difficult field operation from the startup procedure.
The Pipe Car's four-motor concept also lends itself to this method. A motor can arrive as a tested propulsion module whose mounting relationship has already been established before closure. Once the corresponding axle structure is fixed to the frame, the motor module can be secured and connected to the control system without requiring the team to rebuild the motor itself. The modern arrangement keeps the four propulsion units independent. The front pair drives the front axle while the rear pair serves the rear axle, and the driver can isolate a damaged motor from the controls. That later engineering detail grew naturally from the original decision to distribute propulsion across four electric machines. A vehicle assembled from separable units also becomes a vehicle that can lose one unit without turning every propulsion problem into a complete drivetrain failure.
The batteries give assembly a natural final stage because their mass is useful only after the structure can support it. A modern Type VII battery weighs about 85 kilograms, so installing heavy traction storage before the chassis is on its wheels would make every remaining assembly operation harder. Keeping the battery modules separate during the early work allows the frame to be handled at a much lower mass. The present Pipe Car design reinforces that choice through removable battery boxes mounted low in the center of the chassis. A battery box can slide into the frame after the car is structurally complete, and a damaged box can later be removed without dismantling the vehicle around it. The same feature that makes maintenance practical also makes post-emergence assembly practical. The team first builds the machine that carries the batteries and then loads the energy reserve into it.
A vehicle that must be assembled after emergence cannot depend on instructions nobody has rehearsed. The Project therefore has to treat vehicle assembly as a normal trained procedure before anyone enters a Cylinder. The team should know the order of the work and should recognize the checks that prove each stage is ready for the next. That training also improves later repair. A teammate who has physically installed the steering linkage during an exercise understands where play can develop in that linkage. Someone who has mounted a battery box understands how its guides and locks are supposed to feel when they are undamaged. The assembly process teaches the structure of the car through the same actions that will later keep it operating.
The need to assemble the Pipe Car means that mobility is not instantaneous when the Cylinder opens. The team must first make the emergence site safe enough for work and then unpack the vehicle modules without losing the organization established during loading. The car becomes operational only after the frame has recovered its working shape and the heavy power modules have been installed. I like the delay because it gives the opening scene a physical sequence. The Troubleshooters begin with what they can carry by hand while the larger capability is still becoming available. A dangerous emergence site can force the team to decide whether completing the vehicle is worth the time. The packing system therefore affects play even before the first kilometer is driven.
The assembly requirement would have been a poor bargain if the completed car then became difficult to service. The modern design keeps the major systems exposed enough that a team can reach them with field tools, and the battery boxes remain removable without opening the entire chassis. The four-motor arrangement similarly allows a damaged propulsion unit to be isolated while the remaining system continues to function. The pipe-frame family extends this idea through standard components. The same wheel pattern appears on related Project mobility equipment, which reduces the number of unique spares that have to consume Cylinder space. A part saved for one vehicle can remain useful to another because the Project treats interchangeability as a logistical advantage. Assembly, repair, and packing all improve when the same interfaces appear repeatedly.
Electric Drive and the Project Battery System
Electric drive attracted me from the beginning because electricity can be produced without committing the Project to one fuel supply that may no longer exist after emergence. A gasoline engine binds useful mobility to the continued availability of a compatible refined fuel. An electric car still has an energy problem, but the team can solve that problem wherever it can obtain electrical generation. That distinction fitted the future I was building. A settlement with a working dam might possess the one resource that keeps an advanced Project vehicle moving even if nobody there can manufacture the vehicle itself. The relationship gives local infrastructure real value to the Troubleshooters. The car may be Project technology, but its continued operation can depend on the people who keep an ordinary generator alive.
I did not begin by choosing a dramatic top speed and then invent specifications that produced it. I went to stores and physically weighed batteries because their mass had to be real enough for me to understand what the vehicle was carrying. I weighed electric motors for the same reason. The machine began to acquire limits from objects I could actually handle. Those measurements were crude compared with professional engineering work, but they immediately changed my thinking. A battery that looked compact on a shelf became a serious design commitment once its weight had to be accelerated by the same motors it was feeding. A motor that promised more output also took more space and increased demand on the electrical system. The Pipe Car became an early lesson that a machine cannot be improved one specification at a time without affecting the rest of the machine.
A science teacher helped me relate vehicle mass to the power needed for useful speed. I was eleven and was not doing a professional vehicle analysis, but the exercise removed speed from the category of numbers I could simply choose. If I added mass, the motors had to work harder to accelerate it and the battery reserve had to supply the work. That relationship was more valuable than any exact performance figure we produced. It taught me to ask what an improvement cost somewhere else in the system. The Pipe Car became understandable because the major limitations had causes. A player did not need my original calculations to understand why a heavier car consumed its reserve more quickly.
The first Pipe Car used four electric motors because that arrangement gave me a manageable way to think about distributed propulsion. Each motor remained within the scale of machinery I could research, while their combined output could move a vehicle larger than any one of them. The design also let me reason about power as something shared across the vehicle instead of concentrated in one large engine. The modern Pipe Car keeps that basic idea and gives it a stronger operational reason. Each motor can be isolated, allowing the car to continue moving after a propulsion failure. A car with three healthy motors remains a car, even though acceleration suffers. The original four-motor solution survived because later design work found another useful consequence inside the same arrangement.
The modern Project battery system grew far beyond the individual batteries I was weighing in 1979. Department 6 eventually standardized electrical storage so that teams did not have to treat every device as a separate power problem. The important design principle is that a battery belongs to a family whose interfaces and handling procedures are already familiar to Project personnel. For the Pipe Car, the heavy end of that family is represented by the Type VII battery. It weighs about 85 kilograms and provides 420 Energy Points in the current logistics model. Its size is small enough to move as a module and large enough to justify the structural overhead of a heavy vehicle battery. The battery is therefore a piece of cargo during Cylinder transport and a replaceable energy component after the car has been assembled.
The modern Pipe Car carries its energy in six removable boxes mounted low along the center of the chassis. Each box supplies the same usable 420 Energy Points, so the driver does not have to remember a different value for each position. Two rear boxes can each hold a Type VII battery, while the forward boxes can use grouped smaller Project batteries arranged to provide the same planned output. This arrangement integrates the car into the wider Project power system without forcing the vehicle to depend on one irreplaceable monolithic pack. A missing box reduces the car's stored energy by a predictable fraction. A damaged box can be slid out of the frame and replaced when another compatible arrangement becomes available. The power system can degrade in understandable steps instead of failing as one sealed mass.
The value of standardization becomes clearer after the original Project stock begins to thin. Department 6 doctrine permits battery substitution when the intended unit is unavailable, accepting reduced endurance when smaller modules have to stand in for a larger one. The electrical system therefore gives the team a way to improvise without pretending that every substitute is equally efficient. This also means that stored electrical energy is a Project resource before it is a vehicle resource. A team can understand the condition of its battery inventory through one common planning system and decide where that energy is most useful. The Pipe Car participates in the same logistical language as the rest of Department 6 equipment, which makes it easier to integrate into a camp after the immediate need for driving has passed.
The later Energy Point model formalized something I had been trying to express from the beginning: range is a consequence of work done, not a number printed permanently beside the vehicle name. The current Pipe Car begins with 2,520 Energy Points when all six battery boxes are available. On good pavement at a moderate speed, the car consumes far less energy per kilometer than it does when the same vehicle is forced through broken ground. That gives the battery system a common language for planning. The team can estimate how much of its electrical reserve a journey will consume and compare that cost with the benefit of making the trip. The exact figures are modern additions, but the underlying idea is the same one I was working toward when I weighed batteries as a child. Mobility consumes stored work, and the vehicle becomes more interesting when the players can see the consequence before they spend it.
Energy After Emergence
Negentropic transport gives the battery system one extraordinary advantage that does not require an extraordinary battery. Electrical processes stop when the Cylinder closes, so a charged battery does not slowly discharge while the external world advances. Chemical deterioration also stops during the sealed interval. The Project can therefore pack a fully prepared power module and expect it to emerge in the same state in which it was sealed. That makes the opening sequence much more useful. The team does not have to discover a generating station before it can assemble the vehicle and leave the emergence site. The initial energy reserve can be sent forward with the car, while the longer logistical problem begins only after the team starts consuming that reserve. The Cylinder preserves readiness; it does not provide replenishment.
Battery power only works as a long-term Project technology if the Project also thinks about generation. The modern equipment system treats batteries as storage devices that can accept electricity from whatever source the team can establish. A field team can connect to surviving fixed infrastructure when it is safe to do so, while its own generating equipment provides a slower route toward electrical independence. The folded solar mat shows the scale of that relationship. Under good light the current field array produces only a few Energy Points per hour, while even efficient road travel in the Pipe Car consumes several Energy Points for each kilometer. Solar power can preserve communications capability and gradually rebuild reserves, but it does not turn the Pipe Car into an unlimited solar automobile. The difference keeps generation important as infrastructure instead of converting a portable panel into another way to erase range.
The Project can also produce electricity from local fuel through its portable multi-fuel generator. That creates a different kind of connection between the Pipe Car and the future because combustible material can be turned into electrical storage without requiring the vehicle itself to burn that material. The car remains electrically standardized while the generator absorbs much of the uncertainty about what fuel can actually be obtained. I prefer that arrangement because it separates propulsion from energy production. The vehicle does not need a different engine whenever the available fuel changes. The team solves the local energy problem at the generator, then feeds the resulting electricity into the battery system it already understands. The Pipe Car can therefore remain one machine while the world supplies several possible ways to recharge it.
The Project does not need a charging network waiting at the emergence site because the Cylinder can deliver the car's initial reserve in perfect condition. That creates a useful operating window after opening. The team can assemble the vehicle and begin moving before it understands the local economy or has found a dependable power source. The window is temporary by design. Every kilometer reduces the reserve that came through the Cylinder, and the team eventually has to connect the vehicle to the world it entered. Finding a generator then becomes more important than owning a superior motor. The Pipe Car starts as preserved Project capability and gradually becomes part of the contemporary infrastructure around it.
The Limits I Refused to Remove
The obvious answer to short range was always more battery capacity. The problem is that every additional battery also becomes part of the load the motors must move. The added storage increases the available work while simultaneously increasing the work required to move the vehicle. Cylinder volume makes that feedback even sharper. Extra batteries occupy space that could carry something else, and the larger battery allocation has to be handled after opening. The useful question is therefore how much stored energy improves the mission before the storage itself begins to undermine the reason for having a compact vehicle.
I allowed myself a fictional advantage through X-Tech. In the early calculations I often treated advanced Project batteries or motors as roughly twice as capable as the contemporary equipment I could examine. That was a large improvement for a vehicle constrained by transport volume, and it allowed the Project to feel technically ahead of the late 1970s. I kept the improvement finite because the battery still needed to remain a battery. It stored a limited amount of energy and had to be carried by the machine that consumed that energy. X-Tech could make the Pipe Car practical within a severe packing problem. It could not make the packing problem disappear.
Players eventually suggested a much easier answer by giving the Pipe Car an advanced power source that removed the battery problem. Quantum power was one of the proposals. From the player's point of view, the suggestion made sense because it attacked the weakness directly. I refused it because the weakness was producing decisions I wanted to keep. A vehicle that could drive indefinitely would no longer force the team to think about where the next charge came from or whether the present trip deserved the energy it consumed. The car would become more impressive while losing its connection to the setting's infrastructure. The battery system kept movement dependent on choices the players could understand.
Another recurring solution was to enlarge the Negentropic Cylinder. A larger container could carry the Pipe Car with less disassembly and could devote more capacity to the vehicle's batteries. Many of the compromises would become easier immediately. The Cylinder was not supposed to exist for the convenience of the car. Its finite volume was already shaping Project planning, so enlarging it whenever a design became uncomfortable would let each new invention rewrite the premise. I kept the Cylinder small because the vehicle was supposed to adapt to the constraint. The later modular assembly doctrine is a much better answer because it solves the packaging problem without destroying it.
What the Pipe Car Did to Play
The early Pipe Car did not need modern highway performance to be valuable. Its first job was to move a small team farther than they could move the same equipment on foot. Even limited range could change how much country the Troubleshooters could examine before night or how quickly they could return to a damaged installation. Keeping the vehicle modest also made its use a decision. Driving saved time while consuming electrical reserve that might be difficult to replace. Leaving the car at camp protected that reserve but reduced the team's carrying power away from the site. Mobility became something the players allocated according to the problem in front of them.
The Pipe Car changed the way I thought about distance in play because a map did not become smaller when the team acquired a vehicle. The road still had length, and crossing that length still consumed part of a finite energy reserve. A distant destination therefore imposed a cost even when no encounter occurred along the way. Terrain made the same distance behave differently. The modern Energy Point model makes that explicit because broken ground consumes much more of the battery reserve than efficient pavement travel. Route planning can therefore be an engineering decision before it becomes a navigation decision. A shorter path may consume more energy if the surface forces the motors to work harder for every kilometer.
A vehicle with finite energy can create trouble without the Game Master inventing a breakdown. If the team spends too much of the reserve early in a journey, the return problem already exists. The consequence came from a decision the players understood when they made it. Mechanical damage works the same way in the modern design. Losing one battery box removes a known portion of the stored energy, while losing a motor changes how efficiently the remaining system can move the car. The difficulty grows from the condition of the machine. The Game Master does not need to declare that the car fails because the story has reached a dramatic moment.
The vehicle became one of the clearest examples when we later talked about cinematic reality and concrete reality. Cinematic logic can always discover enough power for another chase because the scene wants movement. Concrete reality asks what charge remained before the chase began and accepts that the answer may force a different scene. I never believed every calculation deserved table time. The practical question was whether ignoring the calculation would erase a choice the players had already made. If they had deliberately used most of the charge, the remaining charge had to influence what became possible later. The physical state of the car carried memory from one decision into the next.
The arguments about the Pipe Car were useful even when I rejected the proposed solution. A player who asked for more range was identifying a real weakness in the vehicle. I then had to decide whether the weakness showed that the design had failed or whether it was producing the consequences I wanted the setting to preserve. That process improved Negentropy because it forced me to defend limitations through the world instead of through authority as the Game Master. If I could not explain why a restriction remained, I had a reason to reconsider it. When I could explain the restriction and show the decisions it created, the argument often clarified the design more effectively than another page of rules.
Why the Pipe Car Survived
The Pipe Car remains one of my clearest examples of designing by research because research changed the object instead of decorating it. Weighing batteries made stored energy feel expensive in a physical sense. Working through motor power made speed dependent on machinery instead of desire. The Cylinder then prevented me from solving those problems by increasing size without consequence. Later writing repeated the same method at a more sophisticated level. Standardized wheels answered a transport problem created by the Cylinder, while removable battery boxes answered a handling problem created by heavy electrical storage. The modern design is more detailed because I know more, but the development method remains the same. Each useful feature should solve a real constraint and leave the rest of the system understandable.
Looking back, the most important part of the Pipe Car was never its exact performance. The vehicle taught me that a limitation could create play when the players understood the mechanism behind it. The moment the car could not travel indefinitely, the surrounding world gained importance because the team had to discover where energy could come from. The need for assembly deepens the same lesson. The Project can preserve sophisticated equipment through time, but the equipment still has to occupy physical space and become a working machine after emergence. The car begins as packed components inside a Cylinder and ends as a vehicle whose continued usefulness depends on the infrastructure around it. That movement from preserved capability to local dependence is one of the reasons the Pipe Car still belongs in Negentropy.
The modern Pipe Car is much more developed than the machine I worked out as a child, but the original design pressure remains visible. It still uses four electric motors and still treats battery energy as a finite reserve. The modern vehicle also makes the Cylinder problem explicit by existing as a field-assembled modular system. That continuity is more important to me than preserving every early specification. The old design established the question, while later work supplied a more coherent answer. The Pipe Car can improve because the Project has spent decades of fictional development learning how to package a vehicle, assemble it after emergence, and integrate it into a standardized electrical system.
The Pipe Car survived because it solves enough of the mobility problem without solving every problem surrounding mobility. The Cylinder can deliver a useful vehicle, but it delivers that vehicle as prepared potential that must be assembled into working form. The battery system gives the car substantial endurance, but continued operation eventually requires the team to generate more electricity. That balance keeps the Pipe Car connected to the central design of Negentropy. Project technology gives the Troubleshooters an advantage at the moment of emergence and enough capability to begin acting intelligently. The future then becomes part of keeping that advantage alive. The car is therefore not only a vehicle carried through time; it is a compact example of how Project Negentropy turns finite space into a continuing problem of engineering and logistics.