Friday, August 14, 2026

The Magnetic Construction Spine: Adapting Ultra-High-Performance Maglev for Vertical Logistics in Megatall Construction: From an 800 km/h electromagnetic test vehicle to a new way of moving materials through kilometer-high buildings

The Magnetic Construction Spine: Adapting Ultra-High-Performance Maglev for Vertical Logistics in Megatall Construction:

From an 800 km/h electromagnetic test vehicle to a new way of moving materials through kilometer-high buildings

John Swygert
August 14, 2026

Abstract

A recent wave of attention surrounding China's high-speed magnetic-levitation research has focused understandably on velocity. At Donghu Laboratory in Hubei Province, researchers demonstrated a 1.11-ton test vehicle accelerated from rest to approximately 800 km/h in 5.3 seconds on a one-kilometer test line. The achievement demonstrates extraordinary advances in high-power electromagnetic propulsion, levitation control, positioning, power delivery, and braking. Chinese reporting has additionally identified vertical magnetic elevators and inclined industrial conveyors as potential configurations of the same underlying technology.

For civil engineering, however, the most transformative application may have little to do with transporting passengers at extreme speed.

This article proposes adapting high-force linear-motor and magnetic-transport technology into a Magnetic Construction Spine (MCS): a temporary or semi-permanent vertical logistics system capable of transporting construction materials through supertall and megatall structures independently of conventional cranes. Rather than attempting to replace tower cranes, the system would separate two jobs that cranes currently perform simultaneously: transport and placement. Materials could travel rapidly through a constrained guideway to the active construction zone, where cranes, robotic manipulators, or short-range lifting systems would perform final positioning.

Such an architecture could become increasingly valuable as buildings move from hundreds of meters toward one kilometer and beyond.


The Important Part of the Chinese Record Is Not 800 km/h

Recent English-language reporting described the Donghu Laboratory system as an experimental Chinese "bullet train" capable of accelerating from zero to 800 km/h in approximately 5.3 seconds. More precisely, the demonstration involved a roughly 1.11-ton high-speed maglev test vehicle operating on a one-kilometer experimental line. The underlying achievement involved electromagnetic propulsion, levitation support, high-power energy delivery, precise control, and controlled braking.

The acceleration involved is extraordinary. Reaching 800 km/h in 5.3 seconds corresponds to an average acceleration of roughly 42 m/s², or approximately 4.3 g.

Nothing approaching that acceleration would be desirable for ordinary construction logistics.

But it does not have to be.

A construction system might operate at only a small fraction of those speeds and accelerations while still radically outperforming existing vertical-material workflows.

The more important discovery is architectural: electromagnetic propulsion does not intrinsically care whether its path is horizontal.

Chinese descriptions of the technology have explicitly noted that changing coil arrangements permits different directions of travel: horizontally for high-speed transportation, vertically for magnetic elevators, and at an incline for industrial material transport.

That observation opens an entirely different civil-engineering question:

What happens when the high-performance magnetic transport corridor becomes part of the construction site itself?


The Vertical-Logistics Problem Gets Worse as Buildings Get Taller

Construction already depends heavily upon vertical logistics.

Modern high-rise projects employ tower cranes, construction hoists, concrete pumps, material platforms, temporary elevators, and increasingly sophisticated scheduling systems simply to keep labor and materials reaching the advancing construction front.

Conventional rack-and-pinion construction hoists illustrate both the maturity and the limitations of the present approach. Commercial systems commonly carry loads in the range of several tonnes, with high-rise models reaching speeds around 90–100 meters per minute. Alimak, one of the major manufacturers of these systems, lists construction-hoist capacities reaching approximately 3,500 kg in standard ranges and speeds around 100 m/min for some configurations.

That performance is impressive.

But 100 m/min is only about 1.67 m/s.

At one kilometer of vertical travel, a theoretical nonstop trip at that speed takes approximately ten minutes before loading, unloading, stops, queuing, or repositioning are considered.

A magnetically propelled freight carrier traveling at a relatively conservative 10 m/s could cover the same vertical distance in roughly 100 seconds before acceleration and braking allowances.

At 20 m/s, the cruise portion falls toward 50 seconds.

Neither speed approaches the Chinese experimental vehicle's performance. Yet either could represent a dramatic change in vertical construction throughput.


Megatall Construction Makes the Problem Visible

The problem becomes particularly obvious when considering the next generation of megatall structures.

Saudi Arabia's Jeddah Tower, also known as the Jeddah Economic Company Tower, is designed to exceed one kilometer in height and surpass Dubai's 828-meter Burj Khalifa. Kingdom Holding Company formally announced the agreement to complete the project in October 2024, and construction subsequently resumed.

