Additional information
by James L. Pulley (Author)
Modern software systems appear stable while quietly losing the ability to tell the truth.
Outages, data disputes, security incidents, and regulatory failures rarely begin with dramatic technical collapse. More often, they begin with systems that look healthy but cannot produce trustworthy evidence when conditions change. Logs disagree. Timelines shift. Identity becomes ambiguous. Metrics reassure rather than testify.
The Fleetwood introduces authority engineering - a discipline for designing software systems that remain truthful under stress.
Using the thought experiment of a Cadillac Fleetwood re-engineered with the structural discipline of a 1990s performance workshop, James L. Pulley III explores what it means for a system to possess real authority rather than the appearance of stability. The Fleetwood becomes a physical reference frame for understanding how software systems preserve or lose truth when placed under load.
Through clear engineering analogies, the book demonstrates:
- Why calm systems can be structurally dishonest
- Why elasticity can hide failure instead of fixing it
- Why time must be authoritative and auditable
- Why identity must be stable and enforceable
- Why governance is a technical property, not a management activity
- Why refusal - the ability to say "no" - is the foundation of control
- Why performance without authority creates systemic risk
The book introduces a structural model of authority built on three load-bearing engineering surfaces:
- Infrastructure - the physical limits that cannot be abstracted away
- Identity - the boundaries of responsibility and trust
- Time - the coordinate system of causality
Together these form the invariant reference frame required for systems that must testify under financial, operational, or legal dispute.
Unlike books focused on scaling, observability, or reliability practices, The Fleetwood addresses the deeper problem beneath them: systems that cannot produce defensible truth.
Written for engineers, architects, executives, and system owners responsible for critical software, this book provides a new framework for understanding why modern platforms often feel stable while remaining structurally fragile.
This is not a book about cars.
It is a book about authority as an engineering property.
And about the systems that must be trusted.
