Frequently Asked Questions
Proactive answers to the questions the framework will be asked. If your question isn't here, write — see Contact. The FAQ is updated quarterly with new questions as they recur.
Why is the framework CC-BY 4.0 licensed?
Because the framework's authority depends on its openness, and licensing is the technical mechanism by which that openness is made enforceable. The framework's stated purpose (North Star) is that anyone who would implement it has everything they need to do so. A more restrictive license would substitute a commercial barrier for the openness the framework's claim rests on.
Practically: CC-BY 4.0 permits any use, including commercial, provided attribution. Practitioners can quote, remix, train teams on, and build derivative tooling around the framework with no permission needed beyond honoring the attribution.
The licensing posture is intentional. The framework's claim is that completeness, soundness, and availability are what authority survives scrutiny by. A restrictive license would substitute access-control for the openness the claim rests on.
Where does the framework's authority come from?
It does not come from the author's credentials, the publisher, the marketing, or the price. It comes from the framework's own properties: completeness (every named construct has a definition, a discriminant, a relationship to adjacent constructs); soundness (the axioms are explicitly stated and the discriminants are testable); falsifiability (each axiom carries a negative test specifying what evidence would refute it); openness (the working papers are freely available under CC-BY 4.0); transparency (the canonical revision history is dated and the change log is public); and willingness to be wrong (the contact page exists for exactly this).
The framework's authority is the kind that survives scrutiny. It is what the work calls honest authority. The first volume of the Honest Authority series in development — The Machine That Sees Itself: An Operating View for the People Who Hold the Authority to Act — develops this construct at the executive operating-view scale, and the series will continue to develop authority-bound-to-accountability across additional volumes. Until those books are published, the working operationalization is in this FAQ entry.
Why work with AI on a framework about authority?
Because AI assistance is a tool, and the framework's claims survive the tool's involvement the same way they have to survive any other input. The author drafts with AI assistance, reviews and edits all output, and bears full responsibility for the claims. The disclosure is on every paper, every book, and this site. If the use of AI changes any reader's evaluation of the framework's claims, that change is a substantive critique that belongs in Contact and will be engaged seriously.
The framework's discipline — completeness, soundness, falsifiability, source-citation — applies identically whether the first-pass prose was drafted by the author alone, by the author with AI assistance, or (in some hypothetical future) by AI alone. The author currently uses AI assistance because it accelerates the cycle and surfaces drafting gaps a single-author cycle would miss. The author retains all responsibility for what stays in the published artifact.
What's the relationship between SCT and existing leadership / organizational theory?
The working papers engage the relationship at length (see Papers). The short version:
- SCT is structural where most existing organizational theory is behavioral. The framework's first move is to insist that structure be verified before behavior is diagnosed (Axiom 10 Diagnostic Sequence Discipline).
- SCL inherits from the servant-leadership tradition (Greenleaf and successors) but anchors it in structural subordination to SCT and in operational specification that the existing literatures generally lack.
- ECC formalizes what the visibility / instrumentation / dashboard literature has been doing informally for decades, with a categorical-distinction discipline that prevents the most common error in that space (treating the visibility instrument as if it were the authority).
- The framework engages — by name and citation — Argyris and Schon, Edmondson, Hirschman, Buchanan and Tullock, Tullock, Krueger, Coase, Williamson, Jensen and Meckling, Simon, Ostrom, North, Acemoglu and Robinson, and others. Specific engagements are in the dissertation chapter draft as it matures.
The framework's claim is not "this is new." The claim is "this is a complete, operationally specified, falsifiable apparatus for doing the work the existing literatures do informally, with the categorical discipline that protects the diagnosis from collapsing."
What if you're wrong?
Then the framework's discipline obliges the canon to be amended, the change to be dated in the public update log, and the contributor to be credited. The author has done this before. Look at the change history of the working papers and the canonical change log — it is exactly the trace of where prior claims were sharpened, narrowed, or replaced when the evidence required it.
The author's commitment to being open about being wrong is the operational expression of the framework's own claim about authority. An authority that cannot survive scrutiny is not authority; it is performance.
When will the books be available?
The work is organized as three parallel streams, each written for a distinct audience. See the Books page for the full structure.
Stream 1 — The Code in the Conduit (lived-account, for tradesmen and general readers)
- Book 1, The Code in the Conduit — source narrative; trade-book publication target spring 2027.
- Book 2 (working title TBD) — lived-struggle longitudinal document; capture ongoing; publication when material density and de-identification discipline allow.
Stream 2 — Honest Authority series (executive operating view, for executives, boards, and governance bodies)
- Book 1, The Machine That Sees Itself: An Operating View for the People Who Hold the Authority to Act — in development; publication target after Book 1 of Stream 1.
- Subsequent volumes — develop the executive operating-view program across additional dimensions (civic-scaling, macro-stakes diffusion, polity-scale authority structure).
Stream 3 — The SCT Tool Kit (practitioner deployment instrument, for anyone deploying the framework in an organization). Reference library, not a sequential book series.
- First item, The Practitioner's Handbook — deployment instrument; in development; publication target downstream of the framework's first practitioner deployments and accumulated case-study volume.
- Subsequent items — empirical-program operationalization specifications, diagnostic-instrument refinements, case-study volumes, training-program materials, sector-specific deployment templates. Accumulate as the framework develops.