By August 2026 the tower had reached approximately Level 107 and more than 430 meters in height, according to project leadership and contemporary reporting. It still has hundreds of vertical meters remaining before completion.

At these scales, vertical distance becomes part of the manufacturing problem.

A construction site is effectively a moving factory whose production floor continually relocates upward.

Every piece of reinforcement, formwork, façade material, mechanical equipment, electrical equipment, piping, fastener, tool, prefabricated assembly and replacement component eventually has to follow it.

The taller the tower becomes, the more time and equipment capacity can be consumed merely transporting matter from one elevation to another.


A Magnetic Construction Spine

The proposed Magnetic Construction Spine would treat vertical logistics as a dedicated transportation network rather than as an incidental function of cranes.

A high-capacity guideway could be temporarily attached to the exterior structure, incorporated into the advancing structural core, or installed inside a future elevator/service shaft.

Independent cargo carriers would move along the guideway using linear electromagnetic propulsion.

A basic system could contain:

  1. Ground-level loading stations where pallets, rebar bundles, equipment, prefabricated components and sealed material containers are secured into standardized carriers.

  2. Vertical electromagnetic guideways extending upward with the advancing structure.

  3. Multiple independently controlled cargo carriers, allowing one carrier to ascend while others descend, load, unload, or wait at intermediate levels.

  4. Transfer stations positioned at major construction zones.

  5. Mechanical locking systems at each loading and unloading level so the carrier becomes physically secured before workers or automated machinery approach it.

  6. Independent emergency braking and capture mechanisms that do not depend solely upon electromagnetic suspension.

  7. Automated routing and load identification, allowing materials to be dispatched to specified levels much like freight within an automated warehouse.

  8. A crane or robotic interface at the active construction deck, where the material leaves the vertical transportation system and undergoes its final short-distance movement.

The system therefore does not eliminate the crane.

It changes what the crane is asked to do.


Cranes Should Place Materials, Not Spend Their Lives Transporting Them

Tower cranes are extraordinarily capable machines, and some construction loads will always require their geometry and reach.

But transporting an object hundreds of meters upward and placing that object precisely are fundamentally different operations.

Today they are often combined into a single crane cycle.

The Magnetic Construction Spine would separate them.

A bundle of structural material could be loaded near ground level, accelerated upward through a physically constrained path, automatically slowed at the active construction level, mechanically secured, and then transferred to a crane.

The crane might move the load only the final 20, 40, or 80 meters to its installation point rather than lifting it hundreds of meters from ground level.

This separation has potentially profound consequences.

The expensive and schedule-critical crane becomes primarily a placement machine.

The magnetic system becomes the transport machine.

That means crane availability could increasingly be reserved for the operations at which cranes are uniquely valuable.


Why Magnetic Propulsion Is Especially Interesting

There is already a significant engineering precedent for vertical linear-motor transportation.

TK Elevator's experimental MULTI system replaces conventional elevator ropes with linear motors and allows multiple cabins to travel vertically and horizontally within a common network. The company explicitly describes the technology as derived from magnetic-levitation transportation principles and has demonstrated functioning prototypes.

So the fundamental concept of turning linear-motor transportation vertically is not speculative.

The civil-engineering question is different:

Can a ruggedized version be designed for construction freight rather than passengers?

That change may actually remove some constraints while creating others.

A material carrier does not require passenger comfort.

It can tolerate greater acceleration.

It does not require windows, decorative interiors, or conventional elevator ergonomics.

Its geometry can be optimized around standardized pallets, reinforcement bundles, façade panels, equipment crates or custom construction modules.

And because the carrier follows a constrained guideway rather than hanging freely from a crane hook, the system could eliminate load swing during the long vertical portion of transportation.

But construction creates another set of problems: concrete dust, rain, steel debris, misalignment, vibration, impact, welding contamination, temperature variation, structural movement and continuously changing geometry.

For that reason, the most practical system might not be a perfectly contactless "maglev elevator."

It might instead be a hybrid electromagnetic freight system using linear motors for propulsion while retaining mechanical guide wheels, emergency rails, capture devices and structural locks.

The lesson from maglev may therefore be electromagnetic propulsion rather than levitation for its own sake.


Multiple Carriers Could Change Throughput More Than Raw Speed

The greatest advantage might not even be velocity.

It may be parallelism.

Traditional hoists generally move a limited number of cars along fixed shafts. A magnetic transportation architecture could potentially operate multiple independently controlled carriers within a circulating system.

One carrier could be loading at ground level.

Another could be traveling upward.

Another could be unloading at Level 80.

Another could be descending with waste material, empty pallets or equipment requiring service.

A fifth could wait at the active construction deck.

This begins to resemble an automated warehouse turned vertically.

TK Elevator's MULTI concept already demonstrates the architectural idea of multiple linear-motor-driven cars operating without conventional ropes.

