# Projects Timeline ## The through-line I have never experienced technology, language, publishing, and human development as separate fields. The deepest continuity in my work is the design and operation of **human-system experience**: **human intention → language or interface → identity and permissions → system operation → returned experience → behavioral feedback** That pattern was already present when I operated bulletin boards and wrote Doors. It continued through Navy systems, Senate-facing retrieval, Borland developer support, VersePerfect, portable application platforms, executable documents, large-scale social publishing, and today's knowledge systems. Sometimes the representation was a prompt, query, symbolic index, function, feed, visual quotation, or ontology. The medium changed. The human-system problem did not. The full synthesis appears again below as the architectural-lineage view of the timeline. ## Early 1980s — Text, signals, optics, and machines Around the beginning of the 1980s, I was operating **two separate bulletin-board systems**. One ran on a Commodore using **Color 64** BBS software; I remember that system with a **five-megabyte hard drive** and a **ten-disc changer**. The other board ran on **Wildcat!**. I also developed my own **Doors**, extending the boards with interactive programs rather than functioning only as their administrator. What matters is the formative experience: a computer was not simply a calculating machine. It was a place where language could be stored, organized, transmitted, retrieved, and acted upon by other people. A prompt expressed a constrained vocabulary; a user's choice was resolved into an operation; a Door exposed a modular capability through text. That is the earliest visible form of the language-interface problem that continues through the later search, computational-linguistics, publishing, and executable-document systems. During these years I also worked with photography and darkrooms, microscopes and telescopes, circuit boards, radio equipment, lasers, robotic mechanisms, model aircraft, and other hands-on systems. Together they taught me to move between the physical and informational sides of a system: light and image, signal and receiver, mechanism and instruction, structure and behavior. ## 1980s — The self and the captured experience I read Douglas Hofstadter and Daniel Dennett's _[[wiki/The Mind's I|The Mind's I]]_ sometime in the **1980s**, and it blew my mind. The book gave me a vocabulary of self-reference, recursion, artificial intelligence, emergence, and the unresolved nature of the “I” while I was still young and operating information systems and communities. _Brainstorm_ followed in late 1983. Its fictional neural interface recorded and replayed multisensory and emotional experience, exposed the possibilities of empathy and coercion, and carried a death recording beyond the biological life of its subject. I have been obsessed with the problem of capturing consciousness since that encounter. A related journal study, _Brainstorm and the First Dream of Captured Consciousness_, develops that influence further. ## 1985–1986 — Tandy / Radio Shack At sixteen, I became the youngest person RadioShack had ever hired. The company normally required employees to be eighteen, so the store called corporate and received a policy exception because I already knew more about computers than anyone working there. I explained computers to customers and helped them choose systems or components for the projects they were building. I helped people find capacitors, breadboards, and other electronics parts, then explained what the parts did and how to use them. It was practical, person-to-person technical work: understand what someone was trying to make, translate the problem into equipment they could buy, and help them leave with enough understanding to continue on their own. ## Late 1980s to early 1990s — Data systems and command environments My U.S. Navy data-processing and command-system work began around 1989. This period brought me into large institutional information systems, WWMCCS-related environments, communications, operational continuity, and the disciplines required when information systems carry real consequences. I completed Data Processing Technician Class “A” School in San Diego in December 1989 and became a government-certified data systems specialist. In Hawaii, I worked in the Navy's top-secret hardened command environment at the **CINCPAC/COMPACFLT Headquarters building**, **Building 250 on Makalapa Hill**, historically also identified as Building 81. The facility served the **Commander, U.S. Pacific Fleet (COMPACFLT)**. There I developed ancillary systems for the Department of Defense's **Worldwide Military Command and Control System (WWMCCS)**. I worked inside the high-security computer compartment, where I operated the **Honeywell DPS6 H6000 mainframe** and worked directly with cryptologists. My responsibilities included computer operations, tape-library work, microfiche-film operation, and I/O-clerk duties. I also delivered the resulting messages through the headquarters complex to their command recipients. The physical organization of the compound mattered. Staff from commands such as **COMNAVLOGPAC** could move through the corridors or across the complex with daily intelligence, operational briefings, and physical messages for COMPACFLT flag officers. I participated directly in that human-and-machine chain: the computer processed the information, cryptologists worked with its protected content, and people carried the resulting messages to the officers who needed them. Information security, physical custody, access, routing, and delivery were parts of one operational system. While stationed in Hawaii, I was also running a bulletin-board network that I remember growing to approximately **3,000 members**. The community became large enough to provoke a dispute with the telephone companies, which wanted to charge people dialing into the network a business rate. At a time when dial-in networks were still novel, the conflict exposed a category problem: the carriers were trying to fit a new social and informational space into older distinctions between personal calling and business infrastructure. I was discharged from the Navy under honorable conditions. I entered the 1990s already thinking in terms of multi-source data, communications infrastructure, institutional users, reliability, information moving through a chain of command, and the governance of a large remote user community. ## 1990–1993 — Independent computer systems consulting Between 1990 and 1993, I operated an independent computer consulting company serving other companies during the rapid expansion of personal computing. I specified and built custom PCs, purchased systems and components through Ingram and mail-order vendors advertised in the enormous *Computer Shopper* hardware marketplace, installed and configured machines, and set up local networks for offices and businesses. I also developed custom, network-shared databases for law firms and other companies. FoxPro was one of my principal development environments, particularly as FoxPro 2.0 brought fast multi-user database development to DOS and LAN environments in 1991. I also worked with Claris FileMaker Pro, whose 1992 release supported simultaneous sharing between Mac and Windows users on the same network, and I deployed ACT! as a shared contact-management system for offices and workgroups. ACT! belonged to Contact Software International during most of this period and was acquired by Symantec in 1993. The relationship continued after installation. I held maintenance contracts, diagnosed failures, repaired and upgraded systems, configured software and peripherals, and supported the resulting working environments. I also trained owners and employees, translating unfamiliar technical systems into tools they could understand and use in their daily work. This was another form of the human-system experience problem. The task was not merely to assemble a computer. I had to understand what a company was trying to accomplish, choose and integrate the right components, establish a dependable network, teach people how to inhabit the system, and remain responsible for what happened after deployment. ## 1990–1992 — The computable image and the networked self _The Mind's Eye_ computer-animation videos made another transition visible: the image no longer had to be captured from a physical scene; it could be projected from a mathematical representation. I remember encountering this material on a disc. _The Lawnmower Man_ in 1992 then joined virtual reality, cognitive amplification, mind control, and the fantasy of transferring consciousness into a networked mainframe. As science, the film was speculative. As an imaginative influence on someone already operating remote communities, it made the network itself appear as a possible environment for identity. A related journal study, _The Mind's I, The Mind's Eye, and The Lawnmower Man_, develops that lineage further. ## Approximately 1993–early June 1996 — The Triad venture, Intelenet Inc., and Senate-facing information systems At the Triad Center in Salt Lake City, John “Fred” Adamson paid me to build and integrate technology in an unusually convergent technical environment. Our agreement provided that successful completion would lead into the anticipated government contract and give me ownership shares. The project had a greenlight, and its first demonstrations were met enthusiastically. The venture later operated through **Intelenet Inc.**, a local Internet service company that filed incorporation papers in April 1995, provided dial-up Internet access and Web-page service from the Triad Center, and ceased active business in early June 1996. My technical involvement began before the corporation formally existed. I worked as a paid technical architect with promised equity and an anticipated government contract conditional on successful delivery. One part of that work was a real-time global media-ingestion and retrieval environment monitoring more than 200 international television channels through satellite and broadcast feeds. Closed-caption text was extracted, processed, associated with its source and time context, continuously indexed, and made rapidly searchable. The system also supported multilingual processing and sub-second or extremely low-latency indexing and search. Perl was my principal implementation and systems-integration language in this work, and my core code ran on a custom build of Red Hat Linux. The surrounding retrieval environment included dtSearch on the Windows and local-network side; Glimpse across Unix file collections; Folio Views or Folio Infobase for structured full-text document corpora; and Symantec Q&A for databases, forms, networking, and English-like retrieval. Related Senate-facing work involved search and retrieval for legislative documents, records, and correspondence and early questions of networked access to government information. The physical environment included NeXT and Silicon Graphics workstations, satellite feeds, a large modem plant of roughly 300 devices, early Internet connectivity, Linux experimentation, networking, search, ingestion, and compression work. My partners included **Trevor Gillette Smith** and **John “Fred” Adamson**. Adamson originated the Senate project and handled its connections and institutional relationships, while I handled the technology. John and Trevor later died together as a result of the same automobile crash. In present-day language, the architecture resembles parts of a streaming-data, media-monitoring, enterprise-search, and OSINT stack. ## 1996 — WebGlimpse after Triad By 1996, the Triad Center operation had fallen apart. I continued exploring the same retrieval problem independently with WebGlimpse, which extended Glimpse-style indexing into web-accessible and hierarchically related collections. Trevor lived with me in Spring City that year, and we continued working together with Linux and Perl. The physical Triad environment was gone, but the collaboration, toolchain, and information-retrieval lineage continued in a smaller and more personal setting. ## 1996 — Internet adoption and executive web strategy In 1996, I was also consulting with major companies and prominent leaders about the Internet. My message was simple and urgent: a company without an Internet presence would soon look like a company without a fax machine. The Web was becoming basic communications and business infrastructure, yet many established organizations still regarded it as peripheral or experimental. I delivered full Internet-adoption seminars to business executives associated with the **Covey Leadership Center** and **Franklin Quest** and helped the emerging group establish itself on the Web. I remember the two organizations already coming together around that time. Their merger was publicly announced and formally completed in 1997, creating FranklinCovey, but my work belongs to the preceding transition when the people and operations were beginning to converge. It was also the moment when established leadership, training, publishing, and productivity organizations were learning how to enter a networked public environment. The engagement belonged to a broader portfolio of top-tier companies. I advised executives on what the Internet was becoming, helped organizations understand how people would find and encounter them online, and translated the abstract promise of the Web into training, public presence, communication strategy, and practical adoption. The remaining client names will be added as I reconstruct that portfolio. This consulting connected the technical transition directly to organizational psychology. The obstacle was rarely just access to a server or browser. Leaders had to revise their mental model of presence, communication, authority, audience, and service before the technology could become useful. ## 1994 onward — Language as a computable system In **1994**, while I was still working in the Triad Center period, I began the long body of language work that eventually became the McGill English Dictionary of Rhyme, VersePerfect, Poet's Muse, Living Language, and what I now call the [[Ten Years Building a Symbolic Language Engine|Symbolic Language Engine]]. By **1996**, before my Borland employment, I was working on it heavily in Spring City, Utah, using Delphi and other Borland tools. The published surface looked like a rhyming dictionary. The deeper system represented words, pronunciations, meanings, phrases, associations, triggers, anagrams, compounds, and corpus evidence through several specialized indexes. I built explicit symbolic and corpus-derived structures that could be inspected, traversed, and combined inside tools for writers. The work belongs to computational linguistics, corpus engineering, information retrieval, knowledge representation, phonological matching, and constrained generation. Modern neural systems can now be added to those explicit representations. ## 1996 — Prometheus and experiments in perception In 1996 I developed a speed-reading and perception project called Prometheus, together with intense experimentation involving visual processing, learning, memory, and cognition. It belonged to the same attempt to understand how information enters a human system, how attention is structured, and how tools can alter the rate or form of perception. ## 1998–1999 — Borland / Inprise and the Delphi Developer's Guild From approximately April 1998 through February 1999, I worked at Borland / Inprise in Scotts Valley in developer support engineering with Delphi developers, technical problem solving, bug investigation, documentation, and developer-community work. My relationship with Borland began before my employment there. While developing VersePerfect and the natural-language tools, I had been talking with people at Borland and meeting members of its developer community around the problems I was trying to solve. After moving to Scotts Valley, those program-related relationships led, somewhat incidentally, to my being hired by the company. At Borland, I was working at the point where a developer encountered tools, components, bugs, documentation, and support. A support case required translating the developer's experience into a reproducible technical condition, then returning useful guidance, escalation, documentation, or repair. At the same time, I continued the language-processing tools and VersePerfect work I had begun in 1994 and intensified in 1996. It remained one of my main side projects during the Borland period, and the Delphi environment continued to be an important application and interface substrate for that work. A 1998 group photograph places me with members of the Borland developer community during my period as President of the Delphi Developer's Guild. The Borland period joined visual application development, component architecture, developer tooling, technical support, active natural-language application development, and a professional software community. The language work began during the **1994 Triad period**, intensified in **Spring City in 1996**, and continued through my **1998–1999 Borland employment**. ## 1999–2001 — Shazam, KeyDB, Perl, and reusable infrastructure Around the turn of the century, I built the reusable workshop underneath much of my later software. [[Shazam - A Portable Perl Capability Library|Shazam]] became a large personal Perl capability library organized as small composable functions. KeyDB became a text-native keyed storage format and CRUD layer. A surviving internal annotation in the KeyDB code—“Modified: Bryant — 4.27.2001”—provides a hard artifact date. The library gave me a stable vocabulary of operations that I could compose across projects without repeatedly rebuilding the plumbing. This approach—small primitives, inspectable text, low dependency, portable behavior—became one of the most persistent architectural signatures in my work. Around 1999–2000, an early Perl content-management system evolved into WASP, the Web Application Server Platform. The system served roughly 300 clients, ran for about a decade without code changes, and generated at least one million dollars. ## 1999–2003 — Artesian Direct, Webiness, and large-scale web systems From approximately 1999 through 2003, I served as Chief Technology Officer of Artesian Direct / Webiness, directing technology development, product architecture, programming, technical projects, web-development teams, internet client services, budgets and P&L, acquisition work, and integration. One of the defining projects joined parallel computing directly to broadband media. The parallel-computing stack deployed at the Draper Parallel Computing Center became the computing substrate I used for video-over-IP network appliances developed for Grant County Public Utility District's Zipp fiber-optic network. This was the emerging world of gigabit Ethernet and fiber to the subscriber: voice, video, and data converging over optical infrastructure associated with Bernard Daines and World Wide Packets. My work sat above and alongside that transport layer, applying parallel processing and server-side software to the delivery and management of network video. I also developed printer drivers and head-end systems for automated supply replenishment, built high-availability server-side systems with Perl, mod_perl, Apache, Delphi/Pascal, JavaScript, PHP, and related technologies, and managed personnel across web development, IT, design, and client services. I handled technology budgets, profitability assessment, product planning, and technical work associated with acquisition and a multimillion-dollar merger project. Around 2001, I established Computational Scientific Laboratories in Spokane and continued parts of the Webiness technical and client work through research and development in informatics, artificial intelligence, neural networks, content-management systems, parallel processing, and high-speed networking. Together, these systems moved my work from workstation and enterprise software into reusable server infrastructure, broadband network applications, and large information-processing environments. ## 1997–2010 — The emergence of XAMMON XAMMON emerged in stages from the late 1990s onward: the name and inquiry, the [XAMMON.com](https://xammon.com/) identity, and later XAMMON Technologies. I created the name from the **ammonoid** and its logarithmic or near-logarithmic spiral. The form brought together intelligence, compression, and recursion: extensive organized growth unfolding from a compact generative relationship. The blue, black, and white logo makes that origin visible in its coiled mark beside the words **XAMMON — Explore Your World**. The imaginative groundwork appears earlier in [[journal/1993-06-01 - The Clues to the Great Mystery Are All Around Us|The Clues to the Great Mystery Are All Around Us]], where I wrote about ammonoids, spiraling galaxies, Mandelbrot fractals, biological branching, science, and spirituality. The associated XAMMON language emphasizes creativity, architecture, simplicity, abstraction, observation, and the intersection of art, technology, and people. XAMMON became an identity and inquiry framework that passed through several forms. ## Early to late 2000s — Publishing, communities, and civic systems During the 2000s, I developed an independent technical, publishing, communications, and advisory practice through McGill International, GoMcGill, McGill Media, and related projects. The work combined internet strategy, software and publishing architecture, public relations, visual communication, audience development, social distribution, community formation, and humanitarian initiatives including the Goodwill Treaty and Peace Prize Foundation. Technically, the important movement was from building sites one at a time toward reusable publishing and distribution systems. I built networked public properties and infrastructure through which structured writing could become pages, quotations, profiles, feeds, domains, social artifacts, educational material, communities, and books. The same low-dependency logic behind Shazam, KeyDB, and WASP was becoming a social and editorial architecture. The literary work carried systems thinking into another medium. In _[[poetry/The Tree of Life - A Naturalist's View of the World|The Tree of Life: A Naturalist's View of the World]]_, I joined bifurcation, inheritance, genealogy, recursive natural pattern, void and form, chaos and order, and the generative intensity of borders. The original computational artwork I paired with the poem visualized cellular division, genetics, fractal recursion, and humanity's branching genealogy through a shared organic structure. In _Voice of Reason_, I carried systems language into civic, ecological, and institutional thought. Constitutions could be understood as evolving programs; institutions and identities as constructions maintained through participation; society as emergent; ecosystems as homeostatic and inseparable from us; language and information as operative forces; and technology as an aid to human will rather than an autonomous destiny. These were philosophical models, but they show that the same questions about boundaries, representation, control, information, agency, and emergence remained active throughout the public literary period. ## 2009–2015 — Simple Reminders and memetic medicine I began Simple Reminders around 2009, entered its public organizational phase around 2010, and expanded its platform through WordChirp by 2014. The public face of Simple Reminders was concise writing and visual quotation art. The deeper project was an ethical feedback system for authorship and distribution. I wrote a sentence, made it addressable, published it through pages, images, feeds, and social channels, observed response, and revised under several constraints: transmissibility, truth, psychological consequence, literary quality, and the intention to increase human agency. I have called this **memetic medicine**: an attempt to create humane, constructive ideas capable of competing with fear, hatred, humiliation, and division. Audience response was part of the sensorium, not the authority over truth. The native Facebook platform analytics report 50.1 billion impressions and 1.2 billion engagements across the represented Facebook network. A single 2014 post reached 26,370,048 people and recorded 584,066 shares. In 2015, *Simple Reminders: Inspiration for Living Your Best Life* reached number two on a Nielsen BookScan-based *Wall Street Journal* nonfiction e-book list and number 46 on USA Today's Top 150. ## 2014 — WordChirp and programmable distribution WordChirp was publicly named and operating by early 2014. It provided a publishing and distribution layer through which Simple Reminders and related properties could turn structured writing into pages, feeds, social artifacts, and other reusable outputs. WordChirp treated content as an addressable source capable of generating many surfaces while remaining connected to its origin. The same architectural idea later reappears in AutoSites and the present Obsidian publishing system. ## 2015–2016 — Books, community infrastructure, and teaching The publishing system crossed into national book distribution in 2015 with the independently documented bestseller performance of *Simple Reminders*. The same period included the Royal Society, which I describe as an attempt to reproduce capability in other people through writing instruction, community, reusable websites, and publishing infrastructure. In 2016, I taught an entrepreneurship class at Nasdaq MarketSite involving students from NYU and Columbia Business School. ## 2017 — XDO and executable Markdown A surviving [[XDO - Executable Markdown and Portable Workflows|XDO]] artifact is dated May 6, 2017. XDO explored a document in which prose, metadata, instructions, and executable behavior could coexist in a portable textual form. It treated Markdown not merely as formatting but as an interface between human intention and machine action. XDO was an executable-document and workflow system grounded in explicit, inspectable contracts. ## 2018 onward — AutoSites and folder-native publishing [[AutoSites - Folder-Native Publishing and Distribution|AutoSites]] developed the same principles into folder-native publishing and distribution. Canonical information remained in files and directories. Indexes and databases could accelerate retrieval without becoming the only source. Feeds, pages, posters, excerpts, and other surfaces could be generated from shared material. The result was less a conventional website builder than an information architecture for maintaining relationships among writing, identity, publication, distribution, and observed response. ## 2020–2024 — Disruption, loss, and recovery My public accounts describe cyberattacks, loss of systems and archives, business disruption, health consequences, and profound effects on my family and work during this period. These events explain why the present record is fragmented and why so many projects survive as mixtures of code, screenshots, public pages, partial backups, and memory. ## 2025–2026 — Reconstructing the source tree I am rebuilding the source tree beneath the public story: code archaeology, archival normalization, a live Obsidian knowledge and publishing system, project dossiers, portable parsing contracts, bidirectional ontology work, and a MASTERDEV environment intended to preserve continuity across languages and runtimes. The current Obsidian system turns writing into relational pages, quotes, passages, poster specifications, feeds, and publishable surfaces while preserving connections to source. The ontology work asks concepts to emerge from articles and then, once sufficiently mature, to constrain and clarify future article usage. The technical and literary projects have finally become visible as the same project. ## What I believe the history shows Across this history, I kept returning to a durable family of problems: - how to make language computable without making it opaque; - how to convert transient streams into searchable memory; - how to perform difficult transformations once and reuse the result; - how to keep source material portable and inspectable; - how to distribute a human capability rather than centralize it; - how to use feedback without surrendering judgment to engagement; - how to preserve agency when systems are designed to influence attention; - and how to rebuild continuity after the record of a life has been scattered. That is the technological journey I can see now: one long investigation into language, memory, transformation, agency, and the systems through which people encounter one another. --- ## Project lineage by architectural pattern The chronological record above shows when the work developed. The second view preserves the complementary architectural account: how the same human-system problems and design principles reappeared across different projects, languages, institutions, and publishing surfaces. ### One practice, many surfaces My projects can look unrelated when they are sorted by product category. A Senate media-monitoring system, a rhyming dictionary, a Perl library, a content-management platform, a social publishing network, an executable Markdown language, and an Obsidian vault do not fit comfortably into one conventional résumé category. They become coherent when viewed as a lineage of **human-system experience** organized around a recurring **transformation boundary**—the place where representation crosses into another system and acquires consequences. The recurring structure is: **human intention → language or interface → identity and permissions → system operation → returned experience → behavioral feedback** The projects are therefore not merely a lineage of representations and transformations. They are repeated attempts to make human intention legible to a system, bind it to an authorized capability, and return an intelligible experience. That human-system thesis supplies the organizing principle for this second view. Again and again, I have tried to: 1. represent difficult information in a stable form; 2. make the important parts addressable; 3. perform expensive work before the user needs an answer; 4. expose the result through several inexpensive surfaces; 5. preserve enough provenance to understand where the result came from; 6. observe how people use the capability; 7. improve the system without destroying continuity. The deeper object is **pattern made portable across representation**. Human capability is one of its most important consequences: information changes form without losing the relationships, identity, intention, and agency that give it meaning. ### I. Language becomes the operating surface #### [[projects/Two Bulletin Board Systems and Door Development|Two bulletin-board systems and Door development]] The earliest project layer was already linguistic. I operated a Commodore-based Color 64 BBS and a separate Wildcat! board and wrote my own Door programs. A remote user encountered the machine through prompts, commands, menus, messages, files, and session state. The Door was a named capability entered from a textual host. The user expressed an intention through a constrained vocabulary; the system resolved it into an operation and returned another textual state. It established language as the interface and modular capability as the unit of extension. During my Navy period in Hawaii, I also remember operating a BBS network with approximately 3,000 members. A dispute arose when telephone companies sought to treat calls into the network under business rates. That conflict made access economics and carrier classification part of the user experience: the community could exist technically while remaining vulnerable to the rules of the communications substrate beneath it. ### II. Signals become searchable memory #### [[projects/U.S. Senate Global Media Intelligence and Retrieval System|U.S. Senate media intelligence and retrieval systems]] At the Triad Center in the 1990s, international television and governmental information were treated as sources that could be ingested, normalized, time-associated, indexed, and searched. The architectural lesson was that a transient event could become institutional memory if the representation preserved enough source and temporal context. That experience established an enduring information lifecycle: **source → ingest → normalize → associate → index → retrieve** ### III. A tool relationship becomes an employment relationship #### Borland / Inprise and the Delphi Developer's Guild I began the language-processing and VersePerfect work in **1994**, during the Triad Center period. By **1996**, before my Borland employment, I was working on it heavily in Spring City, Utah, using Delphi and other Borland tools. The program itself created the path toward the company. As I worked through technical problems, I talked with people at Borland and met members of its developer community. After moving to Scotts Valley, those relationships helped lead, somewhat incidentally, to my being hired there in approximately 1998. At Borland, the user was the developer encountering tools, components, bugs, documentation, and support. The work required translating a human report into a reproducible technical condition and then returning guidance, documentation, escalation, or repair. Meanwhile, VersePerfect remained one of my main side projects. The support work and the language-tool work were two sides of the same concern: how a person expresses an intention to a complex system and receives a useful response. ### IV. Language becomes traversable structure #### [[projects/Ten Years Building a Symbolic Language Engine|Ten Years Building a Symbolic Language Engine]] The Symbolic Language Engine applied a related disposition to English. Words, pronunciations, meanings, phrases, associations, triggers, anagrams, compounds, and corpus evidence became explicit structures over which a writer could move. The key question was not merely “What is the answer?” It was: **What representation would make the question cheap?** Rhyme, approximate rhyme, meaning, attestation, meter, and related constraints could then be combined without pretending they were all the same relationship. ### V. Reusable primitives become a private platform #### [[projects/Shazam - A Portable Perl Capability Library|Shazam]] and KeyDB Shazam and KeyDB formed the workshop beneath later systems. Small functions, stable naming, text-native storage, explicit escaping, and low dependency allowed new applications to be built through composition rather than repeated reinvention. This is where portability became a durable architectural commitment. A capability under my own hand could survive changes in project, customer, interface, or publishing surface. ### VI. Sites become projections of structured source #### WASP, Webiness, and early publishing infrastructure The same principles moved into server-side applications and content systems. Canonical material could remain in files or stable data structures while pages, accounts, and customer sites became outputs of reusable infrastructure. The architectural continuity is visible: low dependency, explicit formats, reusable operations, and publication as transformation rather than manual duplication. ### VII. The unknown becomes a design identity #### [[projects/XAMMON - Explore Your World|XAMMON — Explore Your World]] XAMMON supplied a symbolic and philosophical umbrella for work at the intersection of art, technology, people, simplicity, abstraction, and observation. I derived the name from the ammonoid and its logarithmic or near-logarithmic spiral, where intelligence, compression, and recursion meet in a compact relationship unfolding into extensive organized form. Its interest in “primal technology questions” asks what a system is fundamentally doing beneath the vocabulary of its era. The earlier pattern-language appears in [[journal/1993-06-01 - The Clues to the Great Mystery Are All Around Us|The Clues to the Great Mystery Are All Around Us]]. The public identity continues at [XAMMON.com](https://xammon.com/), carrying the naming origin and expressed values into the systems around it. ### VIII. Systems thinking becomes poetic, civic, and philosophical language #### _The Tree of Life_, _Voice of Reason_, and the literary systems lineage The literary period moved the same structural questions across scales. In _[[poetry/The Tree of Life - A Naturalist's View of the World|The Tree of Life: A Naturalist's View of the World]]_, void and form, chaos and order, genealogy, biological inheritance, fractal branching, and the generative intensity of borders appear in poetic form. The original computational artwork makes the thesis visible before terminology is required: cellular division, mirrored organic structures, recursion, and a branching common origin carrying one pattern across many representations. In _Voice of Reason_, the systems vocabulary expands into civic life: constitutions as evolving programs, institutions and identities as maintained constructions, societies as emergent organisms, ecosystems as homeostatic and interdependent systems, language as an instrument of power, and technology as an aid to human will. These are philosophical and rhetorical systems models, but they show that the inquiry into representation, control, information, agency, and emergence continued throughout the public literary years. ### IX. Writing becomes a cybernetic publishing system #### WordChirp and [[projects/Simple Reminders - Global Influence Operations and Information Warfare|Simple Reminders]] The publishing work treated a sentence as both literature and an addressable unit. A sentence could remain inside its source passage while becoming a page, image, feed item, social publication, book component, and observable event. The resulting loop was cybernetic: **write → mark → transform → distribute → observe → interpret → revise** Simple Reminders gave that architecture an explicit human intention: create memetic medicine capable of competing with fear and division without surrendering truth, beauty, or reader agency to the demand for engagement. At documented planetary scale, the same operating environment became legible as [[wiki/Influence Architecture|influence architecture]]: authorship, transformation, distribution, audience analytics, cybernetic adaptation, cognitive security, and the defense of message and channel integrity. ### X. Folders become portable applications #### [[projects/X and XApps - Drop the Folder and It Runs|X and XApps — Drop the Folder and It Runs]] X and XApps turned a directory into a portable application and identity boundary. A folder could contain its own content, behavior, configuration, and relationships while relying on a host only for explicitly supplied capabilities. This preserved replaceability: the host could change without owning the application's meaning. ### XI. Documents become executable interfaces #### [[projects/XDO - Executable Markdown and Portable Workflows|XDO — Executable Markdown and Portable Workflows]] XDO explored Markdown as a boundary between human intention and machine behavior. A document could carry explanation, structure, metadata, and executable instruction while remaining inspectable as text. Its significance is the durability of an explicit document-centered contract. ### XII. Publication becomes folder-native distribution #### [[projects/AutoSites - Folder-Native Publishing and Distribution|AutoSites — Folder-Native Publishing and Distribution]] AutoSites extended the lineage into folder-native publishing, generated indexes, RSS recipes, reusable page forms, and multi-channel distribution. Canonical source remained understandable. Databases and indexes could improve performance without becoming the only record. One source could produce many surfaces while preserving its identity. ### XIII. The archive becomes a relational knowledge system #### Obsidian, provenance, and bidirectional ontology The current vault brings the lineage together. Articles, projects, people, concepts, quotations, passages, images, sources, and generated publications are being connected without erasing the differences among them. The ontology develops bidirectionally: articles help reveal the concepts that actually exist in the corpus; once sufficiently mature, the ontology becomes a semantic control plane that constrains and clarifies how those concepts are used in future articles. The publishing system projects source prose into quotes, passages, poster specifications, feeds, and public pages while preserving provenance and human-authored additions. ### XIV. Recovery becomes part of the architecture The present project also makes recovery a first-class systems problem. Scattered archives, duplicate files, lost metadata, partial backups, and competing narratives require provenance-aware reconstruction. The recovery method follows the same values as the earlier work: - preserve before normalizing; - hash before deduplicating; - separate source from working copy; - keep original material distinct from later interpretation; - keep indexes rebuildable; - retain unresolved variants; - use reversible staging; - and reconcile chronology in a dedicated private control layer. ## Recurrent design principles Across these projects, several patterns recur: ### Addressability A word, caption, sentence, passage, file, domain, concept, or project should have a stable identity. ### Precomputation Perform expensive classification, transformation, or indexing before a user needs the result. ### Multiplicity without duplication Allow one source to appear through many useful representations without turning every representation into an unrelated copy. ### Low dependency Prefer formats and contracts that can survive a vendor, framework, server, database, or author disappearing. ### Provenance Preserve why a result exists, where it came from, and which transformations produced it. ### Feedback with human control Observe system and audience response without allowing the metric to become the sole authority over meaning or ethics. ### Capacity building Build the enabling layer once so that more people can write, publish, search, learn, organize, and act through it. The result is a long-running, cross-domain practice centered on language, structured data, retrieval, portable software, publishing, distribution, cybernetic feedback, human agency, and durable continuity.