Updates

Direct-store repricing across all formats

New list prices are in effect at the direct store, every format of all three volumes:

• The Code in the Conduit: paperback $12.99, digital bundle (PDF + EPUB + AI-narrated M4B) $9.99, print + digital bundle $19.99.
• The Machine That Sees Itself: paperback $14.99, digital bundle (PDF + EPUB + AI-narrated M4B) $9.99, print + digital bundle $19.99.
• The Practitioner’s Handbook: paperback $19.99, digital (PDF) $12.99, print + digital bundle $24.99.
• Complete sets: 3-book paperback set $39.99; 3-book PDF set $14.99.

Buy links are on the Books page.

Three volumes release August 1: the coordinated inaugural launch

The inaugural volume of each publishing stream releases on August 1, 2026 — all three at once:

• The Code in the Conduit: Surviving the Shadow Command of Corporate Construction — the source narrative, written from the trade floor. 196 pages. ISBN 979-8-9972777-0-3. Zenodo record 21488315.
• The Machine That Sees Itself: An Operating View for the People Who Hold the Authority to Act — Honest Authority Vol 1, the executive-register operating view. 170 pages. ISBN 979-8-9972777-1-0. Zenodo record 21470581.
• The Practitioner’s Handbook: Structural Command Theory Deployment Reference — SCT Tool Kit Vol 1, a deployment reference in the technical-standard tradition. 261 pages. ISBN 979-8-9972777-2-7. Zenodo record 21471056.

Three registers, deliberately separated: the floor, the seat, the tool. Start where you work.

Formats at release: trade paperback and direct-sale digital PDF. $30 paperback, $20 digital, direct from commandanalysisgroup.com — every copy pays the author the same wage wherever you buy; channel prices show each platform’s cut on the sticker.

The Books page carries the full program state. Release-day links land here and on the Books page on August 1.

Three new public instruments: case walkthroughs, the Misdiagnosis File, and a citation kit

Three additions to the site, all built from material already published at the working-paper depth:

• Case walkthroughs: documented public cases read structurally. The record first, the framework’s questions second, the published diagnostic read third, sources attached. Opening set: the Challenger launch decision (1986), Wells Fargo cross-selling (2011 to 2016), and Kodak’s digital transition (1975 to 2012).
• The Misdiagnosis File: a symptom-first index into the failure-mode catalog. Enter by the label your workplace uses (“micromanagement,” “a communication problem”), leave with the structural pattern, the discriminating question, and the citation.
• Citation kit: APA, Chicago, BibTeX, and RIS formats for all three working papers, a downloadable BibTeX file, DOI and ORCID references, and CC-BY attribution guidance.

Also in this release: the newsletter signup copy now names who writes it. One person writes this site; the copy says so plainly.

The Code in the Conduit working draft v0.5d

The book is at 17 chapters across three parts, with a closing piece, ~44,900 words.

Trade-book publication target: spring 2027.

FM-11 Capture Pattern canonicalized

A new structural failure mode — FM-11 Capture Pattern — has been registered in the SCT specification. The pattern: a structural form is in operation, but its substance is not produced; the authority controlling the form maintains it without the substance the form was designed to enable.

Two named sub-forms within FM-11: Procedural Capture (process-control layer) and Measurement Capture (instrumentation layer).

Distinguished from FM-7 Execution Fiction (passive absence of mechanism) by the active-suppression discriminant; distinguished from FM-9 Governance Visibility Gap (absence of visibility) by the presence-of-instrument-designed-to-look-like-visibility discriminant.

Economic-theory lineage cited: the public-choice rent-seeking and regulatory-capture literature (Buchanan and Tullock 1962; Tullock 1967; Krueger 1974). FM-11 will appear in the next revision of the SCT working paper.

Lived workplace case study enters closure

The lived workplace case study that anchored the framework’s empirical observations entered its closure phase on this date. A terminating event in the case study coincided — to the day — with the canonicalization of FM-11 Capture Pattern in the framework specification.

The structural failure the framework had been refining language for fired empirically in the lived case the same day that language was made canon. The coincidence is documented as the case study’s closure event and as part of FM-11’s first empirical anchor.

Active observation continues in subsequent positions; the lived material from the closed period is being prepared as the source for Book 2 of The Code in the Conduit stream, after appropriate de-identification and discipline.

SCT-SCL-ECC v1.5 working-paper trilogy fully deposited at Zenodo

All three working papers are now live with permanent DOIs and CC-BY 4.0 licensing. The series is complete as prior-art protection; reference and download information is on the Papers page.

Publishing-name standardization to Brandon S. Goe

The publishing byline across all working papers, the books in development, and this site is now standardized to Brandon S. Goe.

ORCID profile name remains Brandon Scott Goe as the canonical identity; both forms are linked for citation discoverability.

Working paper trilogy v1.5 released

All three working papers — Goe 2026a (SCT), 2026b (SCL), 2026c (ECC) — completed their v1.5 polish pass today. The release integrates the Family Floor doctrinal currency, sharpens the Recoverable Error Standard, and brings the three papers into citation-coherent alignment with one another.

v1.5 is the version that will be deposited to Zenodo.