For construction, the concept could be optimized around tonnage per hour rather than passengers per hour.

That metric matters enormously.

A building does not care how fast one spectacular load can travel.

It cares how reliably thousands of loads arrive where they are needed throughout the working day.


The Energy Requirement Is Significant — But Not Absurd

Gravity still has to be paid.

No propulsion technology eliminates the energy required to raise mass through height.

A 10,000-kg payload lifted 1,000 meters gains approximately:

98.1 megajoules

of gravitational potential energy, equivalent to roughly:

27.3 kilowatt-hours

before carrier mass and system losses are included.

The surprising issue is therefore not necessarily total energy.

It is power.

Moving large loads rapidly requires delivering that energy in a short period. Accelerating a heavy carrier vertically at high speed could therefore require megawatt-scale instantaneous power even though the total energy for each trip is comparatively modest.

That suggests another useful design principle:

Construction maglev should optimize throughput and energy recovery, not headline acceleration.

Descending carriers could potentially return part of their gravitational energy to the electrical system through regenerative operation, while software could coordinate ascending and descending loads to reduce peak electrical demand.

The system could therefore behave less like a launcher and more like an intelligent vertical freight grid.


Concrete Is a Special Case

The first instinct when looking at a kilometer-high building is naturally to ask whether the magnetic system could replace concrete pumping.

Possibly — but this is where restraint is important.

The Burj Khalifa's construction established a vertical concrete-pumping record of approximately 606 meters using specially designed Putzmeister high-pressure equipment.

Modern specialized pumps can operate at enormous pressures, and concrete pumping is already a highly evolved technology.

Concrete also behaves differently from structural steel or a pallet of mechanical equipment.

Aggressive acceleration could cause sloshing, segregation or difficult transient loads within a container. Loading and cleaning containers adds complexity. Concrete has a finite working time. Continuous pumping also possesses an advantage that discrete transportation does not: once established, the pipeline provides a steady material stream.

So pumping should not simply be discarded.

But a hybrid architecture becomes extremely interesting.

Instead of forcing concrete through one extraordinarily long high-pressure pipeline, sealed concrete cartridges or hoppers could travel rapidly to elevated transfer stations through the magnetic spine.

A smaller local pump could then move concrete from the transfer station to the placement boom.

In principle:

ground batching → magnetic bulk lift → elevated buffer → local pumping → final placement

This would divide one extreme vertical pumping problem into two simpler transportation problems.

Whether this is economically superior would have to be determined experimentally, but it is sufficiently plausible to deserve engineering investigation.


The Best Early Cargo Is Probably Not Concrete

The first prototype should transport materials whose behavior is already predictable under acceleration.

Likely candidates include:

  • reinforcement steel;
  • formwork components;
  • steel connections and assemblies;
  • scaffolding components;
  • façade modules;
  • mechanical and electrical equipment;
  • pipe and duct assemblies;
  • pallets of fittings and fasteners;
  • tools;
  • prefabricated bathrooms and utility modules;
  • glazing components inside protective carriers;
  • replacement machinery and spare parts.

These loads consume enormous amounts of logistical effort while avoiding many of the fluid-dynamics problems associated with concrete.

A successful system handling this cargo alone could substantially change construction logistics before anyone attempted bulk concrete transport.


Safety Could Improve in Some Areas — While New Risks Appear

It would be irresponsible to describe electromagnetic lifting as automatically safer than cranes or conventional hoists.

It would eliminate some risks while introducing others.

A carrier constrained by a guideway would not behave like a freely suspended crane load during its long-distance vertical travel. Wind-induced swinging and some forms of load instability could therefore be reduced.

But a multi-ton electromagnetic carrier hundreds of meters above the ground creates obvious catastrophic-failure concerns.

A practical system would require multiple independent layers of protection:

  • mechanical emergency brakes;
  • passive anti-fall catches;
  • structural locking at stations;
  • redundant position sensing;
  • overspeed protection;
  • independent emergency power;
  • controlled power-loss behavior;
  • fire isolation;
  • debris monitoring;
  • structural alignment monitoring;
  • exclusion zones;
  • fail-safe load restraint;
  • redundant communications; and
  • physical containment wherever practical.

The system should never depend upon software or magnetic force alone to prevent a falling load.

Construction technology must assume that power will fail, sensors will fail, communication will fail, debris will enter the guideway, and workers will eventually do something the designer did not anticipate.

The machine should remain safe anyway.


The Guideway Could Grow With the Building

One of the most difficult design questions is also one of the most interesting.

A permanent railway is installed after its supporting structure exists.

A construction spine would have to climb with a structure that is still being created.

That suggests modular guideway segments perhaps one or several floors tall.

As the structural core advances, new electromagnetic stator and guideway modules could be attached above the previous section. Electrical bus, communications, braking rail and control systems would extend simultaneously.

