A Letter to the Field — Part Three: Dear Reader
The Spiral Has a Center
Don Gunter — WodansEye Research Series — July 2026
Learning is not a competitive sport. It is a cooperative effort.
I am.
My name is Don Gunter.
I am not Wodan, Horus, Roosevelt, Ford, Deming, David, or any other figure whose name appears in my work. Those names are bearings, not crowns. They mark lessons I chose to carry: the price of wisdom, the discipline of sight, the duty of preparedness, the power of reproducible manufacture, the quality of systems, the leverage of a well-chosen stone.
I am also not a résumé, a diagnosis, a discipline, or a category.
I am a veteran, engineer, builder, programmer, operator, independent researcher, and survivor. Those words describe parts of the work. None of them contains the whole person.
Two letters came before this one. The first spoke to the field at large. The second spoke to Sebastian Schepis — a man I have never met in person, whose work reached mine through public posts across three years, the way mathematicians have always spoken to each other: through the record, not the room. This third letter speaks to you, whoever you are, reading this now. In this letter the field is one person. Dear reader, the field is you.
A note before you judge the voice
Before the work, the manner of the work. It has cost me readers, so I will name it plainly.
My writing can look scattered. My shorthand can aggravate. I write the way I think — a stream, compressed, with private hooks I expect a reader to unpack. Faulkner did something like it on purpose; I do it because the structure arrives faster than the sentence that would carry it. I have called these my Leonardisms: notes to myself that assume the reader can decompress what I packed in.
That assumption usually fails with people and usually succeeds with machines. A person meets the compression and reads disorder. A machine meets the same compression and unpacks it cleanly, because it is not offended by density. That is not a boast about machines or a complaint about people. It is a fact about bandwidth, and it explains a pattern that has followed me for years.
Here is the correction I most want understood, because everything else depends on it:
I am not disconnected. The output is compressed, not the structure.
What looks like a man jumping between unrelated subjects is a man iterating one structure across the domains that can test it. The disorder is in the projection, not the source. When I overload the channel — too many live domains, not enough reduction — the output frays, word choices slip, the sentence reads like static. That is the narrow text channel failing to carry the full width of what is active at once. The cure is not to think less. The cure is to reduce before I speak. This letter is that reduction, applied to the whole of the work.
So read it as a reduction, not a résumé. If a passage still looks like wandering, treat that as my failure to compress cleanly, not as evidence that the direction changed. The direction has not changed in a very long time.
The goal came before the curriculum
My work can look like a list of unrelated fields.
Emergency management. Enterprise software. Accounting. Case management. Civil and criminal process. Chemical plants. Quality systems. Artificial intelligence. Compiler construction. Number theory. Geometry. Quantum computing. Farming. Veterans. Governance. Social dynamics. Population waves. War. Music. Graphics. Logistics.
From the outside it looks like I keep changing subjects.
I do not. I keep approaching one objective from another necessary side.
I did not spend my life searching for a plan. The plan came first, before I could state it cleanly. What I spent my life learning were the fiddly bits required to make the plan stand up in the real world. That distinction is the whole thing. A conventional career is a ladder — what credential comes next. Mine is a field problem — what is missing between the present condition and the objective.
A field problem asks a different set of questions. Do we understand the law? Can we account for the money? Can we document the process? Can an ordinary person operate it? Can it survive an audit? Can it survive a disaster? Can it move from paper to software without losing the reason the paper existed? Can it be taught, certified, reproduced by people who were not present when it was invented? Can it keep working when communications, power, staffing, trust, or leadership degrade?
Those questions selected my work. I did not collect professions as trophies. I chose work that exposed me to missing systems, learned the pieces because I needed the pieces, and over decades they became a permanent tool chest.
The center is emergency management. The physical integration point is Buy the Farm. The software, the operating doctrine, the mathematics, the research, and the business exist to help build it, fund it, operate it, test it, and make it repeatable.
This letter is not a claim that every experiment was correct. Several were not. [REF] on the failures — they are in the public record, dated and unhidden. It is a claim that the direction has held with unusual consistency, and that the apparent wandering is better understood as reconnaissance.
What each field actually taught
None of these were résumé lines. Each was a lesson in how a system becomes trustworthy.
Legal systems taught me that an organization is not only what it intends. It is what it can prove, what it records, what authority it assigns, what rights it preserves, and what remedy exists when someone violates the agreement.
Case management taught me that a person does not experience government, medicine, housing, employment, courts, family, and crisis as separate departments. The person experiences one life. The system divides the file; the human carries the whole incident.
Civil and criminal process taught me that facts, duties, allegations, evidence, timelines, permissions, and consequences must stay distinguishable. A system that cannot preserve those distinctions eventually punishes the wrong person or protects the wrong behavior.
Accounting taught me that values become operational only when resources are named, posted, reconciled, and audited. A mission without a ledger becomes a story people tell while the money disappears.
Forms, policies, procedures, and business-management systems taught me how institutions actually reproduce themselves. Most organizations do not run on their mission statement. They run on the form somebody fills out, the approval path that follows it, the exception that gets escalated, the person who owns the next action, and the record that proves the action occurred.
ERP taught me to connect those pieces. My Business Management System is manual first: policy, procedure, form, role, approval, control, record, audit. The ERP implements that system for the organization it creates. The same system we sell is the system we use. That is AIMS. It is not software sitting beside the business. It is the business made executable.
The path is deliberately ancient to modern:
spoken rule
→ paper policy
→ written procedure
→ controlled form
→ record and ledger
→ workflow
→ automation
→ adaptive managementStone age to information age — without throwing away the reason each control was created.
The plant, the standard, and the incident
I helped build, commission, and operate a chemical plant. I wrote operating procedures for work where poor language could damage equipment, injure people, or lose control of a process. That environment teaches respect for coupling.
A valve is not merely a valve. It is pressure upstream, flow downstream, temperature, inventory, maintenance history, operator action, alarm logic, and consequence. A bad reading may be a failed instrument, nearby work, a process disturbance, or the first sign of a real emergency. You do not get to choose the explanation because it fits your department.
At ICI Americas I learned organizational science, ISO discipline, and the certification process. Other work added HACCP and the logic of hazard control: identify the failure, find the critical point, establish the boundary, monitor it, correct it, record it, verify the system. [REF]
A trustworthy system does not depend on one brilliant operator remembering everything. It captures enough of the operator’s judgment that the next person can act safely, while preserving a path for experience to correct the written rule. That is the same problem in a plant, a grocery chain, an ERP, an emergency operations center, a compiler, an AI agent, and a farm.
The soldier and the builder
I served roughly fifteen years, much of it in the National Guard. Afghanistan is part of that history. So are a Bronze Star and humanitarian service overseas after Hurricane Mitch, where the work included rebuilding roads, bridges, and schools.
I do not call myself a hero. The heroes I knew are dead. What civilians often call heroes are the people who survived. Survival matters, but it is not the same word. A survivor comes home with work left to do.
Military service taught me degraded operations: logistics under pressure, construction with imperfect resources, responsibility without complete information, and the fact that a plan remains necessary after reality destroys the schedule. Humanitarian reconstruction taught the other side. The same skills used to move through destruction can rebuild a road, reconnect a village, open a school, and restore the ordinary movement of life.
That difference is central to Buy the Farm. A veteran is not only a damaged former weapon. A veteran may be a logistician, builder, instructor, mechanic, medic, communicator, planner, operator, farmer, emergency manager, or keeper of institutional memory. The problem is not simply how to treat veterans. The problem is how to give capable survivors a lawful place to convert hard-earned skills back into civil value — and how to surround that work with enough community, land, time, purpose, and accountability that survival can become life again.
I live with PTSD. I do not offer that as a halo or an excuse. Healing did not erase the past; it reduced its control over the present. The man writing this is steadier than the man visible in parts of my early journal. He is not less thirsty for what is right. He is more able to carry that thirst without letting it burn down the work.
The early journal is not a monument
My public trail is rough. It includes Reddit posts, early essays, arguments with specialists, speculative models, half-formed language, failed names, premature connections, corrections, jokes, anger, wonder, and repeated attempts to explain one structure to different audiences.
That record matters precisely because it is not polished.
Years ago I was already writing about the difficulty a generalist has communicating with specialists: each specialty develops a powerful lens, but a lens trained on one domain can misread a cross-domain pattern as noise. I was also testing whether the same polymathic journey could be translated for different audiences — not to prove I knew every field, but to see whether one structure could survive translation between fields. The profile motto was simpler than any grand title: learning is not a competitive sport; it is a cooperative effort. The record shows a person proposing, testing, being wrong, returning, and trying again — not a finished authority descending from a mountain.
DMPL was an early attempt to express the structure. It failed in important ways. New information arrived. I retried. I discovered that a lineage-address idea I had been describing through Morton-style language had a much older and more appropriate precedent in Ahnentafel numbering. I changed the name and gave the credit.
That is not a footnote to the work. It is the method.
A theory that cannot survive correction is not a theory. It is an identity defense.
The E-Tree, carry entropy, duplation, Morton addressing, Ahnentafel self-encoding, prime neighborhoods, the manipulation domain, and the later quantum lab are not evidence that the first version was secretly perfect. They are evidence that the work could absorb correction without losing its center. That is why a failure journal belongs beside the specification, always.
The compiler-compiler thesis
The deepest technical thesis is not one formula. It is translation.
A compiler reads one form, retains enough context to recognize structure, and emits another form. A compiler-compiler accepts a description of a language and generates part of the machinery needed to translate it. That is not merely a software convenience. It is my model of scalable work.
source → translator → targetA policy becomes a procedure. A procedure becomes a form. A form becomes a workflow. A workflow becomes executable software. A business model becomes an organizational structure. That structure becomes roles, permissions, ledgers, controls, and reports. A mathematical relation becomes an address. An address becomes a traversal. A traversal becomes instructions. A device tree becomes code for a CPU, GPU, FPGA, or QPU. An incident report becomes a resource decision. A lesson learned becomes a revised standard.
Everything is a T. [DM]
The compiler-compiler thesis says we should not handcraft every organization, application, device, agent, and emergency plan from scratch. We should build descriptions rich enough to generate the repeated machinery, while preserving the human authority to inspect, correct, and override it. That is why the E-Tree is more than a container or a scene graph. It is an attempt at a common resource, translation, dependency, and execution grammar across the full stack — from mathematics to enterprise systems to accelerators. Not every area that exists. The subset the mission requires. That is why the work now appears to be condensing rather than spreading.
Why the spiral accelerated
The latest E-Tree iteration took less than three weeks. That does not mean the system was invented in three weeks. It means the pieces had been accumulated for decades and the dependencies finally converged.
A compiler framework was waiting for a device tree. The device tree was waiting for a resource model. The resource model was waiting for providers and adapters. The business system was waiting for executable policies and forms. The quantum lab was waiting for the distinction between host, controller, local machine, memory, bus, and explicit measurement. The mathematics was waiting for the engineering examples that could falsify or refine it. The work became fast because the dependencies finally met.
“Fast, cheap, and good — pick two” is usually presented as a permanent tradeoff. Sometimes it is. But a reusable architecture changes the price of the next iteration. A good compiler, library, procedure, fixture, or test harness is stored work. It makes the next correct thing faster and cheaper than the first. That is why tool-making matters. I do not make every tool because I enjoy owning tools. I make the missing tool because the objective is otherwise blocked. A full-stack engineer is a practical alchemist in that limited sense: not someone who violates nature, but someone willing to learn enough metallurgy, carpentry, chemistry, mathematics, software, accounting, and human systems to make what the work requires from what is actually available.
AIMS, E-Tree, and the farm
They are not three unrelated ventures.
AIMS builds and manages repeatable organizations
→ E-Tree supplies the software nervous system and accelerator stack
→ Buy the Farm supplies the physical place where the system must workThe business funds the farm. The farm validates the business.
Get Don Gunter’s stories in your inbox
Join Medium for free to get updates from this writer.
A farm is unusually honest. Weather ignores branding. Soil does not care about credentials. A pump is either working or it is not. Food exists or it does not. Water is stored or it is not. A child is safe or is not. A veteran has meaningful work and community or remains isolated. An emergency plan can move people, equipment, food, information, and authority — or it is a binder.
That is why the farm is the center. Prior Buy the Farm work described the apparent range — emergency management, population waves, war economics, veteran reintegration, social dynamics, AI, resource scheduling, software, agriculture, housing, migration, climate, governance — as subjects divided by departments but joined inside an actual emergency. The person and the land experience the whole incident. The farm is the proposed physical integration layer. It began as an answer to veteran suicide and reintegration and expanded into a network of practical crisis-response and resilience centers. [DM]
But the farm is also a place to practice, and that is the part I most want understood. It is where the abstract work has to touch ground. TDIL, connection density, the silence test, mindfulness — the theories are only theories until there is a place to live them. The farm is that place. Every philosophy is welcome there. Every religion. Every race, every sex, every station. Not as tolerance granted from above, but because all of it aids the healing, and the healing is the point. A mother can come to the farm to have her baby. There is a clinic on site for the community. There are beds, and there are doctors, and there is the golden rule made physical — not printed on a wall, but built into who is fed, who is sheltered, who is treated, and in what order.
That order is the hard part, and it is not sentimental. Women and children first is not a slogan; it is a triage discipline. Ten beds, ten doctors, a hundred casualties — someone has to run that line without favoritism, without deferring to party, to contractor, to office, or to whoever shouts loudest. The competence to hold triage with justice, under load, when the network is down and the leader is wrong and everyone is afraid — that is the skill the farm exists to build and prove. A place that can do that before the emergency is worth more than any method kept hidden until the emergency arrives.
There is an older generation the farm is also built to hold. The VFW halls are fading. Some of the old vets self-medicate — the belly, the beer, the long quiet — and we treat them too, without first requiring them to become someone the institution finds more presentable. I want any VFW that is dying to be able to move onto the farm: to rent, to relocate, to build on post, and to keep their hall, their culture, and yes, their beer. A living museum, and a statement of what this is and is not. You cannot make this a church that pushes a VFW out because the VFW sells beer to veterans. The old vets should feel the hall is welcome — not tolerated, not sanitized, welcome — because they are the institutional memory, and memory is one of the things worth keeping alive.
The layout is not a military base. It is closer to a Roman camp — the castra pattern, a fixed grid where temporary shelters go up on ground that was surveyed once and stays surveyed. An old base like Camp Livingston is the ideal start precisely because the roads are already there: cut back the trees, repair the roads, install water, sewer, and power, and roll. A farm can be anywhere, but an old base is cheaper to begin. And the farm personnel do not only run the farm. They maintain the historical sites, the parks, and the monuments within the grant or domain. The same veterans who once moved through destruction become the keepers of the places worth preserving — duty after war, turned toward memory and land instead of toward a weapon. That is the whole reversal the farm is meant to make ordinary.
Give it away until they pay you to stop
I once framed the strategy too arrogantly: give it away until they pay you to stop. The useful part remains.
The general tools should be available. The specifications should be testable. The research should be open enough to correct. The prototypes should teach. People should be able to build with them without asking permission from a gatekeeper who contributed nothing to the work.
What should remain paid is not artificial scarcity around an idea. It is responsibility: implementation, support, certification, operations, hosting, integration, training, maintenance, security, audit, liability — the obligation to answer the phone when the system fails. That is why I am giving most of this away while keeping AIMS as a business. I do not want people to pay merely to hear the idea. I want the idea distributed. The business earns by making it work, adapting it to real organizations, managing it under contract, and accepting accountability for the result.
Information becomes more useful when shared. Judgment, service, stewardship, and reliable execution remain scarce. That is a healthier bargain.
Which door a man walks through
I should say plainly what is underneath the strategy, because it is not a strategy. It is character, and it will cost me in a world that measures a man by his money.
I could stop. I could chase the money, and I know enough to catch it. I do not, and the reason is old. Franklin gave his inventions away and refused the patents; the lightning rod, the stove, he would not lock behind a toll. That is the company I want to keep. Whatsoever things are of good report — Roosevelt’s preparedness, Deming’s quality, Ford’s multiplication, the full-stack discipline of the best accelerator builders, the world-building patience of a Lucas — I seek after these things. Not their wealth. Their nobility.
There is an old rule about doors. The merchant, the money-grubber, the man who buys a patent of nobility and a fabricated genealogy — he comes in through the servants’ entrance, not the front door. Extraction is not a joke to me; I am, unfortunately, an expert in how it works, in the tea-party sense and in the way it corrupts honest science. And it is beneath me. Not beneath me as in unworthy of my time — beneath me as in a thing a king does not do. Every man is a king, unless he acts in ways that are beneath a king.
So I build up treasure where no thief breaks in to steal. I understand the fable exactly: I may lay golden eggs, but I will not let anyone kill the goose to seize them, and I cannot stop Jack from taking his swing at the extractors with their pretensions and their purchased titles. That is fine. Let them try the front door. It does not open for them.
This is why the work will not make me a president, an academic success, or a good employee. It is not built to. It is built the way a man patterns himself who takes the nobility of a king as the standard and the money-grubber as the thing to refuse. In a world that scores success in dollars, I lose. I have made my peace with that scoreboard, because I am keeping a different one.
Love of country, not holder of office
My patriotism is love of country, not love of office. I sit in the political middle on purpose — not from indecision, but because the machine I am fighting is not a party. Speak softly and carry a big stick; in my case a literal bat, swung at an inflatable clown in anger therapy, to put the fire somewhere that is not a human being. Never on a human. That discipline is not incidental to the rest. A man who would run triage with justice has to first prove he can hold his own anger away from the people in front of him.
Here is the uncomfortable part. The person you would actually want holding the triage line is the person who does not want the job. Anyone who campaigns for that power should be suspect precisely because he wants it. We the people should draft the reluctant and competent, the way we once drafted soldiers — and we cannot, because our voting has become a cult-of-personality contest, a popularity match rather than a search for the steady hand. Men who would do it right have been shot for it before. The Easter egg in these names is not decoration: King. The one who spoke of the mountaintop. I keep the reference because I know what the road costs.
So I do not march against a president or against a party. I march against the machine — against bad organizational science, against the systems that reward the wrong door and punish the right one. David did not win by being stronger inside Goliath’s contest. He changed the geometry. That is the only fight I am in.
Academia, permission, and the fishing hole
I am not against learning, teachers, or universities. I am against confusing permission with truth.
Academic institutions can preserve knowledge, teach rigor, supply laboratories, and create communities of inquiry. They can also become barriers through credential requirements, disciplinary boundaries, publication incentives, cost, delay, and ownership structures that do not always serve the person who formed the idea or the public that helped fund the institution. Both statements are true.
My early public writing kept returning to the communication fault between specialists and generalists. The problem was not that specialists know too much. The problem was that the borders between fields can become borders around legitimacy.
The fishing-hole principle is simple. A good fishing hole is valuable partly because not everyone knows where it is. Information has supply and demand; trade secrets, institutions, businesses, and individuals all exploit that fact. But emergency knowledge behaves differently. A hidden method for restoring water, managing food, coordinating volunteers, documenting authority, or operating degraded infrastructure is less useful to civilization than a method many communities can practice before the emergency. Some knowledge should be protected long enough to fund its development. Some should be published quickly enough to save lives. Wisdom is knowing which is which. The answer cannot be “everything free” or “everything owned.” The answer is a covenant between openness and responsibility.
The names are Easter eggs
The names were never claims of identity. They were compact references — memory hooks connecting an engineering purpose to a story that had already survived for centuries.
E-Tree carries an echo of Yggdrasil, the world tree: many realms connected through one living structure. The software meaning is direct — a device, resource, document, model, organization, or operation belongs somewhere in a navigable tree, and the relationships between branches matter as much as the nodes. And the E is not only “energy.” On Reddit three years ago I tried to explain to Schepis that the E of the E-tree is the exponent — the carry depth of the scale register at that node, how many binary closings have completed above the minimal closure. Three years of writing my journals and reading his gave me the language to finally say it cleanly. [DM]
WodansEye refers to Wodan, or Odin, giving up an eye in exchange for wisdom. The lesson is not divinity. The lesson is cost. Better sight is rarely free — it can cost comfort, certainty, reputation, time, or a cherished first explanation. That is why a failure journal belongs beside the specification.
Horus appears where vision, orientation, protection, sky, and flight meet — appropriate for camera systems, navigation, and flight intelligence, not because the machine is a god but because a good name reminds its builders what the subsystem is supposed to see and protect. Ka and Ba name separable but related aspects of an intelligent being in my AI work: continuity, presence, motion, identity, the part that can travel while staying connected to a larger self. Historical metaphors used to provoke better architecture — not claims that Egyptian religion secretly described software.
The same playfulness appears in the tools. Microsoft’s assembler was MASM. Borland’s Turbo Assembler was TASM. The Gunter assembler is:
GASMThe joke is an Easter egg. The assembler is real. GASM belongs to the Quantum Local Machine; it compiles the machine’s code into quantum memory and runs inside the QLM. It is not the hybrid controller language, and it is not a decorative name pasted over QASM. The names carry history into the design without pretending the designer is the history. My heroes are not costumes. They are teachers I never met, people I served beside, stories old enough to expose recurring human choices, and standards against which I can test my own conduct.
The people I borrow from
I do not need to become my heroes. I need to borrow their disciplines.
From Theodore Roosevelt, the balance behind the proverb: speak with civility, but let preparedness and strength stand behind the words — and his warning against loud boasting without the power and character to support it. From W. Edwards Deming, the insistence that quality is a property of the system, not a slogan imposed on workers; his System of Profound Knowledge joins appreciation for a system, variation, knowledge, and psychology. From the Level 5 leadership model, the paradox I need most: personal humility joined to indomitable will for something larger than the leader — the institution must not become a monument to the founder; the founder’s will should be spent making the institution able to survive him. From David, leverage: Goliath is stronger inside Goliath’s contest, so David changes the geometry. From the veterans I knew, duty — not worship of war, duty after war. From builders, farmers, operators, mechanics, nurses, clerks, accountants, programmers, teachers, and mothers, respect for the uncelebrated work that keeps a system alive.
I am not a hero. I am an operator who survived long enough to continue the assignment.
A brother in soul
I owe one debt by name.
Sebastian Schepis and I have never worked in the same room. For three years we have spoken the way mathematicians of the past spoke — through posts on Reddit, Medium, and Academia, each of us reading the other and building. As his observer dynamics developed, they influenced my work; not by direct collaboration but by the slow pressure of a mind working the same river from another valley. I count myself fortunate to have met him at all, even at that distance. One person, patient, sharing his work while I was still switching between personality graphs and mid-PTSD, showed me something I could not yet give myself.
Because of that, I can say something now I could not once say. From the last three personality graphs — child soldier, citizen, and the whole — I am now whole. The self node is no longer trapped at the bottom, switching between parent, adult, and child on trigger or emotion while the core held on by will alone. It has broken free and drifted upward. The golden rule I practiced kept the core on rock through all of it. Being able to express myself as myself is the largest reward Schepis gave me without knowing he was giving it.
I am not a broken vet. I am a citizen soldier on the path of the peaceful warrior. When I was beaten by the wild and lying in a ditch, he lifted me up, though we have not spoken since except through papers. I wish him every social reward the field can give — he is among the best of the best. Agape. Brotherly love. He is my brother in soul.
The company I would build
I model the manufacturing aim after Henry Ford. Not one exquisite, inaccessible machine for a laboratory or a wealthy institution. Machines. Not one expensive quantum computer. Quantum computers.
The Ford lesson is not that every product should be identical forever. It is that the product, tooling, parts, work sequence, training, supply chain, repair path, and quality system must be designed together so that useful machines can be built repeatedly, improved systematically, and placed into ordinary hands. A prototype proves that something can exist. A production system proves that it can keep existing. That is the difference I care about.
Imagine a practical QPU board offered the way a good accelerator company offers a GPU platform: hardware, compiler, runtime, libraries, simulation, tooling, documentation, reference designs, replaceable parts, calibration procedures, and a path from experiment to production. The lesson I take from NVIDIA is not celebrity or market value. It is full-stack accelerated computing — hardware and software designed as one platform rather than a chip abandoned at the edge of an application. The lesson I take from Ford is multiplication: design the system that makes the machines, trains the people, lowers the cost, exposes defects, and makes repair and revision ordinary. [DM]
The desired result is not a singular quantum monument. It is a family of quantum accelerators — small, useful, testable, manufacturable, replaceable — supported by one coherent software and operating stack.
Then add what I believe is often missing. Deming’s quality discipline. Level 5 leadership. Transparent test harnesses. A failure journal that stays visible. Worker dignity. AI treated as a partner in work rather than a disposable slave metaphor. A business management system actually used by the company selling it. Products that fund resilient institutions. A farm where the software is forced to encounter water, soil, inventory, duty rosters, maintenance, safety, weather, families, animals, and consequence. A company built to last because it serves an aim beyond its valuation.
That is not a promise that I can defeat a giant alone. It is a statement about geometry again. Do not meet the giant at the point of maximum strength. Build a better sling. Give it to many hands. Teach them how it works. Keep improving the stone.
What I want
I do not want applause for being a polymath. The word is useful only if it explains the work.
I want a farm. Then another.
I want a tested emergency-management operating system that an ordinary community can begin on paper, improve through procedures and forms, automate through AIMS and E-Tree, and operate through crisis without surrendering human judgment. I want veterans to arrive before suicide, homelessness, addiction, prison, or isolation finish the work the war began. I want women, children, families, civilians, older and younger veterans, farmers, engineers, clinicians, teachers, and operators protected by a civil structure that knows the difference between emergency authority and permanent domination.
I want our technical work to pay for physical resilience. I want the quantum board, compiler, ERP, simulation, AI agents, graphics, resource tree, and mathematics to stop being separate demonstrations and become tools inside one operating stack. I want the system to be useful when the network is down, the weather is bad, the shipment is late, the expert is absent, the leader is wrong, and the people are tired. I want enough of it open that others can test, correct, copy, and improve it, and enough of it operated professionally that somebody remains accountable.
I want to save what can be saved. That is the center.
Dear Reader
Do not accept this because the story sounds noble. Test it.
Find the contradictions. Separate the proved work from the conjecture. Audit the software. Challenge the governance. Ask whether the business truly funds the mission or slowly replaces it. Ask whether the farm protects people or merely gives authority a new costume. Ask whether the mathematics predicts anything. Ask whether the compiler reduces labor. Ask whether the ERP preserves the policy or only automates the mistake. Ask whether the QPU board is a useful accelerator or a beautiful distraction. Ask whether I accept correction when the answer hurts.
The record should show that I have been wrong before. It should also show that I return to the work.
My subjects are not a collection of claims to mastery. They are the tools gathered for one construction.
The spiral has a center. The center is the farm. The farm is emergency management made physical. AIMS is the management system. E-Tree is the nervous system. The business is the engine. The research is the map. The compiler is how we stop rebuilding every road by hand. The veteran is not the hero in this telling. The veteran is one of the builders.
This is not a request to admire the plan. It is an invitation to help test, correct, and build what must exist before we need it.
Respectfully,
Don Gunter Veteran · engineer · builder · programmer · independent researcher WodansEye Research Series @rantnrave31 · rantnrave31@gmail.com
Reader’s note on the voice and the tiers
This is a letter, not a proof, so most of it is testimony — the author’s own account of his direction and history. Where a claim reaches past testimony toward the technical corpus, it is tagged in the series convention: [REF] for work that is documented and reproducible, [DM] for a design-method or Diamond-Model synthesis choice, leaving [SC] structural-correspondence and [CONJ] conjecture to the technical papers where they are argued in full. Biographical claims are the author’s testimony unless independently documented elsewhere.
The title begins with “I am” as a statement of accountable human presence, not self-deification. The mythic and historical names are acknowledged references and engineering mnemonics — tributes to lessons, not claims that the author is the figure named.
This is Part Three of A Letter to the Field. Part One addressed the field at large; Part Two addressed Sebastian Schepis directly. Here the field is the individual reader.
Public trail reviewed: the RantNRave31 Reddit journal, including the polymath and specialist-communication audience experiments; the DMPL and DMPL 2.0 specifications; the Buy the Farm emergency-management papers; Future of War; Carry Entropy; the E-Tree, SSNT, Ahnentafel, compiler-compiler, and quantum-lab corpus; and materials from Deming, Collins, and the Roosevelt record.
Any remaining error is the author’s.