Axiom 9 added to SCT: Workforce-AHJ-Operational-Hierarchy

A ninth axiom entered the Structural Command Theory specification: Workforce-AHJ-Operational-Hierarchy.

The axiom formalizes the structural relationship between (a) the workforce that performs the operation, (b) the Authority Having Jurisdiction (AHJ) — the externally-binding standards body or regulator — and (c) the operational hierarchy that holds tactical command. Each layer’s authority is bounded by what it can structurally confirm; the layers are not interchangeable; command flows in one direction and accountability flows the other.

The axiom closes a gap in the framework where construction-industry and rank-based-organization examples had been describing this relationship informally without an explicit structural statement.

SCL Corollary 5.4 Recoverable Error Standard added

A new corollary entered Servant Command Leadership: the Recoverable Error Standard.

A leader’s responsibility under SCL Axiom 5 (Honest Feedback) is not to be infallible. It is to operate so that errors made in good faith remain recoverable — visible, attributable, correctable — rather than absorbed into the structure where they become impossible to surface.

The corollary makes the recoverable-error standard explicit so that it can be tested rather than left to interpretation.

Value Fiction registered as a named form within FM-7

A named sub-form of FM-7 Execution Fiction is now part of the framework: Value Fiction.

The pattern: a value or benefit is asserted as produced by an organizational mechanism, but the mechanism does not actually produce the value claimed. The form is in operation; the value is not.

Value Fiction is the value-pointed instance of the broader Execution Fiction pattern — it sharpens the failure-mode taxonomy by giving the value-claim variant its own discriminant.

Capability Floor formalized: FM-10 False Floor and the Duty to Step Aside

A new structural failure mode and a paired conduct corollary entered the framework.

• FM-10 False Floor. Authority is held by someone who lacks the operational capability the role requires — but the structural form treats the floor as present. The mechanism: a confirmed-authority signal continues to be produced after the underlying capability has decayed.
• Corollary 1.4 Duty to Step Aside. The SCL conduct correlate. When a leader recognizes the floor has fallen below role requirements, the leader has a structural duty to step aside.

Together these close a class of failure the framework had previously described informally but not specified.

The North Star is stated

The framework’s foundational purpose statement — the North Star — is now formally registered.

The purpose of this body of work is to make the framework complete, logical, and fully available, so that anyone who would implement it has everything they need to do so. The measure of the work is the completeness and soundness of the knowledge, not its commercial uptake.

This is the senior reference for every decision the work makes. When two commitments are in tension, this is what governs.

Three-paper architecture decided: SCT, SCL, ECC each get their own working paper

The framework’s three companion specifications will be published as three separate working papers rather than as a single combined document.

• SCT (Structural Command Theory) — the structural-authority core.
• SCL (Servant Command Leadership) — the conduct framework that operates downstream of SCT-confirmed command.
• ECC (Executive Command Center) — the visibility-instrumentation domain that operates strictly downstream of confirmed command.

Each paper stands on its own and cites the others. Splitting the architecture this way keeps each specification independently citable and independently refutable — and reflects the framework’s own discipline about structural separation.

Framework architecture stabilized at Rev 6

The body of work entered its current maturity baseline today. The framework’s architecture — its three companion specifications (SCT, SCL, ECC), the NONCOLLAPSE constraint that binds them, the failure-mode taxonomy, and the published-paper / book / practitioner-reference surfaces — is now stable enough for sustained refinement rather than continued restructuring.

This is the version of the framework that subsequent working papers and books will derive from.

Execution Fiction named for the first time

The structural failure mode now canonical as FM-7 Execution Fiction — a mechanism that has the form of doing work without actually doing the work — was named explicitly for the first time today in a draft titled ExecutionFiction v1.0. The naming preceded the full failure-mode taxonomy by several weeks. FM-7 was one of the first named failure modes in the framework and has since been refined with named sub-forms (Value Fiction, registered 2026-06-02).

Command and Governance Field Ledger (CGFL) full specification

The Command-and-Governance Field Ledger — the earliest formalized field-deployment instrument for the structural-authority discipline — reached a full specification today. CGFL was iterating rapidly through this period (v6 within ten days). The discipline of producing field-usable, structurally-disciplined ledger forms — visible, accountable, transferable without the author present — dates from this work.

Governance Asset Stewardship Control baseline established

The framework’s governance-asset stewardship-control scheme — an early precursor to what is now the ECC visibility-instrumentation domain — reached its v0 baseline. The discipline of tracking which assets, decisions, and visibility instruments belong to which authority layer dates from this point.

First Command-Governance synthesis drafted

The first substantive synthesis document — the Command-Governance Suite — was drafted today. This was the earliest unified attempt to write down the structural-authority and governance-accountability ideas that would eventually become SCT, SCL, and ECC. The terminology had not yet stabilized; the names “Structural Command Theory,” “Servant Command Leadership,” and “Executive Command Center” were still ahead.

Research anchor: governance and stewardship literature compiled

The earliest cataloged reference material for what became the framework was compiled around this date — governance, stewardship-control, and protected-area-management literature pulled into a working library. The framework’s structural-authority claims have a literature lineage; this date marks the start of that lineage being tracked in writing.