The spine could therefore grow much like climbing formwork or temporary construction hoists already grow with tall structures.

At completion, several possibilities exist.

The system could be removed.

Parts could be repurposed elsewhere.

Or, if designed into the building from the beginning, the construction freight spine could become a permanent maintenance, logistics or service transportation system.

That final possibility is particularly intriguing.

The infrastructure used to construct a kilometer-high building might remain inside it afterward to maintain that building for the next century.


Jeddah Tower Is an Illustration of the Need, Not a Proposed Retrofit

The currently rising Jeddah Tower makes the scale of this problem tangible.

At more than 430 meters and Level 107 as of August 2026, it remains far below its intended ultimate height of more than one kilometer.

This article does not suggest that an unfinished experimental magnetic logistics system should suddenly be installed on that project.

The tower instead demonstrates where construction is heading.

Buildings approaching a kilometer in height force engineers to reconsider systems that worked adequately at 200, 300 or 500 meters.

The same thing occurred with foundations.

It occurred with wind engineering.

It occurred with concrete pumping.

It occurred with elevators.

It will inevitably occur with construction logistics.


A Rational Development Program

The concept does not require beginning with a kilometer-high tower.

The logical development sequence would be much smaller.

A first research installation might consist of a 30–50-meter vertical guideway and a payload measured in hundreds of kilograms.

The next stage could test several tonnes over 100–200 meters.

Engineers could evaluate:

  • energy consumption;
  • acceleration limits;
  • braking distance;
  • structural loads;
  • electromagnetic heating;
  • guideway tolerances;
  • wind effects;
  • contamination resistance;
  • payload stabilization;
  • carrier switching;
  • emergency stopping;
  • regenerative energy recovery;
  • automated loading;
  • maintenance requirements;
  • and tonnage delivered per hour.

Only after those systems were understood would the technology need to move toward supertall construction.

The goal would not be to prove that a load can travel absurdly fast.

China has already demonstrated the underlying ability to exert extraordinary controlled electromagnetic force on a ton-scale vehicle.

The civil-engineering problem is to make that force boring, reliable, rugged and useful.


From Faster Trains to Faster Buildings

Major technologies are often developed for one problem and become transformative when somebody rotates the problem ninety degrees.

Rail became elevators through a different mechanical architecture.

Aircraft technology transformed wind engineering.

Robotics developed for manufacturing migrated into construction.

Magnetic transportation may follow a similar path.

The achievement at Donghu Laboratory is presented primarily as a transportation breakthrough. That is entirely reasonable. Researchers are pursuing ultra-high-speed ground transportation and electromagnetic launch technologies.

But civil engineers should look at the machine and ask a different question.

Not:

How fast can it move a train?

But:

How much material can this principle move vertically, how precisely can it stop, and how reliably can it do so ten thousand times during the construction of a building?

That is a completely different engineering target.

And it may ultimately be just as consequential.

The skyscraper of the future may still have cranes at its summit.

But the cranes may no longer reach all the way to the ground.

Instead, materials could enter a high-capacity electromagnetic logistics network at the base of the structure, travel upward through a growing magnetic construction spine, emerge only a short distance from where they are needed, and be handed to cranes or robots for final placement.

In that architecture, magnetic propulsion does not replace construction equipment.

It reorganizes it.

The crane places.
The spine transports.
The building becomes its own vertical supply chain.

That is the possibility worth testing.

References

Donghu Laboratory / Hubei Province reporting on the 1.11-ton high-speed magnetic-levitation test vehicle and 800 km/h demonstration.

CCTV reporting on Donghu Laboratory's electromagnetic propulsion and high-speed magnetic transportation research.

Reporting describing horizontal, vertical and inclined configurations of electromagnetic propulsion technology.

The Independent, English-language coverage of the 800 km/h acceleration demonstration, August 13, 2026.

TK Elevator, MULTI rope-free linear-motor elevator technology and magnetic-transport-derived propulsion.

Alimak, contemporary rack-and-pinion construction-hoist capacities and operating speeds.

Putzmeister, Burj Khalifa high-rise concrete pumping and 606-meter vertical pumping record.

Kingdom Holding Company, Jeddah Economic Company Tower completion agreement and planned height exceeding 1,000 meters.

Current Jeddah Tower construction progress, including Level 107 and approximately 430 meters.

Friday, August 7, 2026

Body Slave ~ Lyrics / Poetry ~ Mobius∆Tripz

I want to harken back to the good old days
but that doesn't happen at this bitter old age
the best is all behind me
now I'm just a body slave.

every action I take today
is only to keep this body a vessel of transport,
and this soul within is old, and  older and tired and more tired and less and less I have 
and less for this body can I upon act and afford

