Methodology

This page explains how the work on commandanalysisgroup.com is produced. It is the framework's account of its own process: who authors it, how AI is used, how versions are tracked, how research is being built, and how readers can engage. Where claims appear elsewhere on the site about authorship, sources, and license, this page is the place they are documented in one register.

Authorship and AI assistance

Every framework artifact published here — the working papers, the in-development books, the framework page, the glossary — is authored by Brandon S. Goe. AI assistance is used throughout: for drafting candidate prose, for stress-testing arguments, for catching register and consistency drift, and for accelerating the mechanical parts of a writing cycle. The voice and the substantive judgments are the author's; the polish, the structural checking, and a meaningful share of the drafting iteration involve large language models working under direction.

This is disclosed plainly rather than implicitly. A framework that argues for honest institutional behavior cannot hide its own production process. The disclosure also appears in the site footer and in each working paper's front matter.

At the final-product stage, external-bound writing is revised to remove the visible tells of generated prose — em-dash overuse, characteristic cadences, throat-clearing, bolded lead-ins, generic padding. A reader cannot tell, from style alone, what was drafted by hand and what was drafted with assistance, because both have been edited to the same register. That register is the author's.

Versioning, license, and what "current" means

The three working papers are deposited at Zenodo under CC-BY 4.0. Each paper carries a version number and a deposit date in its front matter. When a paper is revised, a new version is deposited and receives its own DOI; the previous DOI continues to resolve to the earlier version so that anyone who cited it can still reach what they cited.

The site itself is rebuilt on every meaningful change. Build dates appear on the updates log. The framework page (/framework) always reflects the current articulation; previous articulations are not preserved on the site (they are preserved in the working-paper version history).

The framework distinguishes between an update (an addition or refinement) and an erratum (a correction to something that was wrong). The updates log carries the first kind; the errata page carries the second. The distinction matters because a reader who trusted a previous claim deserves to know whether it has been retracted or merely improved.

Research process — Capability Floor and Honest Authority

The framework's substantive claims are subject to a Capability Floor: a stated bar of evidence that a claim must clear before it is asserted as established. When a claim has not yet cleared its floor, it is published as a working hypothesis or as a forecast rather than as a finding. The peer-reviewed empirical work that tests the framework is reserved for the dissertation; the working papers state the framework as theory, with its testable predictions named explicitly so a future reader can hold the work accountable to the predictions it made.

The same principle governs the books in development. The diagnostic books — the ones that name structural failure modes that are already publicly documented elsewhere — are published as soon as they are ready. The normative and the speculative books wait until the diagnostic foundation has cleared its bar.

This is the practical meaning of "Honest Authority" on this site: the framework does not claim more than its evidence supports, and the gap between claim and evidence is itself a published item rather than a private one.

Reader engagement

The contact page is the canonical way in. Substantive critique of a specific paper section, axiom, or failure mode is welcome and is the most actionable kind of feedback. Reports of errors that name a specific page and explain what is wrong will route to the errata page if they hold up under review.

The updates log doubles as a public change log; an RSS feed is available at /rss.xml for readers who want notifications without a mailing-list subscription.

Source canon

The public-facing artifacts of the framework, in order of formal weight:

• The three working papers (/papers) — the formal statement of the framework, with permanent DOIs at Zenodo. These are the canonical cite-able artifacts.
• The framework page (/framework) — the plain-English articulation of what the working papers specify formally. Useful for readers who want the substance without the formal apparatus.
• The glossary (/glossary) — definitional terms used across the framework, with cross-references to the papers in which each term is introduced and to the page sections in which each is discussed.
• The books in development (/books) — the narrative and operational treatments. These are works in progress; the working papers are what should be cited until the books are published.

Anything beyond those four surfaces is either work in progress or not yet a public artifact of the framework.