Plan the Whole Job: A TSTOEAO Systems Guide to Engineering and Construction: A Practical Method for Scoring Labor, Movement, Materials, By-Products, Stewardship, and Lifetime Value Before Work Begins
Plan the Whole Job:
A TSTOEAO Systems Guide to Engineering and Construction for Scoring Labor, Movement, Materials, By-Products, Stewardship, and Lifetime Value Before Work Begins
DOI: Pending assignment
John Swygert
August 1, 2026
Abstract
Engineering and construction plans are commonly evaluated by whether they can produce a specified primary deliverable within a proposed budget and schedule. A tunnel must provide passage. A building must provide usable space. An electrical system must deliver power. A drainage system must move water. A machine must perform its designated operation.
These requirements are necessary, but they do not establish that the whole job has been planned intelligently.
Every project also contains labor movements, material transfers, equipment transitions, temporary works, removed matter, unused capacity, by-products, waste streams, environmental effects, maintenance obligations, future modifications, and opportunities to supply other projects or industries. A plan may successfully produce its primary deliverable while performing poorly across the larger system.
This paper proposes a general TSTOEAO planning method for evaluating the complete job before physical work begins. The method applies most directly to engineering and construction, particularly projects in which material is removed, placed, transformed, transported, or exchanged. It is intentionally general enough to apply across civil, structural, electrical, mechanical, chemical, environmental, industrial, software, aerospace, biomedical, and other engineering disciplines.
The governing principle is:
> Every engineering and construction plan should be evaluated not only by whether it produces its primary deliverable, but by how intelligently it routes every necessary action, material, movement, by-product, cost, and future opportunity.
The proposed method begins by establishing non-negotiable safety, structural, quality, legal, and environmental gates. It then maps the whole job through inputs, actions, transitions, outputs, by-products, destinations, externalized costs, and future uses.
A project is scored across a portfolio of planning dimensions, including:
action economy;
transition economy;
resource utilization;
by-product routing;
effective output multiplicity;
downstream industrial leverage;
avoided-cost capture;
lifetime adaptability;
resilience and maintainability;
and stewardship.
These measures support an overall Engineering Planning Portfolio Score, a separate Weakest-Boundary Score, and an engineering form of SEQ comparing the realized plan with the best feasible plan available under actual constraints.
The framework does not assume that every project should produce many products, eliminate all redundancy, or reuse every material. Some separation, repetition, reserve capacity, and disposal are necessary for safety and reliability. The objective is not maximum output count. It is maximum compatible, risk-adjusted lifetime value without transferring unacceptable costs to workers, communities, ecosystems, or future generations.
The practical sequence is:
\[
\boxed{
\text{Map the whole job}
\rightarrow
\text{score the plan}
\rightarrow
\text{identify weak pathways}
\rightarrow
\text{replan}
\rightarrow
\text{score again}
}
\]
A poor score is not merely a criticism of the planner. It is an early warning delivered before labor, money, material, time, and the resources of the Earth are unnecessarily consumed.
Keywords
TSTOEAO; engineering planning; construction efficiency; SEQ; systems engineering; force multiplication; action economy; transition economy; material utilization; by-product routing; stewardship; industrial ecology; lifetime value; weakest boundary; project optimization.
1. Introduction
A worker must move several pieces of lumber from a yard to a lower sidewalk.
One plan carries each piece through the complete route separately. The worker crosses the yard, descends the retaining wall, places the lumber, returns, and repeats the sequence.
A second plan moves all the lumber to the transition point first. The worker then crosses the wall once and completes the lower portion of the task as one grouped operation.
The second plan does not require the worker to move faster.
It does not require greater strength.
It does not change the final destination.
It changes the sequence.
\[
\text{same worker}
+
\text{same material}
+
\text{same objective}
+
\text{better pathway}
=
\text{less unnecessary work}.
\]
This is a simple household example, but the principle scales.
The repeated motion that wastes several minutes in a yard can become:
thousands of unnecessary truck movements;
repeated crane repositioning;
duplicated excavation;
avoidable shutdowns;
excessive equipment changes;
unnecessary heating and cooling cycles;
wasted concrete;
unused electrical capacity;
discarded industrial heat;
redundant data processing;
or years of preventable maintenance.
Engineering efficiency is therefore not merely a matter of working faster.
> Engineering efficiency begins by arranging the work so unnecessary actions and transitions do not have to occur.
2. The Primary Deliverable Is Not the Whole Job
Every engineering project has a primary deliverable.
Examples include:
a bridge;
a tunnel;
a building;
an electrical network;
a machine;
a water-treatment plant;
a roadway;
a production line;
a drainage system;
a software platform;
or a medical device.
The conventional planning question is:
> Can the project produce the required deliverable?
The whole-job question is broader:
> What complete system of actions, resources, outputs, costs, risks, and future conditions will be created while producing it?
A project can succeed narrowly while failing systemically.
A tunnel may function while millions of tonnes of potentially useful material are transported unnecessarily to disposal sites.
A building may open on time while being difficult to repair, adapt, or deconstruct.
An electrical system may meet current demand while lacking access, modularity, or spare pathways for foreseeable expansion.
A factory may produce its intended product while discarding usable heat, water, material, and chemical by-products.
A drainage system may protect one property while transferring flooding downstream.
The primary deliverable is only one expression of the project.
3. Planning the Object Versus Planning the System
Object-centered planning asks:
What must be built?
How large must it be?
What materials are required?
What will it cost?
When will it be complete?
Systems planning adds:
Where do all materials originate?
Where does removed material go?
How many times is each item handled?
Where do transitions occur?
What temporary structures are required?
What by-products will be created?
Can those by-products become useful inputs?
What burdens are transferred outside the project boundary?
What maintenance pathways remain accessible?
What can the system become later?
What industries or communities can the project support?
What future work can be avoided through better planning now?
The difference is not greater complexity for its own sake.
It is greater completeness.
4. The TSTOEAO Foundation
The Swygert Theory of Everything AO proposes the foundational relation:
\[
V=E\times Y,
\]
where:
\(V\) is realized value or outcome;
\(E\) is energy or opportunity;
and \(Y\) is Encoded Equilibrium.
In engineering, \(E\) may include:
labor;
materials;
machinery;
energy;
land;
time;
information;
capital;
and natural resources.
These inputs do not determine the final value by themselves.
Their expression is governed by:
sequencing;
boundaries;
geometry;
access;
routing;
compatibility;
standards;
timing;
logistics;
destination;
maintenance;
and future adaptability.
These relationships constitute:
\[
Y_{\text{plan}}.
\]
Therefore:
\[
V_{\text{project}}
=
E_{\text{project}}
\times
Y_{\text{plan}}.
\]
Two projects may consume similar resources and produce radically different lifetime value because their planning architectures differ.
5. The Whole-Job Principle
The central operational proposition is:
\[
\boxed{
\text{Plan the whole job, not merely the named deliverable.}
}
\]
The whole job includes:
\[
J=
\{
I,A,T,O,B,D,X,F
\},
\]
where:
\(I\) represents inputs;
\(A\) represents actions;
\(T\) represents transitions;
\(O\) represents intended outputs;
\(B\) represents by-products;
\(D\) represents destinations;
\(X\) represents externalized effects;
and \(F\) represents future states and uses.
A plan is incomplete when one or more of these categories remain unexamined.
6. Inputs
Every input entering the project should be identified before work begins.
Inputs may include:
human labor;
machine time;
fuel;
electricity;
water;
raw materials;
components;
land;
temporary access;
storage space;
transportation;
information;
software;
permits;
supervision;
and capital.
The planning question is not only:
> “How much input is required?”
It is also:
> “How many useful expressions can this necessary input support?”
A trench requires excavation.
Could it safely support several compatible utilities?
A roof requires structural area.
Could it also manage water, support energy generation, regulate heat, or provide habitat?
A cooling system removes heat.
Can that heat serve another process?
A demolition project separates a structure.
Can its steel, masonry, timber, fixtures, or equipment become inputs elsewhere?
7. Actions
An action is any operation requiring labor, energy, time, equipment, or attention.
Actions may include:
lifting;
carrying;
drilling;
cutting;
loading;
unloading;
inspecting;
measuring;
fastening;
cleaning;
heating;
cooling;
starting;
stopping;
repositioning;
transporting;
approving;
transferring;
and repairing.
Every action should answer three questions:
1. Is it necessary?
2. Is it occurring in the best sequence?
3. Can it contribute to more than one compatible objective?
The first objective is not to make necessary work faster.
It is to remove unnecessary work from the pathway.
8. Action Economy
Action economy compares the action burden of the proposed plan with the lowest feasible burden consistent with safety and quality.
A cost-weighted Action Economy score may be written:
\[
AE
=
\frac{C_{A}^{*}}
{C_{A}},
\]
where:
\(C_A\) is the total planned cost of actions;
and \(C_A^{*}\) is the lowest feasible action cost under real project constraints.
The cost may include:
labor time;
energy;
equipment wear;
supervision;
delay;
and risk.
Because:
\[
C_A\geq C_A^{*},
\]
the normalized score satisfies:
\[
0<AE\leq1.
\]
A score near 1 indicates that unnecessary actions have largely been removed.
A low score indicates that the job should be resequenced, regrouped, redesigned, or staged differently.
9. Transitions
A transition occurs when work crosses a boundary.
Transitions include:
moving between floors;
crossing a retaining wall;
loading material onto a truck;
unloading it elsewhere;
transferring work between contractors;
changing tools;
changing voltage;
converting file formats;
restarting machinery;
switching production lines;
changing temperature;
changing pressure;
obtaining a new approval;
or transferring responsibility between organizations.
Transitions often contain greater cost and risk than the steady operation occurring between them.
A machine operating continuously may perform efficiently.
Repeated starting, stopping, cleaning, resetting, and restarting may dominate total cost.
A material may be inexpensive.
Handling it six times may not be.
> Every transition should be required to justify its existence.
10. Transition Economy
A Transition Economy score may be written:
\[
TE
=
\frac{C_T^{*}}
{C_T},
\]
where:
\(C_T\) is the total cost of planned transitions;
and \(C_T^{*}\) is the minimum feasible transition cost consistent with safety, quality, and operational requirements.
Transition cost can include:
movement;
loading;
unloading;
waiting;
setup;
shutdown;
restart;
inspection;
coordination;
conversion loss;
damage probability;
and accident exposure.
The objective is not to eliminate necessary boundaries.
It is to prevent repeated or poorly located crossings of those boundaries.
11. Stage Before Crossing
A general rule follows from transition analysis:
> Where safe and practical, consolidate compatible work before crossing an expensive boundary.
Examples include:
staging materials before a crane lift;
collecting several components before entering a controlled area;
grouping deliveries by destination;
completing compatible underground utilities during one excavation;
performing several inspections during one shutdown;
processing compatible data in one pass;
or completing preparatory work before mobilizing specialized equipment.
This does not justify unsafe loads or excessive batching.
It means the sequence should minimize unnecessary repetition.
12. Outputs
The primary output is the deliverable named in the project.
The complete output inventory should include:
permanent structures;
usable voids;
recovered materials;
access routes;
data;
temporary works with future value;
generated heat;
recovered water;
reusable components;
land shaping;
utility corridors;
environmental improvements;
and future capacity.
A project cannot measure its efficiency accurately while counting only the most obvious product.
13. By-Products
A by-product is an output not originally identified as the primary purpose of the operation.
Examples include:
excavated soil or rock;
demolition material;
waste heat;
wastewater;
pressure;
vibration;
gases;
metal offcuts;
sawdust;
packaging;
organic matter;
recovered chemicals;
data;
empty space;
and temporary access.
A by-product may become:
another project input;
a commercial product;
an environmental burden;
a future resource;
or unavoidable waste.
The plan should identify which of these outcomes is intended.
14. Waste as an Unrouted Output
Some waste is unavoidable.
Some material is contaminated, incompatible, degraded, hazardous, or economically impractical to recover.
Other waste exists because no pathway was prepared for it.
\[
\text{recoverable output}
+
\text{absent destination}
=
\text{waste stream}.
\]
This produces a critical TSTOEAO distinction:
> Waste is not always an intrinsic property of matter. It may be the result of an incomplete routing architecture.
The correct question is not merely:
> “Can this be reused?”
It is:
> “Can this be reused safely, reliably, economically, and at greater total value than the complete cost of recovery?”
15. Resource Utilization
Resource utilization should be measured separately for major input classes rather than forcing unlike resources into one physical unit.
For resource class \(j\):
\[
RU_j
=
\frac{
Q_{j,\text{usefully expressed}}
}{
Q_{j,\text{introduced}}
},
\]
where \(Q_j\) may represent:
material mass;
energy;
water;
land;
machine capacity;
or another measurable resource.
A composite score may then be created:
\[
RU
=
\sum_{j=1}^{m}w_jRU_j,
\]
where:
\[
\sum_{j=1}^{m}w_j=1.
\]
Weights should reflect project significance and must be declared before scoring.
A high resource-utilization score does not require every gram or joule to become a product.
It requires unused fractions to be identified, justified, and minimized where feasible.
16. By-Product Routing
The By-Product Routing score measures how much recoverable secondary value the plan actually captures:
\[
BR
=
\frac{
V_{\text{by-products realized}}
}{
V_{\text{by-products best feasible}}
}.
\]
The denominator is not every imaginary use.
It is the best feasible by-product value after accounting for:
composition;
contamination;
processing;
demand;
distance;
timing;
safety;
storage;
regulation;
and market reliability.
A plan should not receive credit for speculative uses lacking a real destination.
17. Effective Output Multiplicity
Counting products alone can be misleading.
A project does not become highly efficient by creating one valuable product and several nearly worthless side products.
The portfolio should measure the number of economically or operationally substantial outputs.
Let:
\[
p_i
=
\frac{v_i}
{\sum_{k=1}^{n}v_k},
\]
where \(v_i\) is the net value of output \(i\).
An Effective Output Multiplicity can be written:
\[
EOM
=
\frac{1}
{\sum_{i=1}^{n}p_i^2}.
\]
If one output contains nearly all project value:
\[
EOM\approx1.
\]
If two outputs carry approximately equal value:
\[
EOM\approx2.
\]
If four outputs carry approximately equal value:
\[
EOM\approx4.
\]
This prevents token side products from being used to exaggerate force multiplication.
18. More Outputs Are Not Automatically Better
The objective is not:
\[
\max(n_{\text{outputs}}).
\]
The objective is:
\[
\max
\left(
V_{\text{compatible lifetime portfolio}}
\right).
\]
Additional products may require:
expensive separation;
additional transport;
new environmental disturbance;
quality compromises;
hazardous coupling;
excessive maintenance;
or markets that do not exist.
A single-purpose design can be correct when:
safety requires separation;
contamination risk is high;
reliability requires independence;
no useful secondary demand exists;
or added complexity destroys more value than it creates.
The framework does not reward output count.
It rewards justified value.
19. Highest-Compatible-Value Routing
A mixed material or energy stream should not automatically be assigned to one destination.
Different fractions may have different best uses.
For excavated material:
\[
\text{high-grade rock}
\rightarrow
\text{structural aggregate},
\]
\[
\text{medium-grade material}
\rightarrow
\text{road base or embankment},
\]
\[
\text{fine clay-bearing fraction}
\rightarrow
\text{ceramic, liner, or stabilized fill},
\]
\[
\text{unusable remainder}
\rightarrow
\text{safest feasible disposal}.
\]
The same cascade applies elsewhere.
High-temperature waste heat may support industrial processes.
Lower-temperature heat may support buildings, water, drying, or agriculture.
Clean water may return to production.
Lower-grade water may support cooling, washing, or landscape uses.
> Maximum value is created when each fraction is routed to the highest-value use for which it remains technically and ethically suitable.
20. Downstream Industrial Leverage
An engineering project may increase productivity beyond its own project boundary.
Excavated aggregate may supply road construction.
Recovered heat may support food processing or district heating.
A wastewater plant may supply reclaimed water, nutrients, or biogas.
A utility corridor may allow later communication, electrical, or water systems to expand.
A software platform may become reusable infrastructure for several applications.
This can be described through Downstream Industrial Leverage:
\[
DIL
=
\frac{
V_{\text{downstream enabled, net}}
}{
C_{\text{primary project}}
}.
\]
The measure should include only downstream value that is:
causally enabled;
reasonably measurable;
not double-counted;
and greater than the cost transferred downstream.
> The strongest project does not merely complete itself. It increases the productive route-space of surrounding systems.
21. Supporting Several Industries
Supporting several industries can be a sign of intelligent engineering.
It is not automatically proof of efficiency.
A project supporting two industries substantially may be more valuable than one nominally connected to ten.
The correct question is:
> How much useful capability does the project create outside its primary output?
Examples include:
transportation excavation supplying construction materials;
power generation supplying usable heat;
agricultural systems supplying food, energy, soil amendments, and water treatment;
data infrastructure supporting research, administration, logistics, and public services;
and industrial facilities exchanging heat, water, gases, and material streams.
The project becomes a node within a portfolio rather than an isolated object.
22. Avoided-Cost Capture
Value can be created by preventing a future expense.
Avoided costs may include:
\[
C_{\text{avoided}}
=
C_{\text{disposal}}
+
C_{\text{replacement}}
+
C_{\text{transport}}
+
C_{\text{rework}}
+
C_{\text{downtime}}
+
C_{\text{remediation}}
+
C_{\text{future reconstruction}}.
\]
Examples include:
avoiding landfill fees;
avoiding purchase of virgin aggregate;
avoiding a second excavation;
avoiding repeated mobilization;
avoiding future demolition;
avoiding environmental cleanup;
and avoiding replacement of inaccessible components.
Avoided cost is real value even when no visible new product is created.
23. Removal and Placement
Construction frequently contains a paired material system:
\[
\text{removal at Site A}
\rightarrow
\text{placement at Site B}.
\]
The source and destination should be planned together.
A project requiring fill should ask whether another nearby project will generate suitable material.
A demolition project should ask where recovered components are needed.
A road cut should be coordinated with embankment requirements.
A tunnel should be coordinated with aggregate, concrete, restoration, or land-shaping needs.
A dredging project should evaluate beach nourishment, wetland construction, land reclamation, or other compatible destinations.
> Every removal has a destination. Every placement has a source. Planning them separately can create two problems where one coordinated system could create two products.
24. Paired Project Planning
Two projects may each possess a liability that becomes valuable when connected.
Project A produces excess material.
Project B requires fill.
Project A produces heat.
Project B requires heat.
Project A produces treated water.
Project B requires non-potable water.
Project A creates an access route.
Project B requires future access.
The relationship can be written:
\[
B_A
\rightarrow
I_B,
\]
where the by-product of Project A becomes an input to Project B.
This is not automatically beneficial.
Compatibility, timing, distance, quality, ownership, and regulation must align.
But the possibility should be tested before either project pays to destroy or replace the same value.
25. Time as a Boundary
A material may be correct but available at the wrong time.
\[
\text{correct resource}
+
\text{wrong schedule}
=
\text{storage or disposal problem}.
\]
Whole-job planning must coordinate:
production rate;
demand rate;
storage capacity;
processing time;
weather;
equipment availability;
permits;
and receiving-site readiness.
A useful resource can become waste when timing is ignored.
Scheduling therefore belongs inside \(Y_{\text{plan}}\), not outside it.
26. Distance as a Boundary
A reusable material may lose its advantage when transported too far.
Its net value should include:
\[
V_{\text{net material}}
=
V_{\text{use}}
-
C_{\text{processing}}
-
C_{\text{handling}}
-
C_{\text{transport}}
-
C_{\text{risk}}.
\]
Material reuse is not good stewardship when recovering it consumes more energy, creates greater emissions, or transfers greater harm than an available alternative.
The system must evaluate the complete route.
27. Lifetime Value
A project should not be judged only at the moment of completion.
Its value continues through:
operation;
maintenance;
repair;
modification;
expansion;
repurposing;
deconstruction;
and recovery.
Lifetime value may be represented as:
\[
V_{\text{lifetime}}
=
\int_{t_0}^{t_f}V(t)\,dt
-
C_{\text{lifetime}}.
\]
For economic calculations, future values and costs may be discounted through an explicitly declared method.
Not all value should be forced into monetary terms. Ecological protection, safety, access, resilience, and cultural value may require separate measures.
> A project can be efficient at opening and wasteful across its life.
28. Future Route-Space
A well-planned system preserves useful future choices.
Examples include:
accessible utility paths;
spare conduit;
modular components;
removable connections;
standardized interfaces;
repair access;
structural capacity for foreseeable expansion;
adaptable interior space;
separable materials;
and documented system provenance.
Future route-space can be represented conceptually as:
\[
R_F
=
\{
\text{feasible later adaptations}
\}.
\]
A project with greater useful future route-space may possess higher lifetime value even when its immediate output is similar.
29. Lifetime Adaptability
A Lifetime Adaptability score may compare realized future options with the best feasible option set:
\[
LA
=
\frac{
V(R_{F,\text{plan}})
}{
V(R_{F,\text{best feasible}})
}.
\]
This should not reward unused capacity without justification.
Oversizing every system is not efficient.
Adaptability should be based on:
plausible future demand;
cost of providing flexibility now;
cost of retrofitting later;
probability of future change;
and value preserved through modularity.
30. Maintenance as Part of Construction
A project is not complete when it becomes difficult to inspect, repair, or replace.
Maintenance pathways should be designed before construction.
Questions include:
Can components be reached?
Can failures be isolated?
Can one part be replaced without destroying another?
Are inspection points available?
Are records preserved?
Are replacement parts standardized?
Can hazardous energy be safely controlled?
Can maintenance occur without unnecessary shutdown of the complete system?
A cheap installation with inaccessible maintenance may be a high-cost lifetime failure.
31. Resilience and Maintainability
A Resilience and Maintainability score should evaluate:
fault isolation;
repair access;
spare capacity;
redundancy;
modular replacement;
inspection capability;
recovery time;
and availability of documentation.
Redundancy must not automatically be classified as waste.
A backup pump, alternate circuit, structural reserve, or independent safety system may appear underutilized during normal operation while providing enormous value during failure.
> Unused capacity is not waste when its purpose is resilience against a credible risk.
32. Stewardship
The missing word beneath engineering efficiency is stewardship.
Engineering uses:
land;
minerals;
forests;
water;
energy;
ecosystems;
human labor;
community space;
and resources inherited from the Earth.
A project is not efficient merely because its waste disappears from its own accounting.
If the burden is transferred to:
workers;
nearby communities;
rivers;
air;
wildlife;
taxpayers;
or future generations,
the cost has not been eliminated.
It has been externalized.
> Cost transferred is not cost eliminated.
33. Stewarded Value
A stewarded project value may be represented as:
\[
V_{\text{stewarded}}
=
V_{\text{direct}}
+
V_{\text{secondary}}
+
V_{\text{future}}
+
C_{\text{avoided}}
-
C_{\text{externalized}}.
\]
Externalized costs may include:
pollution;
habitat destruction;
groundwater depletion;
unsafe labor;
uncompensated community disruption;
long-term toxic waste;
climate effects;
irreversible material loss;
and infrastructure imposed upon future generations without adequate support.
The value of a project should not increase by moving its costs outside the chosen boundary.
34. Stewardship Score
A Stewardship score should compare the project with the best feasible environmental and social performance under equivalent functional requirements.
\[
ST
=
\frac{
P_{\text{stewardship, realized}}
}{
P_{\text{stewardship, best feasible}}
}.
\]
Because stewardship contains unlike dimensions, its components should first be reported separately:
energy intensity;
water use;
land disturbance;
recoverable material;
emissions;
toxicity;
worker exposure;
community impact;
ecological restoration;
and end-of-life recovery.
The combined score should never conceal catastrophic weakness in one category.
35. Non-Negotiable Gates
Efficiency calculations begin only after essential obligations are satisfied.
The proposed gates are:
safety;
structural integrity;
essential quality;
legal and regulatory compliance;
and minimum environmental protection.
Let each gate be represented by:
\[
G_i\in\{0,1\}.
\]
Then:
\[
G
=
G_{\text{safety}}
G_{\text{structure}}
G_{\text{quality}}
G_{\text{legal}}
G_{\text{environment}}.
\]
If any essential gate equals zero:
\[
G=0.
\]
The plan does not receive a valid efficiency score.
A shortcut that creates unacceptable danger is not efficiency.
A reuse pathway that contaminates water is not stewardship.
A multipurpose structure that compromises structural integrity is not intelligent design.
36. The Engineering Planning Portfolio
The proposed planning portfolio contains ten dimensions:
\[
\mathcal{P}
=
\{
AE,TE,RU,BR,EOM,DIL,AC,LA,RM,ST
\}.
\]
Where:
\(AE\) = Action Economy;
\(TE\) = Transition Economy;
\(RU\) = Resource Utilization;
\(BR\) = By-Product Routing;
\(EOM\) = Effective Output Multiplicity;
\(DIL\) = Downstream Industrial Leverage;
\(AC\) = Avoided-Cost Capture;
\(LA\) = Lifetime Adaptability;
\(RM\) = Resilience and Maintainability;
\(ST\) = Stewardship.
The portfolio explains how the plan performs.
It should not be hidden behind one number.
37. Normalization
Each portfolio category should be normalized to a score between 0 and 1:
\[
0\leq s_i\leq1.
\]
A value of:
0 indicates complete failure in the measured category;
0.5 indicates partial achievement;
1 indicates the best feasible performance under declared constraints.
The phrase best feasible is essential.
The benchmark must respect:
available technology;
geography;
geology;
project scale;
safety;
budget;
timing;
legal requirements;
demand;
and environmental limits.
The denominator cannot be an imaginary perfect project.
38. Engineering Planning Portfolio Score
The overall Engineering Planning Portfolio Score may be written:
\[
EPPS
=
100
\sum_{i=1}^{n}w_is_i,
\]
where:
\[
\sum_{i=1}^{n}w_i=1.
\]
The weights should reflect project priorities.
A tunnel project may place greater weight on:
transition economy;
material routing;
and lifetime maintenance.
An electrical system may place greater weight on:
reliability;
energy loss;
access;
and adaptability.
A water project may place greater weight on:
stewardship;
resilience;
water recovery;
and downstream consequences.
Weights must be declared before final scoring to prevent manipulation.
39. Suggested Initial Interpretation
Before empirical calibration, an initial planning interpretation could be:
\[
85\text{–}100
=
\text{strongly integrated plan},
\]
\[
70\text{–}84
=
\text{workable plan with identifiable improvements},
\]
\[
50\text{–}69
=
\text{substantial replanning required},
\]
\[
0\text{–}49
=
\text{poorly integrated plan}.
\]
These ranges are proposed planning categories.
They are not yet validated universal engineering standards.
Different project classes will require separate calibration.
40. The Weakest-Boundary Score
A weighted average can conceal a dangerous failure.
A project may score highly in:
labor economy;
output value;
material recovery;
and scheduling,
while scoring terribly in:
safety;
maintenance;
water impact;
or environmental stewardship.
The Weakest-Boundary Score is:
\[
WBS
=
100\min(s_1,s_2,\ldots,s_n).
\]
The portfolio score tells how the project performs overall.
The Weakest-Boundary Score identifies the category most likely to transfer cost, produce failure, or limit the complete system.
> The weak boundary always pays—or makes another boundary pay.
41. Minimum Category Thresholds
A project should not pass solely because its strong categories overwhelm a severe weakness mathematically.
A planning organization may require:
\[
WBS\geq W_{\min}.
\]
For example, a project could require every non-gate category to score at least 60 before approval.
The exact threshold should be calibrated by project type and risk.
This prevents a high average from legitimizing one unacceptable planning failure.
42. Engineering SEQ
SEQ can provide the larger judgment:
\[
SEQ_{\text{engineering}}
=
\frac{
V_{\text{realized, risk-adjusted lifetime}}
}{
V_{\text{best feasible, risk-adjusted lifetime}}
}.
\]
The numerator represents the complete value of the proposed or completed project.
The denominator represents the best feasible value available under actual constraints.
Therefore:
\[
0\leq SEQ_{\text{engineering}}\leq1.
\]
SEQ answers:
> How close is the project to the best feasible whole-job architecture?
The portfolio answers:
> Why is the project close—or why is it not?
Thus:
> SEQ gives the judgment. The portfolio identifies the pathways producing that judgment.
43. Financial and Nonfinancial Ledgers
Not every project value should be converted into money.
The system should use at least two coordinated ledgers.
Financial and material ledger
This includes:
capital cost;
labor;
energy;
transport;
processing;
disposal;
revenue;
avoided purchases;
maintenance;
decommissioning;
and recoverable material.
Systems and stewardship ledger
This includes:
safety;
resilience;
environmental impact;
accessibility;
adaptability;
community burden;
ecological value;
and irreversible loss.
Monetary valuation can inform decisions.
It should not erase values that cannot be honestly priced.
44. The Whole-Job Value Equation
A conceptual whole-job value equation is:
\[
V_J
=
\sum_{i=1}^{n}V_{O_i}
+
V_{\text{downstream}}
+
V_{\text{future}}
+
C_{\text{avoided}}
-
C_{\text{direct}}
-
C_{\text{processing}}
-
C_{\text{transport}}
-
C_{\text{storage}}
-
C_{\text{maintenance}}
-
C_{\text{decommissioning}}
-
C_{\text{externalized}}.
\]
Where:
\(V_{O_i}\) is the value of each substantial output;
\(V_{\text{downstream}}\) is value enabled in connected systems;
\(V_{\text{future}}\) is plausible future-use value;
\(C_{\text{avoided}}\) is prevented expense;
and the remaining terms represent the complete cost portfolio.
This equation should be used as an accounting framework, not as a claim that every value can be measured perfectly.
45. The Planning Cycle
The proposed planning cycle contains seven stages.
Stage 1: Define
Specify the primary function, project boundary, constraints, time horizon, and non-negotiable requirements.
Stage 2: Map
Identify inputs, actions, transitions, outputs, by-products, destinations, externalities, and future possibilities.
Stage 3: Route
Assign every material, energy, data, space, and by-product stream to a planned destination.
Stage 4: Score
Calculate the portfolio, Weakest-Boundary Score, gates, and engineering SEQ.
Stage 5: Challenge
Identify unnecessary actions, repeated transitions, unused outputs, transferred costs, inaccessible maintenance, and lost future route-space.
Stage 6: Replan
Change sequencing, geometry, staging, material selection, interfaces, destinations, or partnerships.
Stage 7: Rescore
Repeat until the plan reaches an acceptable portfolio and no critical weak boundary remains.
The complete instruction is:
\[
\boxed{
\text{Calculate. Identify waste. Replan. Calculate again.}
}
\]
46. The Preconstruction Requirement
The framework is most valuable before work begins.
After construction:
labor has been spent;
materials have been committed;
routes have been closed;
waste has been generated;
and future adaptability may have been lost.
Preconstruction scoring allows planners to discover preventable waste while change remains inexpensive.
> The best time to remove an unnecessary action is before anyone performs it.
> The best time to assign a by-product destination is before the by-product exists.
> The best time to preserve future access is before the wall is closed.
47. Action Mapping
Each major task should be mapped as a sequence:
\[
A_1
\rightarrow
T_1
\rightarrow
A_2
\rightarrow
T_2
\rightarrow
A_3.
\]
The team should then ask:
Can two actions occur together?
Can a transition be removed?
Can work be staged before crossing?
Can one inspection satisfy several requirements?
Can one excavation support several compatible functions?
Can one machine setup produce several parts?
Can one shutdown support several maintenance activities?
Can one data collection process serve several models?
Can temporary work become permanent infrastructure?
The purpose is not to compress work blindly.
It is to eliminate repetition lacking independent value.
48. Movement Mapping
Material movement should be recorded from origin to final destination.
For each material:
\[
\text{source}
\rightarrow
\text{handling}
\rightarrow
\text{processing}
\rightarrow
\text{transport}
\rightarrow
\text{placement}
\rightarrow
\text{future state}.
\]
Count:
loading events;
unloading events;
temporary storage;
transport distance;
elevation changes;
contamination risk;
damage risk;
and equipment changes.
Material handled five times may be more expensive than material transported farther but handled once.
49. Destination Mapping
No major output should be labeled simply as away.
A complete plan should specify whether each stream is routed to:
1. direct project use;
2. secondary project use;
3. another industry or project;
4. safe storage for a plausible future use;
5. environmental restoration;
6. recycling or reprocessing;
7. or unavoidable disposal.
“Disposed” is not a destination description.
The actual site, method, cost, risk, and long-term responsibility must be known.
50. Civil Engineering
In civil engineering, the framework can evaluate:
excavation balance;
cut-and-fill coordination;
road alignment;
tunnel spoil;
embankments;
drainage;
bridge access;
temporary roads;
utility corridors;
land restoration;
and future expansion.
Questions include:
Can excavated material replace imported fill?
Can a borrow pit become a reservoir or habitat?
Can temporary access become a permanent service road?
Can one trench carry several safely separated systems?
Can drainage serve flood control, water storage, and habitat?
Can bridge construction preserve future utility access?
51. Structural Engineering
Structural engineering can evaluate:
material efficiency;
modularity;
disassembly;
repair access;
reserve capacity;
reuse of components;
adaptable floor plans;
and end-of-life recovery.
Questions include:
Can structural elements serve more than one compatible function?
Can components be replaced without destroying adjacent systems?
Can connections support later adaptation?
Can material be recovered rather than crushed during demolition?
Does a small increase in initial cost prevent major future reconstruction?
52. Electrical Engineering
Electrical engineering can evaluate:
conversion losses;
waste heat;
conductor sizing;
power-factor correction;
regenerative energy;
modular distribution;
shared pathways;
fault isolation;
storage;
monitoring;
and future capacity.
Questions include:
Can braking energy be recovered?
Can waste heat be used?
Can spare conduit prevent later demolition?
Can one sensor network serve several operational needs?
Can systems be isolated without shutting down the entire facility?
Is redundancy protective or merely duplicated without purpose?
53. Mechanical Engineering
Mechanical engineering can evaluate:
component count;
motion;
friction;
heat;
tool changes;
maintainability;
energy recovery;
modular replacement;
and part reuse.
Questions include:
Can one motion accomplish several compatible operations?
Can rejected heat become process heat?
Can tool changes be reduced by better sequencing?
Can high-wear components be replaced independently?
Can the machine recover energy during deceleration?
Can one component safely serve structural and operational roles?
54. Chemical Engineering
Chemical engineering can evaluate:
heat integration;
solvent recovery;
reaction selectivity;
water reuse;
pressure recovery;
by-product markets;
catalyst regeneration;
and closed-loop material flows.
Questions include:
Can one process stream preheat another?
Can a by-product become feedstock elsewhere?
Can solvents be recovered?
Can pressure be converted into useful work?
Can wastewater be separated into usable fractions?
Can a hazardous waste pathway be prevented through process redesign?
55. Environmental Engineering
Environmental engineering can evaluate:
water recovery;
nutrient capture;
biogas;
runoff;
adsorption media;
soil restoration;
heat recovery;
material regeneration;
and ecological effects.
Questions include:
Can wastewater treatment also recover nutrients and energy?
Can stormwater infrastructure create habitat?
Can treatment media be regenerated?
Can waste heat support drying or biological treatment?
Can a remediation project leave useful land rather than only removed contamination?
56. Industrial Engineering
Industrial engineering directly addresses:
workflow;
staging;
batching;
inventory;
movement;
bottlenecks;
handoffs;
waiting;
setup time;
and quality control.
The whole-job framework extends this analysis beyond factory output to include:
resource provenance;
by-product destinations;
environmental burden;
future adaptability;
and downstream leverage.
The question becomes not only:
> “How quickly does the line produce?”
It becomes:
> “How intelligently does the complete system convert every necessary input and consequence into value?”
57. Software and Systems Engineering
Software engineering produces no excavation spoil, but it still produces:
duplicated processing;
unused data;
incompatible interfaces;
maintenance burdens;
security risks;
energy consumption;
and future lock-in.
Questions include:
Can one verified data source serve several applications?
Are modules reusable?
Are interfaces standardized?
Is provenance preserved?
Can systems be updated independently?
Is duplicate computation necessary?
Does short-term speed create long-term technical debt?
The same whole-job grammar applies.
58. Aerospace Engineering
Aerospace systems are strongly constrained by mass, energy, reliability, and access.
Questions include:
Can one component safely serve several functions?
Can heat be recovered or redistributed?
Can water and air be recycled?
Can vehicles or stages be reused?
Can systems be repaired in place?
Can modularity reduce replacement mass?
Does multifunctionality create dangerous common-mode failure?
The portfolio prevents the pursuit of multifunctionality from overriding reliability.
59. Biomedical Engineering
Biomedical engineering must place patient safety and clinical effectiveness above output multiplicity.
Within those gates, the framework can evaluate:
combined sensing and treatment;
reduced procedures;
modular replacement;
sterilization;
recoverable materials;
data reuse;
repair access;
and full patient pathways.
A device that performs several functions is not superior when coupling those functions increases failure risk.
The correct objective remains compatible value under non-negotiable safety constraints.
60. Construction as a General Application
Construction of every scale contains:
material origin;
removal;
placement;
movement;
staging;
temporary work;
utilities;
access;
waste;
inspection;
maintenance;
and later modification.
Even a small job should ask:
Can trips be combined?
Can materials be staged once?
Can demolition occur selectively?
Can usable components be preserved?
Can future access be left open?
Can one temporary action serve the permanent job?
Can disposal be reduced?
Can the next worker understand what was built?
The scale changes.
The planning grammar does not.
61. Avoiding False Efficiency
Several apparent efficiencies are actually cost transfers.
Overloading workers
Fewer trips are not efficient if the load becomes unsafe.
Eliminating redundancy
Fewer components are not efficient if failure becomes catastrophic.
Combining incompatible systems
Shared routes are not efficient when they create contamination, interference, fire, or maintenance risk.
Reusing unsuitable materials
Reuse is not efficient when quality or durability is compromised.
Delaying maintenance
Lower current cost is not efficient when failure cost increases disproportionately.
Exporting waste
A clean project site is not proof of stewardship when the burden has merely been moved elsewhere.
> A plan is not efficient when its apparent gain depends upon hiding the cost.
62. Preventing Score Manipulation
Any scoring method can be manipulated unless its boundaries are declared.
The project must publish or preserve:
the system boundary;
the baseline;
the time horizon;
the weights;
the assumed service life;
the discount method;
excluded costs;
externalized effects;
uncertainty ranges;
and the definition of best feasible performance.
The scoring record should show why each value was assigned.
Large or public projects should receive independent review.
63. Baseline Selection
The force multiplier depends on the baseline.
A project can appear highly efficient when compared with an intentionally poor alternative.
The baseline should be:
technically credible;
legally compliant;
functionally equivalent;
and representative of ordinary feasible practice.
The best-feasible benchmark should be a real alternative architecture, not an impossible ideal.
64. Weight Declaration
Weights can determine the final portfolio score.
They should therefore be established:
before final design selection;
by relevant disciplines;
with public or stakeholder review where appropriate;
and with reasons documented.
A project should also report sensitivity analysis showing how the result changes under alternative reasonable weights.
If a project is efficient only under one highly selective weighting scheme, the conclusion is weak.
65. Double Counting
Value must not be counted twice.
For example, material sold to another project may produce:
sales revenue;
avoided disposal;
and downstream value.
These are distinct only when they represent distinct effects.
The same underlying benefit should not be entered repeatedly under different names.
The ledger should identify each causal pathway.
66. Uncertainty
Early planning contains uncertainty.
Scores should therefore include ranges:
\[
s_i
\in
[s_i^{-},s_i^{+}].
\]
The portfolio may report:
expected score;
conservative score;
optimistic score;
and confidence level.
Projects with uncertain by-product markets should not receive full credit before agreements, demand, quality, and transport pathways are established.
67. Sensitivity Analysis
A strong plan should remain strong when reasonable assumptions change.
Test:
fuel prices;
labor cost;
material value;
transport distance;
demand;
service life;
maintenance frequency;
environmental cost;
and future expansion.
If one assumption collapses the complete value portfolio, the project may be fragile.
68. The Weak Boundary
TSTOEAO repeatedly identifies the weak boundary as the location where cost accumulates.
In engineering, the weak boundary may be:
a handoff;
a joint;
an interface;
a transport bottleneck;
an inaccessible component;
a disposal site;
a community receiving pollution;
a worker carrying an unsafe burden;
or a future owner inheriting undocumented infrastructure.
The score should identify the weakness before the project commits material and labor.
> The overall project is not stronger than the boundary through which its unresolved cost must eventually pass.
69. Expression Becomes Future Architecture
The completed project becomes part of the conditions governing later projects.
\[
V_n
\rightarrow
Y_{n+1}.
\]
A road enables settlement.
A utility corridor enables development.
A tunnel enables transportation and later services.
A waste stream creates either environmental burden or future feedstock.
A building creates either adaptable space or rigid future constraint.
A factory creates either recoverable infrastructure or expensive contamination.
> What the project produces changes what society can produce next.
70. The Planning Record
Every major project should preserve a whole-job planning record containing:
project purpose;
system boundary;
input inventory;
action map;
transition map;
material-flow map;
output inventory;
by-product destinations;
externality assessment;
future-use analysis;
maintenance pathway;
gates;
portfolio scores;
weakest-boundary score;
SEQ calculation;
rejected alternatives;
and reasons for final selection.
This creates engineering provenance.
Future operators can understand not only what was built, but why its pathways were chosen.
71. Replanning as Success
A low preliminary score should not be treated as an embarrassment.
It means the scoring method worked early enough to matter.
A poor result may reveal:
repeated movement;
poor staging;
unnecessary material purchase;
missing destinations;
inaccessible maintenance;
weak stewardship;
false redundancy;
insufficient redundancy;
or lost future route-space.
The response should be:
\[
\text{weak score}
\rightarrow
\text{identified cause}
\rightarrow
\text{revised architecture}.
\]
> The failure is not receiving a bad planning score. The failure is proceeding after the score has shown that the plan is bad.
72. A Minimum Practical Guide
A simplified version can be applied through twelve questions.
1. What is the primary deliverable?
2. What enters the job?
3. What must be removed?
4. What must be placed?
5. How many times will each item be handled?
6. Which transitions can be reduced or combined?
7. What secondary outputs will be created?
8. Where will every by-product go?
9. Can another project or industry use it?
10. What costs are being transferred outside the project?
11. What future uses or repairs should be preserved?
12. Does the revised plan pass all gates and score better than the first plan?
This is the accessible front end of the larger calculation.
73. What Would Strengthen the Framework?
The framework would be strengthened if:
1. independent teams can score the same plan with reasonable agreement;
2. high-scoring plans produce lower lifetime cost and waste;
3. transition scores predict labor, delay, and accident exposure;
4. by-product routing scores predict actual recovered value;
5. the Weakest-Boundary Score identifies later failures;
6. engineering SEQ predicts project resilience and adaptability;
7. the method transfers across engineering disciplines;
8. rescoring after redesign produces measurable improvement;
9. and historical project data can calibrate category thresholds.
74. What Would Weaken the Framework?
The framework would be weakened if:
scores depend mainly upon subjective preference;
weights are manipulated after results are known;
the same benefit is counted repeatedly;
speculative future value is treated as guaranteed;
high scores fail to predict better outcomes;
the portfolio adds complexity without improving decisions;
project boundaries exclude major costs;
externalities cannot be incorporated meaningfully;
or simpler existing methods consistently perform better.
A planning system that always declares the chosen design efficient is not a planning system.
It is a justification device.
75. Claim Discipline
This paper does not claim:
that every project should produce several products;
that every by-product is valuable;
that all repetition is waste;
that redundancy should be eliminated;
that every material should be reused;
that every engineering value can be converted into money;
that one portfolio replaces discipline-specific engineering analysis;
that the proposed thresholds are already validated;
or that \(V=E\times Y\) is presently a universal quantitative engineering law.
The framework is a general systems-planning method.
It must operate alongside:
structural analysis;
electrical standards;
materials testing;
environmental review;
clinical requirements;
safety engineering;
legal compliance;
and discipline-specific judgment.
76. Central Propositions
> Plan the whole job, not merely the named deliverable.
> Efficiency begins by eliminating unnecessary actions rather than demanding that workers perform unnecessary actions faster.
> Every transition should justify its cost.
> Where safe and practical, consolidate compatible work before crossing an expensive boundary.
> Every removal has a destination, and every placement has a source.
> Waste may be an unrouted output rather than a useless material.
> More outputs are not automatically better; more compatible lifetime value is better.
> The strongest project does not merely complete itself. It increases productive route-space for other systems.
> Avoided disposal and avoided replacement purchases are real value.
> Future adaptability must be designed before present construction closes the pathway.
> Unused capacity is not waste when it provides necessary resilience.
> Cost transferred is not cost eliminated.
> A high average score must not conceal a critically weak boundary.
> SEQ gives the overall judgment; the portfolio identifies the reasons.
> A poor planning score is a warning to replan before irreversible work begins.
> What a project produces changes what society can produce next.
Conclusion
Engineering is often praised for accomplishing difficult primary objectives.
The bridge stands.
The tunnel opens.
The building operates.
The electrical system delivers power.
The machine performs its function.
The water flows.
The software runs.
These accomplishments matter.
They do not prove that the whole job was planned well.
A complete project also contains:
every unnecessary trip;
every repeated transition;
every wasted material;
every by-product;
every transport route;
every inaccessible component;
every environmental burden;
every maintenance obligation;
and every future opportunity either preserved or destroyed.
The engineering question must therefore expand from:
> “Did the project work?”
to:
> “How completely and intelligently did the project convert all necessary inputs and consequences into compatible lifetime value?”
The TSTOEAO framework provides a way to ask that question systematically.
\[
V_{\text{project}}
=
E_{\text{project}}
\times
Y_{\text{plan}}.
\]
Labor, material, equipment, energy, information, and capital are opportunities.
The plan determines how those opportunities are routed.
The same quantity of effort can produce:
one product and several liabilities;
or several coordinated products, avoided costs, adaptable pathways, and downstream opportunities.
The difference is encoded in the architecture.
The framework therefore begins with the complete job:
\[
J=
\{
I,A,T,O,B,D,X,F
\}.
\]
Inputs are inventoried.
Actions are challenged.
Transitions are compressed.
Outputs are counted honestly.
By-products are routed.
Destinations are specified.
Externalized costs are restored to the ledger.
Future route-space is preserved.
The plan is then evaluated through:
\[
\mathcal{P}
=
\{
AE,TE,RU,BR,EOM,DIL,AC,LA,RM,ST
\}.
\]
The Engineering Planning Portfolio Score summarizes overall performance.
The Weakest-Boundary Score prevents one severe failure from hiding beneath a strong average.
Non-negotiable gates prevent unsafe or environmentally destructive shortcuts from being mislabeled as efficiency.
Engineering SEQ compares the proposed system with the best feasible system:
\[
SEQ_{\text{engineering}}
=
\frac{
V_{\text{realized, risk-adjusted lifetime}}
}{
V_{\text{best feasible, risk-adjusted lifetime}}
}.
\]
The calculations do not exist to decorate a completed decision.
They exist to challenge the decision before it becomes concrete, steel, wiring, machinery, contamination, debt, or irreversible land use.
The practical instruction is direct:
\[
\boxed{
\text{Map the whole job.}
}
\]
\[
\boxed{
\text{Calculate the portfolio.}
}
\]
\[
\boxed{
\text{Find the weak pathways.}
}
\]
\[
\boxed{
\text{Replan the job.}
}
\]
\[
\boxed{
\text{Calculate again.}
}
\]
At the smallest scale, this means staging several pieces of material before crossing the same boundary once.
At the largest scale, it means coordinating cities, tunnels, electrical systems, factories, water networks, transportation, land restoration, material recovery, and future industries as parts of one complete architecture.
The scale changes.
The principle does not.
The purpose of engineering should not be to consume the greatest quantity of labor, material, and energy while eventually producing an acceptable object.
Its purpose should be to produce the greatest safe, durable, compatible, and stewarded value from every necessary action.
A civilization is not advanced merely because it can build large projects.
It is advanced when it can see the complete pathway created by those projects.
It is advanced when removal and placement are coordinated.
It is advanced when one project supplies another.
It is advanced when waste becomes feedstock where appropriate.
It is advanced when maintenance remains possible.
It is advanced when future generations inherit route-space rather than hidden liabilities.
It is advanced when its engineers understand that the Earth’s resources are not merely available inputs.
They are a stewardship responsibility.
The final proposition is:
\[
\boxed{
\text{A well-engineered project does not merely complete the job.}
}
\]
\[
\boxed{
\text{It multiplies the value of every necessary action while preserving the pathways through which future value can still emerge.}
}
\]
References
Ashby, M. F. (2016). Materials and Sustainable Development. Butterworth-Heinemann.
Deming, W. E. (1986). Out of the Crisis. Massachusetts Institute of Technology, Center for Advanced Engineering Study.
Graedel, T. E., and Allenby, B. R. (2010). Industrial Ecology and Sustainable Engineering. Pearson.
Meadows, D. H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing.
McDonough, W., and Braungart, M. (2002). Cradle to Cradle: Remaking the Way We Make Things. North Point Press.
Womack, J. P., and Jones, D. T. (2003). Lean Thinking: Banish Waste and Create Wealth in Your Corporation. Free Press.
Swygert, J. (2026). The Computer Cannot Work Without It: Computation, Voice Recognition, and Operational Proof of Encoded Equilibrium. Ivory Tower Publishing.
Swygert, J. (2026). The Disease Builds Its Own Pathway: Pathological Equilibrium and the Self-Construction of Illness. Ivory Tower Publishing.
Swygert, J. (2026). The Mine and the Monument: Excavation as a Civilizational Force Multiplier: How Ancient and Modern Builders Convert Removed Material, Created Space, and Necessary Labor into Multiple Layers of Value. Ivory Tower Publishing.
Swygert, J. (2026). The Organism Builds Its Own Pathway: Fertilization, Embryonic Development, and the Self-Construction of Encoded Equilibrium. Ivory Tower Publishing.
Swygert, J. (2026). Operationalizing Boundary Portfolio Engineering. Ivory Tower Publishing.
Swygert, J. (2026). The Swygert Theory of Everything AO. Ivory Tower Publishing.
Comments
Post a Comment