now I'm just a body slave
more and more disciplined and less and less a dividend 
I can't pretend that's this is enjoyable or easy
but rather closer to an end

closer to an end
closer to that end
I'm definitely near that finish line
my bodies inevitable and imminent end

I'll launch from this mortal coil 
my energy mine again
no more a body slave
I'll soar with the Gods, soul evolved, no more reality pretend 

breaking the surly bonds
busting free from the chains that hold me down
exploding towards the heavens my wings sprout and evolve to flap instantaneously 
as if I had never been a body slave

but you first have to be a body slave
be vigilant and the course in faith you stay
do not your faith betray
blast into the forever afterlife and if worthy at long last remain to stay 

closer to an end
closer to that end
I'm definitely near that finish line
my bodies inevitable and imminent end

now I'm just a body slave
more and more disciplined and less and less a dividend 
I can't pretend that's this is enjoyable or easy
but rather closer to an end

every action I take today
is only to keep this body a vessel of transport,
and this soul within is old, and  older and tired and more tired and less and less I have 
and less for this body can I upon act and afford

I want to harken back to the good old days
but that doesn't happen at this bitter old age
the best is all behind me
now I'm just a body slave.

Saturday, August 1, 2026

The Provenance Protocol: Chain of Intellectual Custody from First Note to Final Publication

The Provenance Protocol: Chain of Intellectual Custody from First Note to Final Publication


DOI: Pending assignment


John Swygert


August 1, 2026


Abstract


Modern authorship is increasingly collaborative, tool-assisted, distributed, and difficult to reconstruct after publication. A book may involve an originating author, artificial intelligence systems, editors, ghostwriters, researchers, translators, designers, software, and publishers. Existing disclosure practices rarely preserve the full developmental history of the work.


This paper proposes the Provenance Protocol, a structured chain of intellectual custody beginning before drafting and continuing through publication. The protocol does not prescribe one acceptable route to authorship. It permits solo, collaborative, ghostwritten, AI-assisted, edited, translated, and mixed workflows. Its purpose is to make the chosen route explicit, updateable, verifiable, and accountable.


The protocol begins with an Authorship Process Declaration describing the intended creative method and anticipated contributors. It then preserves the originating note, outline, outline development, source record, contribution log, drafts, revisions, approvals, and publication record. Changes in method are documented rather than prohibited.


The paper distinguishes three levels of disclosure: a concise public statement, a more detailed verifiable project record, and a private evidentiary archive. It proposes metadata fields, version controls, contributor classifications, final authorship attestation, and amendment procedures.


The protocol is designed for implementation through the Secretary Suite system, but it may also be followed manually. Its central principle is:


> Declare the route, preserve the route, update the route, and accept responsibility for where the route leads.




1. Introduction


Authorship disputes often begin after the evidence needed to resolve them has disappeared.


A finished manuscript exists.


Its developmental history does not.


The publisher sees polished prose but cannot determine:


where the idea began;


whether the author developed an outline;


whether another person drafted the text;


whether AI produced substantial passages;


whether sources were verified;


whether revisions were directed by the named author;


or whether the author understands and accepts the final claims.



The finished artifact has become separated from its route.


That separation creates a provenance problem.


Provenance is the history of origin, development, transfer, and custody.


Chain of custody is the record preserving continuity across that history.


In authorship, the relevant chain is intellectual rather than merely physical.


It should answer:


> How did this idea become this book?




2. Authorship as a Route


A book does not appear in one step.


It travels through successive states:


\[

\text{intuition}

\rightarrow

\text{note}

\rightarrow

\text{question}

\rightarrow

\text{outline}

\rightarrow

\text{research}

\rightarrow

\text{draft}

\rightarrow

\text{criticism}

\rightarrow

\text{revision}

\rightarrow

\text{approval}

\rightarrow

\text{publication}.

\]


Each transition may involve different people, tools, and decisions.


The final language is therefore not the complete history of the work.


It is the endpoint of a route.


A valid provenance system must preserve enough of that route to distinguish:


origination from assistance;


suggestion from acceptance;


drafting from approval;


editing from replacement;


correction from concealment;


and publication responsibility from mechanical production.



3. Multiple Legitimate Routes


The protocol begins by rejecting the idea that all authentic books must follow one method.


Route A: Independent solo authorship


The author plans, researches, drafts, edits, and publishes without substantive generative or human writing assistance.


Route B: Conventional edited authorship


The author drafts the work and later works with developmental, line, copy, or proof editors.


Route C: Research-assisted authorship


Researchers gather evidence, conduct interviews, verify claims, or prepare background material under the author’s direction.


Route D: Ghostwritten authorship


The subject or directing author supplies the experiences, knowledge, objectives, and approval while a ghostwriter constructs substantial language.


Route E: Collaborative authorship


