# Bryant McGill Resume [bryantmcgill.com](https://bryantmcgill.com/) · [LinkedIn](https://www.linkedin.com/in/bryantmcgill/) · Austin/Dallas, Texas · Remote and global travel ### Founder / Global Influence Operations Systems Architect — Simple Reminders / McGill Media — circa 2009–present - Built and operated a software-assisted global influence architecture integrating authored language, content atomization, publishing automation, programmable distribution, visual communication, audience analytics, and cybernetic feedback; see [[projects/Simple Reminders - Global Influence Operations and Information Warfare|Global Influence Operations and Information Warfare]]. - Designed and continuously operated [[wiki/Atomic Markdown|Atomic Markdown]], a dual-render authoring grammar in which contextual prose and autonomous quotations are composed together, then validated and atomized into addressable publication objects; see [[projects/Dual-Render Authorship and the Atomic Markdown Double-Brace Grammar|Dual-Render Authorship: The Atomic Markdown Double-Brace Grammar]]. - Designed the semantic layer and transmission system that converted canonical source writing into structured linguistic objects, separately addressable quotations and passages, public pages, graphics, feeds, search surfaces, social publications, recurring distribution objects, books, and later publishing forms while preserving source identity and provenance. - Developed automated transformation and distribution infrastructure across websites, RSS, visual publishing, social platforms, books, and related channels; the evolving architecture later included [[projects/XDO - Executable Markdown and Portable Workflows|XDO]] and [[projects/AutoSites - Folder-Native Publishing and Distribution|AutoSites]]. - Operated the communication system as a cybernetic loop—compose, encode, transform, distribute, observe, interpret, adapt, and redistribute—using behavioral response as an instrument without treating engagement as truth. - Applied computational linguistics, natural-language processing, information retrieval, automation, message iteration, audience observation, and systems analysis to narrative propagation and population-scale response. - Extended the work into strategic communications, influence operations, narrative intelligence, cognitive security, adversarial narrative analysis, provenance, channel integrity, and information-warfare applications, with architectural continuity into contemporary AI-mediated communication systems without recasting the earlier deterministic systems as language models. - Built an organically developed network exceeding 12 million direct subscribers; preserved native Facebook analytics record [[about/statistics|50.1 billion impressions and 1.2 billion engagements]] across the represented network. - Produced individual publications at exceptional scale, including a May 2014 publication that reached 26,370,048 people and recorded 584,066 shares. - Converted network-scale influence into conventional publishing outcomes: *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 national Top 150 in 2015. **Selected contemporary records:** [[sources/bryant-mcgill__facebook__network-analytics__circa-2016__50-billion-impressions-1-billion-engagements.png|ᴘɴɢ]] · [[sources/bryant-mcgill__sprout-social__group-analytics__2014-2018__52-billion-impressions-233-million-link-clicks.png|ᴘɴɢ]] · [[sources/bryant-mcgill__facebook__viral-post-analytics__2014-05-25__26-million-reach-584-thousand-shares.png|ᴘɴɢ]] · [[sources/bryant-mcgill__wall-street-journal__bestseller-list__2015-05-28__simple-reminders-number-2-nonfiction-ebooks.png|ᴘɴɢ]] · [[sources/bryant-mcgill__usa-today__bestseller-list__2015-05-28__simple-reminders-number-46.png|ᴘɴɢ]] [[sources/bryant-mcgill__usa-today__bestseller-list__2015-05-28__simple-reminders-number-46.pdf|ᴘᴅꜰ]] ### President & Chief Research Scientist — Computational Scientific Laboratories — beginning in 2001 ![[resources/images/computational-scientific-laboratories-banner.png]] - Our goal was to apply data science practices to information, communications, automation, publishing, and data reusability / abstraction in SaaS systems. - Led an operational computational and scientific research organization financed through reusable software intellectual property, hosted application systems, commercial deployments, licensing, hosting, and vertical information systems. - Directed historically supported research and development in computational linguistics and natural-language processing, artificial intelligence adjacent NLP, learning-machine work, bioinformatics, search and information retrieval, advanced data modeling, compression, parallel computing, communications, networking, and complex simulations. - Directed the Web Application Server Platform (WASP) as the reusable application, commercialization, and delivery substrate for dynamic database-backed systems with shared runtime services, account context, configurable presentation, and reusable navigation. - Productized reusable software including `pro.pm`, `keydb.pm`, `ip2location.pm`, `fusionchart.pm`, Component-Based Theme Builder, and PageBuilder Pro with embedded-distribution, deployment, licensing, and source-retention models. - Developed and delivered systems spanning content management, customer service, intranets, inventory, e-commerce, project management, search and retrieval, and other business and institutional applications. - Led government, university, educational, nonprofit, automotive, and commercial deployments for organizations including Kootenai County, the City of Liberty Lake, Coeur d'Alene Airport, YMCA Spokane, Wendle Motors, and Gonzaga University. - Absorbed Webiness clients, personnel, software and intellectual property, hosting operations, and technical assets into CSL, moving customer sites to CSL head-end servers while expanding the operation beyond Web design and hosting. - Integrated multimillion dollar compute estate that included high-end RAID storage, Compaq rack systems, and components of parallel-compute infrastructure. **Selected contemporary records:** [[sources/spokane-journal-of-business-webiness-ceases-web-design-hosting-services-undated.png|ᴘɴɢ]] [[sources/spokane-journal-of-business-webiness-ceases-web-design-hosting-services-undated.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-02-csl-about-2001-12-09.png|ᴘɴɢ]] [[sources/webiness-csl-02-csl-about-2001-12-09.pdf|ᴘᴅꜰ]] · [[sources/csl-executive-staff-bryant-mcgill-2001-12-09.png|ᴘɴɢ]] [[sources/webiness-csl-03-csl-executive-staff-2001-12-09.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-04-csl-clients-2001-12-09.png|ᴘɴɢ]] [[sources/webiness-csl-04-csl-clients-2001-12-09.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-05-csl-products-2001-10-26.png|ᴘɴɢ]] [[sources/webiness-csl-05-csl-products-2001-10-26.pdf|ᴘᴅꜰ]] · [[sources/csl-wasp-homepage-corporate-overview-undated.png|ᴘɴɢ]] · [[sources/computational-scientific-laboratories-logo-source.png|ᴘɴɢ]] ### Chief Technology Officer; later Owner / Operator — Webiness — 2000–2001 - Served first as Chief Technology Officer after leaving Artesian Direct, overseeing Web development, hosting infrastructure, software systems, technical personnel, client services, budgets, profitability assessment, product planning, and delivery. - Directed operational Web systems for automotive inventory and financing, employment and applicant management, real-estate listing ingestion, utilities, commerce, education, and community organizations. - Built high-availability server-side and enterprise systems using Perl, mod_perl, Apache, Delphi/Pascal, JavaScript, PHP, and related Web technologies. - Subsequently took over Webiness as owner/operator and absorbed its customer relationships, infrastructure, personnel, hosting operation, and software base into Computational Scientific Laboratories. **Selected contemporary records:** [[sources/spokane-journal-of-business-webiness-ceases-web-design-hosting-services-undated.png|ᴘɴɢ]] [[sources/spokane-journal-of-business-webiness-ceases-web-design-hosting-services-undated.pdf|ᴘᴅꜰ]] · [[sources/spokane-journal-of-business-daines-buys-building-for-startups-undated.png|ᴘɴɢ]] [[sources/spokane-journal-of-business-daines-buys-building-for-startups-undated.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-07-webiness-company-2001-02-15.png|ᴘɴɢ]] [[sources/webiness-csl-07-webiness-company-2001-02-15.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-08-webiness-portfolio-2001-02-06.png|ᴘɴɢ]] [[sources/webiness-csl-08-webiness-portfolio-2001-02-06.pdf|ᴘᴅꜰ]] · [[sources/webiness-csl-01-webiness-homepage-2003-02-03.png|ᴘɴɢ]] [[sources/webiness-csl-01-webiness-homepage-2003-02-03.pdf|ᴘᴅꜰ]] · [[sources/webiness-website-navigation-splash-2000-10-18.png|ᴘɴɢ]] ### Chief Technology Officer — Artesian Direct — 2000 - Served as Chief Technology Officer during Artesian Direct's development as a broadband, Internet-appliance, multimedia, and technology-commercialization company. - Worked within a nine-member executive and board environment described in archived company materials as representing more than 150 years of cumulative technology-industry experience and $5.25 billion in combined technology sales. - Worked alongside industry figures including Bernard Daines, cofounder of Grand Junction Networks and founder of Packet Engines; Gerry Sumner of Delta Marketing; President and COO Cristopher G. Hollingsworth; and corporate/legal executive Robert Van Siclen. - Directed technology architecture, engineering evaluation, product-development planning, and technical strategy across broadband networking, distributed computing, Internet appliances, server-side systems, multimedia delivery, and emerging fiber-access applications. - Applied parallel-computing infrastructure to video-over-IP appliances and supporting systems associated with Grant County Public Utility District's Zipp fiber-optic network. - Developed printer drivers and head-end systems supporting automated supply replenishment and worked in the Liberty Lake technology environment surrounding World Wide Packets, Gigabit Ethernet, optical-access networking, set-top systems, and broadband application infrastructure. - Participated in technical-personnel management, engineering integration, budgets, profitability analysis, acquisition evaluation, and executive-level technology decisions before leaving within the first several months of 2000. **Selected contemporary records:** [[sources/artesian-direct-management-team-2001-02-14|ᴍᴅ]] ### Developer Support Engineer / Executive Technology Consultant — Borland / Inprise — April 1998 – 1999 - Served as President of the Delphi Developer's Guild and held a visible position within the Borland/Delphi developer ecosystem. - Entered through the formal Developer Support Engineer role and provided software-engineering assistance to Delphi developers solving programming problems, including difficult-issue investigation, failure reproduction, documentation interpretation, escalation, and repair. - Reviewed and appraised two proposed Delphi books for publication. - Met and consulted regularly with two sitting Borland chief executives and Vice President of Business Development **Jerome “Jay” R. Leite** on technical, business, and developer-community strategy, working to create a more developer-friendly company culture. “Executive Technology Consultant” describes this functional assignment rather than the original HR title. - Worked directly with developer-community leaders, engineers, technical authors, and senior Borland personnel while routine support obligations were substantially reduced during the executive-consulting assignment. - Continued developing VersePerfect and the larger [[projects/Ten Years Building a Symbolic Language Engine|Symbolic Language Engine]] as active computational-linguistics, natural-language-processing, symbolic-AI, corpus-engineering, and information-retrieval work. - Pursued technical interests in linguistics, artificial intelligence adjacent NLP, compression, neural networks and pattern recognition, self-improving code, learning machines, complex systems, cybernetics. ### Founder / Owner — McGill Engineering / Lionheart — approximately 1990–2001 - Owned and operated an engineering, software-development, and Internet-systems practice providing custom software, computer systems, networking, Internet infrastructure, consulting, training, hardware, connectivity, databases, and information systems. - Began with business-computing engagements: specified and assembled custom PCs, installed office networks, built shared multi-user databases for law firms and other companies using FoxPro and Claris FileMaker Pro, deployed shared ACT! systems, maintained systems under contract, and trained users. - Operated McGill Engineering and its Lionheart company structure from the Triad Center while performing the Intelenet and U.S. Senate-facing work as a major concurrent engagement. - Developed Internet and TCP/IP systems, Linux and Perl infrastructure, content-management and information-retrieval tools, software applications, and technical services that continued through Webiness and CSL. - Continued Linux, Perl, search, retrieval, and WebGlimpse experimentation with Trevor Gillette Smith in Spring City during 1996 after the Triad operation ended. - Intensively developed the language-processing architecture begun in 1994 into VersePerfect and the larger [[projects/Ten Years Building a Symbolic Language Engine|Symbolic Language Engine]], spanning computational linguistics, NLP, information retrieval, symbolic AI, knowledge representation, corpus engineering, and specialized retrieval. - Delivered executive Internet-adoption seminars and client consulting, including work with Covey Leadership Center and Franklin Quest while the organizations were coming together, helping the emerging group establish itself on the Web before the formal 1997 FranklinCovey merger. - Built reusable low-dependency software and portable server infrastructure that continued into later systems, including [[projects/Shazam - A Portable Perl Capability Library|Shazam]]. ### Technical Architect — Triad Center engagement; later Intelenet Inc. — approximately 1993–early June 1996 - Architected and integrated the [[projects/U.S. Senate Intelligence Global Media and Retrieval System|U.S. Senate Intelligence Global Media and Retrieval System]] within a Senate-facing institutional information environment. - Connected more than 200 international television channels and live broadcast/satellite feeds to closed-caption extraction, multilingual text processing, source/time association, continuous indexing, and rapid search and retrieval. - Used Perl on a custom Red Hat Linux build as the principal implementation and integration environment across heterogeneous text, file, database, broadcast, and retrieval systems. - Integrated a retrieval toolchain including dtSearch, Glimpse, Folio Views / Infobase, and Symantec Q&A. - Worked in a heterogeneous technical environment involving satellite feeds, telecommunications infrastructure, NeXT and Silicon Graphics systems, early Internet connectivity, search, compression, and experimental Linux deployments. - Built and presented early demonstrations while John “Fred” Adamson originated the Senate engagement and managed institutional relationships. - Performed the engagement while operating McGill Engineering/Lionheart from the same Triad Center environment. ### Data Processing Technician — U.S. Navy — beginning circa 1989 - Completed Data Processing Technician Class “A” School in San Diego in 1989. - Was formally assigned to **COMNAVLOGPAC** within the CINCPACFLT/HQ USCINCPAC command complex on Makalapa Hill, Hawaii. - Provided data-processing support in the top-secret **Worldwide Military Command and Control System (WWMCCS)** operating environment at the largest WWMCCS site in the Pacific. - Developed ancillary systems for the Department of Defense's WWMCCS environment. - Operated Honeywell H-6000/6000-series WWMCCS mainframe systems inside the high-security computer compartment and worked with cryptologists, tape-library systems, microfiche film, and input/output operations. - Assisted the J6 staff function at HQ USCINCPAC. - Processed secure information and physically delivered computer-produced information and command messages within the headquarters complex to CINCPACFLT and HQ USCINCPAC recipients. - Applied controlled-access, reliability, communications-discipline, and operational-continuity practices in a consequential institutional environment. - Operated a Hawaii bulletin-board network remembered as serving approximately 3,000 members. - Discharged under honorable conditions. ### Sales Associate — RadioShack / Tandy — approximately December 1985–November 1986 - Hired at sixteen after the store obtained a corporate exception to RadioShack's eighteen-year minimum-age policy; became the youngest person the company had hired. - Explained personal computers to customers and helped them select systems and components suited to what they wanted to build or learn. - Assisted electronics hobbyists in finding capacitors, breadboards, and other project components and explained their functions and use. - Translated customers' practical goals into understandable technical choices at the point of purchase. ## Education ### Data Processing Technician Class “A” School — Service School Command, Naval Training Center San Diego — 1989 In 1989, I completed the U.S. Navy’s Data Processing Technician Class “A” School at **Service School Command, Naval Training Center San Diego, California**. A 1990 Naval Postgraduate School report identifies Data Processor “A” School—DP-A—as one of seven initial technical schools operated by Service School Command in San Diego. The Navy also referred to the larger installation as Naval Training Center San Diego. [Naval Postgraduate School report](https://upload.wikimedia.org/wikipedia/commons/5/50/Attrition_reporting_in_Navy_technical_training_%28IA_attritionreporti00craw%29.pdf) The school prepared me to operate military automatic data-processing systems rather than merely use computers as an end user. I learned fundamental digital-computer architecture: processors, memory, peripheral equipment, storage devices, communications channels, and the movement of information through input, processing, storage, and output stages. The period Data Processing Technician curriculum covered number and coding systems, data preparation, computer software, operating systems, input/output control, magnetic-media libraries, computer-generated output, microcomputer concepts, and the practical operation of a computer installation. Earlier Navy manuals also included programming concepts and languages, electronic data processing, storage principles, and the control of EDP equipment. [1987 Navy manual catalog record](https://www.govinfo.gov/content/pkg/GOVPUB-GP3-fb245dcbe13ce5c72afa8514dcb916a6/pdf/GOVPUB-GP3-fb245dcbe13ce5c72afa8514dcb916a6.pdf) [Navy Data Processing Technician manual](https://files.eric.ed.gov/fulltext/ED096543.pdf) I learned that data processing was an operational chain in which accuracy at every stage mattered. Source information had to be received, validated, coded, entered, stored, updated, retrieved, and transformed into reports without losing its meaning or provenance. Operators had to understand job scheduling, queues, file organization, storage allocation, input/output devices, system messages, abnormal terminations, restart procedures, media handling, and production deadlines. Tape libraries, disk storage, printed output, microfiche, terminals, and other physical media were parts of the information system. A mislabeled tape, incorrect job-control instruction, damaged record, unauthorized copy, or misrouted report could compromise both the data and the mission. My later Hawaii assignment applied that foundation in the **World Wide Military Command and Control System**, normally abbreviated **WWMCCS**. WWMCCS was not merely a single computer program. It was a worldwide arrangement of personnel, computers, communications links, facilities, databases, procedures, and command centers supporting military planning and operational control. Its purpose included delivering warning and intelligence information, supporting the President and Secretary of Defense, assigning missions, directing unified and specified commands, and supporting the Joint Chiefs of Staff. Common formats, compatible equipment, reliable communications, timely retrieval, and continuity under crisis conditions were therefore essential. [GAO description of WWMCCS](https://www.gao.gov/products/lcd-80-22) The standard WWMCCS computers were the **Honeywell H-6000/6000-series mainframes**, descendants of the General Electric GE-635 architecture. They operated under Honeywell’s **General Comprehensive Operating Supervisor**, or GCOS, with specialized WWMCCS software and security modifications. GCOS managed system resources, files, job scheduling, security controls, program execution, and input/output flow. The original architecture was strongly oriented toward batch and sequential processing, requiring additional software and locally developed applications to meet the faster and more specialized information requirements of individual commands. That historical limitation helps explain the importance of the ancillary WWMCCS systems I helped develop. [GAO Honeywell and GCOS findings](https://www.gao.gov/assets/109172.pdf) Security was inseparable from computer operation. I learned the classification levels, the difference between clearance eligibility and an operational need to know, and the requirement to protect classified information throughout its lifecycle: creation, marking, access, processing, reproduction, transmission, storage, delivery, and destruction. Work areas were divided into controlled, limited, and exclusion areas according to sensitivity. Entry depended on authorization, identification, and mission need; uncleared visitors required escort and protection from exposure. Removable media, printouts, tapes, microfiche, messages, and working material required positive custody and accountability. Suspected loss, exposure, misrouting, or unauthorized access had to be reported as a potential security violation or compromise. These principles were embedded directly in Navy Data Processing Technician training and federal safeguarding rules. [Executive Order 12356](https://www.archives.gov/federal-register/codification/executive-order/12356.html) I also learned the principles associated with **TEMPEST**: protecting classified information from compromising electromagnetic or electrical emanations produced unintentionally by computers, terminals, printers, cables, and communications equipment. Protection included approved equipment, shielding, filtering, physical separation, controlled zones, proper wiring and grounding, and separation of unencrypted “RED” information paths from “BLACK” encrypted or unclassified paths. TEMPEST taught that information security extends beyond passwords and locked doors: data can escape through radiation, power lines, signal cables, or nearby conductors if equipment and facilities are not properly designed and controlled. [NSA history of TEMPEST](https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-spectrum/tempest.pdf) Together, the school and my WWMCCS assignment taught me to regard computing as a complete human, technical, physical, and security system—one in which data integrity, access control, reliable operation, physical custody, communications discipline, and timely delivery all carried operational consequences. ### Site-Specific WWMCCS Operations and Compartmented-Security Qualification — Makalapa, Pearl Harbor, Hawaii Following Data Processing Technician Class “A” School, I completed extensive site-specific indoctrination and practical qualification for duty in the classified command, communications, and computing environment at Makalapa. This training functioned as a second technical school: it prepared me to operate within a hardened, access-controlled facility supporting the Commander in Chief, U.S. Pacific Fleet and the Pacific theater’s World Wide Military Command and Control System. The wider architecture included separate WWMCCS nodes for Pacific Fleet, Pacific Command, and the PACOM Regional Automatic Data Processing Center on Oahu. [GAO WWMCCS architecture](https://www.gao.gov/assets/lcd-80-22.pdf) The qualification covered the physical organization of a secure computer installation: raised-floor mainframe spaces, controlled power and signal distribution, cipher-controlled compartments, successive access-control boundaries, positive identification, visitor escort, and strict prohibition of unauthorized electronic, photographic, recording, or information-bearing devices. I learned that clearance alone did not grant access; entry and exposure also depended upon current authorization, assigned duties, and need to know. Work occurred within controlled, limited, and exclusion areas whose protections increased with the sensitivity of the systems and information inside them. I received practical instruction in communications security, information security, computer security, and TEMPEST protection. Power feeds, communications lines, equipment, and information paths were identified and controlled according to their security status. Training emphasized RED/BLACK separation, approved equipment, shielding, filtering, grounding, physical separation, cable routing, and protection against unintended electromagnetic or conducted emanations. The underlying lesson was that classified data could escape through power systems, signal wiring, nearby conductors, terminals, printers, or peripheral equipment even when no document had been removed. [NSA history of TEMPEST and RED/BLACK separation](https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-histories/history_comsec.pdf) The operational qualification joined these security principles to Honeywell H-6000/6000-series WWMCCS mainframe work. I learned the local system configuration, GCOS operations, job flow, input/output control, magnetic-tape and microfiche handling, message production, system monitoring, abnormal-condition response, restart and continuity procedures, and the ancillary applications developed to meet Pacific command requirements. Accuracy, timeliness, accountability, and availability were operational requirements because the information supported fleet movements, command decisions, readiness reporting, and time-sensitive military action. I was trained in the positive custody and movement of classified command messages. This included verifying recipients and authorization, enclosing material in approved locked containers, maintaining continuous physical possession, passing through armed and interlocked access-control points, documenting transfers, and delivering time-sensitive fleet information directly to authorized command recipients. Within the hardened headquarters environment, armed Marine security personnel verified access before material could proceed to protected command spaces. Facility 250 was constructed with a reinforced, bombproof basement specifically intended to preserve command functions during attack. [Library of Congress facility history](https://tile.loc.gov/storage-services/master/pnp/habshaer/hi/hi0600/hi0649/data/hi0649data.pdf) Training also covered routine and emergency destruction. Classified messages, working material, magnetic media, cryptographic material, and sensitive system components had defined retention and destruction requirements. I learned destruction priorities, approved methods, accountability after destruction, and emergency procedures intended to prevent recovery or exploitation if a facility were threatened, penetrated, evacuated, or lost. Emergency-action tools and destruction capabilities were positioned near critical systems, and personnel were expected to understand their assignments before an emergency occurred. [Navy emergency-destruction guidance](https://www.secnav.navy.mil/dusnp/Security%20Documents/SECNAV%20M-5510.36%20-%20Chapter%204.pdf) The indoctrination extended beyond buildings and equipment into counterintelligence awareness. I was trained to recognize elicitation, unusual interest in my duties or access, attempts to cultivate personal relationships, requests for seemingly harmless fragments of information, unauthorized devices, suspicious contacts, and efforts to learn operational routines. I was expected to disclose nothing outside authorized channels and to report attempted exploitation or security anomalies. This taught me that people, conversation, habits, and social relationships were potential information channels just as surely as cables and computers. [National Counterintelligence and Security Center](https://www.dni.gov/files/NCSC/documents/SafeguardingScience/foreign-collection-methods.pdf) The result was a comprehensive understanding of command computing as a unified system of technology, people, physical architecture, armed protection, communications discipline, information custody, counterintelligence, continuity, and emergency denial. I performed this work inside a senior flag-level staff environment where secure data processing directly supported admirals, fleet commanders, and the Pacific command structure.