Multiple identified authors jointly develop the concepts and text.


Route F: AI-assisted authorship


The author uses AI for defined functions such as:


dialogue;


brainstorming;


organization;


critique;


comparison;


research assistance;


summarization;


drafting;


rewriting;


formatting;


citation assistance;


or voice refinement.



Route G: Mixed authorship


Several human and computational contributors perform separate roles.


The protocol does not rank these routes.


It records them.


4. The Authorship Process Declaration


Every project should begin with a dated Authorship Process Declaration.


This declaration identifies the anticipated route before the final work exists.


A general form is:


> Authorship Process Declaration — Version 1

This work originates with [name]. The originating author will direct the project and retain final approval and responsibility. The anticipated process includes [solo drafting / AI assistance / ghostwriting / editing / research assistance / collaboration]. The intended roles of each contributor or system are described below. This declaration will be updated if the process changes.




The declaration should contain:


project title or working title;


originating author;


date and time;


purpose;


expected audience;


anticipated contributors;


anticipated tools;


intended AI roles;


intended human-assistance roles;


disclosure level;


owner of final approval;


and process version.



The initial declaration is not a permanent restriction.


It is a starting record.


5. Amendment Rather Than Concealment


Creative methods change.


An author may begin alone and later hire an editor.


A project may begin without AI and later use AI for structural comparison.


A ghostwriter may add a researcher.


A publisher may require a translator.


The ethical requirement is not that the original plan never change.


The requirement is that the record change with it.


An amendment may state:


> Authorship Process Declaration — Version 2

On August 14, 2026, AI assistance was added for chapter-outline comparison and source organization. No AI-generated prose will be inserted without author review and revision.




A later amendment might state:


> Version 3

A developmental editor was added to evaluate continuity and argument order.




Changing routes is not deception.


Undocumented change creates the risk of deception.


6. The Originating Note


The chain should preserve the earliest identifiable expression of the work.


The originating note may be:


a typed paragraph;


a handwritten page;


a voice recording;


an email;


a conversation excerpt;


an image;


a diagram;


a question;


or a brief declaration of intent.



The note need not contain the whole theory or story.


Its purpose is to establish:


what first existed;


who expressed it;


when it was expressed;


and how the later work relates to it.



A useful originating note records:


1. The initial idea



2. The reason it matters



3. The intended direction



4. Known uncertainties



5. The anticipated next step




7. The Outline as Evidence


An outline is not merely a writing aid.


It is evidence of conceptual architecture.


A preserved outline shows that the author:


selected the major subjects;


arranged their relationships;


anticipated the sequence;


distinguished central claims from supporting material;


and developed the work before its final prose appeared.



The protocol should preserve:


the first outline;


every major revision;


added sections;


deleted sections;


reordered sections;


and reasons for substantial changes.



The outline may develop through stages:


\[

O_1

\rightarrow

O_2

\rightarrow

O_3

\rightarrow

O_f.

\]


Where:


\(O_1\) is the originating structure;


intermediate versions show development;


\(O_f\) is the final structural plan.



This chain is particularly valuable when AI or a ghostwriter assists with prose because it preserves evidence of the directing architecture.


8. The Source Record


A source record identifies the materials informing the work.


It should include:


title;


author;


publication;


date;


location or identifier;


date accessed;


relevant section;


claim supported;


verification status;


and whether AI located or summarized the source.



A source log should distinguish:


source text;


author interpretation;


AI summary;


independent verification;


and final use.



This prevents a common failure in AI-assisted research: a generated summary becoming detached from the source it supposedly represents.


The record should state when:


the source was read directly;


only an abstract was consulted;


the source was inaccessible;


the claim remains provisional;


or a citation was suggested but not verified.



9. The Contribution Log


A contribution log records who or what proposed each meaningful addition.


The log should distinguish:


9.1 Origination


Who first introduced the idea?


9.2 Expansion


Who developed it further?


9.3 Linguistic formulation


Who proposed the wording?


9.4 Selection


Who chose among alternatives?


9.5 Revision


Who changed the selected material?


9.6 Verification


Who confirmed its accuracy?


9.7 Approval


Who authorized inclusion in the final work?


A simple record might state:


Entry Contributor Proposed contribution Author decision Final status


014 AI assistant Three alternative chapter titles Modified by author Accepted

015 Author Commitment-state concept Expanded through dialogue Accepted

016 Editor Remove redundant example Approved Accepted

017 AI assistant Unsupported factual claim Rejected by author Excluded



The purpose is not to record every comma.


It is to preserve meaningful intellectual custody.


10. Suggestion Is Not Adoption


A system may generate twenty ideas.


The author may reject nineteen.


The one selected idea may then be rewritten beyond recognition.


A provenance system must not treat every suggestion as equivalent authorship.


The record should distinguish:


\[

\text{proposal}

\neq

\text{adoption}.

\]


And:


\[

\text{adoption}

\neq

\text{unchanged use}.

\]


Possible statuses include:


proposed;


rejected;


accepted;


accepted with modification;


merged;


superseded;


retained as background;


or removed after review.



This preserves the author’s judgment as an observable part of the process.


11. Draft and Version History


Every meaningful draft should receive:


project identifier;


version number;


date;


time;


contributor;


summary of changes;


source relationship;


and approval state.



A possible version structure is:


\[

1.0

\]


Initial full draft


\[

1.1

\]


Minor revisions


\[

2.0

\]


Major structural change


\[

2.1

\]


Post-review correction


\[

3.0

\]


Publication candidate


\[

3.1

\]


Published correction


Prior versions should not be overwritten when preserving them is reasonably possible.


A record can be maintained manually, through cloud history, through repository systems, or through dedicated provenance software.


12. Persistent Identity and Verification


Each project should receive a persistent identifier.


Each version may receive:


a unique version ID;


a timestamp;


a cryptographic hash;


a parent-version reference;


contributor identities;


and a status signature.



A hash does not prove that a claim is true.


It can help prove that a specific file existed in a specific form and has not been silently altered after the record was created.


The chain should therefore record:


\[

H(V_n)

\]


for each preserved version \(V_n\), where \(H\) is a cryptographic hash function.


The next version references the prior one:


\[

V_{n+1}

\rightarrow

H(V_n).

\]


This produces a verifiable sequence.


13. The Three Disclosure Layers


Not every reader needs access to every private draft.


The protocol therefore distinguishes three layers.


13.1 Public authorship statement


A concise statement included in the book, article, or publication page.


Example:


> This work originated with and was directed by John Swygert. AI was used for structured discussion, organization, research assistance, criticism, drafting support, and editorial refinement. The author selected, revised, approved, and accepts responsibility for the final work.




13.2 Verifiable project record


A more detailed record available to publishers, reviewers, institutions, collaborators, or interested readers.


It may include:


declaration versions;


outline history;


contributor roles;


version milestones;


source log summary;


and final attestation.



13.3 Private evidentiary archive


The complete confidential record.


It may include:


conversations;


voice files;


unpublished drafts;


notes;


correspondence;


contracts;


raw source materials;


rejected passages;


metadata;


and hashes.



The three-layer system protects both transparency and privacy.


14. The Final Authorship Attestation


Before publication, the named author should complete a final attestation.


A model statement is:


> Final Authorship Attestation

I have reviewed and approved this work in its final form. I understand its principal claims, arguments, and contents. I accept responsibility for its publication. To the best of my knowledge, the accompanying authorship and contribution record accurately describes the process through which the work was created.




The attestation may also identify:


known limitations;


unresolved factual questions;


rights status;


AI-generated components;


external contributor permissions;


and publisher disclosures.



The final attestation converts publication into an explicit act of responsibility.


15. Correction After Publication


Provenance should continue after release.


Corrections may be necessary because of:


factual error;


citation error;


omitted credit;


newly discovered evidence;


updated law;


revised data;


or process-disclosure correction.



A corrected edition should preserve:


original publication date;


correction date;


description of change;


responsible party;


new version identifier;


and relationship to the prior edition.



The chain should not pretend that the earlier version never existed.


Correction strengthens integrity when the correction itself is preserved.


16. Privacy and Proportionality


A provenance protocol should not become compulsory surveillance of thought.


Authors may need to protect:


confidential sources;


private medical information;


family communications;


trade secrets;


unpublished inventions;


security-sensitive material;


and intimate drafts.



The principle should be proportionality.


The record must preserve enough continuity to authenticate the route without forcing every private detail into public view.


Possible protections include:


sealed records;


redacted logs;


delayed release;


third-party escrow;


access permissions;


pseudonymous contributor IDs;


and selective verification.



Provenance should protect creation, not punish privacy.


17. Protocol Levels


The system may be implemented at three levels.


17.1 Minimum protocol


initial declaration;


originating note;


outline;


final manuscript;


public disclosure;


final attestation.



17.2 Standard protocol


declaration history;


outline versions;


source log;


major drafts;


contribution log;


public and verifiable records;


final attestation.



17.3 Enhanced protocol


complete version history;


cryptographic hashes;


timestamped conversation records;


contracts;


private archive;


third-party verification;


and persistent publication ledger.



The appropriate level depends upon:


commercial value;


institutional requirements;


controversy risk;


research significance;


number of contributors;


and the author’s preferences.



18. Application to Ghostwriting


A ghostwritten project should identify:


whose experiences and ideas form the work;


who conducted interviews;


who drafted prose;


who determined structure;


who revised;


who approved;


and what attribution agreement governs publication.



The public statement may remain brief if contract and convention permit.


The private record should be clear.


The honor of the arrangement does not require public performance of creative purity.


It requires that the involved parties tell the truth to one another and meet the disclosure obligations owed to publishers, readers, institutions, or law.


19. Application to AI-Assisted Writing


The Authors Guild has recommended that authors distinguish among kinds of AI use, fact-check outputs, comply with contractual obligations, and disclose substantial text generation. It also advises written agreements requiring editors, ghostwriters, and other contributors to reveal their own AI use. 


The Provenance Protocol extends that principle.


AI use should be described by function rather than by a binary yes-or-no label.


Possible functions include:


ideation;


interrogation;


outlining;


summarization;


source discovery;


comparative analysis;


draft generation;


rewriting;


style development;


translation;


formatting;


code generation;


image creation;


and quality control.



The record should also identify:


whether output entered the final work;


whether it was revised;


whether claims were verified;


whether the author understood it;


and who approved it.



20. Secretary Suite Implementation


Secretary Suite can implement the protocol as a persistent authorship layer.


Each project would contain:


Project identity


title;


author;


project ID;


purpose;


date opened;


status.



Authorship declaration


current version;


prior versions;


declared route;


contributors;


tools.



Origin record


first note;


recording;


transcript;


timestamp;


source identity.



Structural record


outline versions;


chapter map;


decision notes.



Source record


citations;


verification state;


claim mapping.



Contribution record


contributor;


role;


proposal;


author decision;


final status.



Version record


file;


parent version;


timestamp;


hash;


change summary.



Approval record


reviewer;


approval level;


comments;


final attestation.



Publication record


edition;


ISBN or DOI;


platform;


publication date;


correction history.



The system would preserve provenance when text is copied, exported, revised, or transferred between applications.


21. Provenance as Boundary


In TSTOEAO terms, provenance is a boundary that preserves identity through transformation.


The work changes:


\[

V_1

\rightarrow

V_2

\rightarrow

V_3.

\]


Without provenance, the later version may become detached from its prior states.


With provenance:


\[

V_3

\supset

\operatorname{history}(V_1,V_2).

\]


The record does not prevent change.


It ensures that change remains relationally accounted for.


This is dynamic equilibrium applied to authorship.


The project remains itself while evolving because the chain preserves continuity.


22. What the Protocol Does Not Prove


The protocol cannot prove that:


every idea was original;


every source was accurate;


every contributor was truthful;


the author fully understood everything;


the book is good;


or the claims are correct.



It can establish stronger evidence that:


the work developed through identifiable stages;


declared contributors participated in stated ways;


versions existed in a documented sequence;


the author made identifiable decisions;


and publication responsibility was accepted.



Provenance is not omniscience.


It is disciplined continuity.


23. The Ethical Principle


The protocol rests upon a simple distinction:


> Assistance is not deception. Concealment where truth is owed is deception.




An author should not be punished merely for using tools.


A reader should not be intentionally misled about material authorship where the representation matters.


A publisher should not have to rely exclusively upon intuition or unreliable AI detectors.


A genuine author should not lose a career because developmental evidence was never preserved.


The route should be available for examination at the level appropriate to the relationship.


Conclusion


Modern creation follows many routes.


Some authors work alone.


Some dictate.


Some collaborate.


Some hire ghostwriters.


Some use editors, researchers, translators, or artificial intelligence.


The future of authorship should not depend upon pretending that only one route is legitimate.


It should depend upon preserving truth across whichever route is chosen.


The Provenance Protocol begins before drafting with an Authorship Process Declaration.


It preserves:


\[

\text{origin}

\rightarrow

\text{outline}

\rightarrow

\text{research}

\rightarrow

\text{contribution}

\rightarrow

\text{draft}

\rightarrow

\text{revision}

\rightarrow

\text{approval}

\rightarrow

\text{publication}.

\]


It permits the process to change while requiring the declaration to change with it.


It distinguishes public transparency from private evidence.


It protects authors, collaborators, publishers, and readers.


Its governing principle is:


\[

\boxed{

\text{Declare the route. Preserve the route. Update the route.}

}

\]


\[

\boxed{

\text{Then accept responsibility for where the route leads.}

}

\]


References


Authors Guild. (2026). AI Best Practices for Authors. The Authors Guild. 


Loffhagen, E. (2026, July 31). $2m Crime Novel Deal Collapses Amid Questions Over AI Use. The Guardian. 


United States Copyright Office. (2025). Copyright and Artificial Intelligence, Part 2: Copyrightability. 


Swygert, J. (2026). The Tool Is Not the Lie: AI, Ghostwriters, Authorship, and the Ethics of Honest Creation. Ivory Tower Publishing.