Research Papers and Prior Art
Academic foundations of Organizational Schema Theory: the DSR paper, the practitioner audit protocol, and the twelve-property prior art comparison.
Papers
Foundational
The Organizational Schema Theory: Test-Driven Business Design
Introduces Organizational Schema Theory as a specification-first methodology where customer experience goals function as acceptance tests for business operations. The six-level cascade (L0 customer experience contracts → L1 signal requirements → L2 process contracts → L3 procedures → L4 input specifications → L5 sourcing) makes each level the acceptance test for the level below. Designed top-down, validated bottom-up by a CI/CD pipeline that traces every operational parameter back to its customer-experience justification. The v1.3 revision adds a twelve-property structural comparison matrix (Table 4) showing what each adjacent methodology — BDD, BPMN, ISO 9001, IaC, Service Blueprinting, OKR + SLO/SRE — provides by design and where the seams between them become operationally costly when AI agents begin consuming organizational specifications directly. The DSR artifact is the methodology itself, demonstrated through the Spectra Coffee reference deployment (twenty-five YAML files, six products, full cascade, CI/CD passing). Currently under review at the European Journal of Information Systems.
The OrgSchema Audit: A Six-Level Diagnostic for Specification-Driven Organizations
Translates the six-level specification cascade of Organizational Schema Theory into a practitioner-executable audit protocol. Each audit level defines what to examine, what a healthy specification looks like, what failure modes indicate, and what corrective actions restore specification integrity. A worked example (Spectra Coffee, Berlin) demonstrates the full protocol. Positioned against five existing diagnostic frameworks (PEMM, service blueprinting, Balanced Scorecard, QFD, CMMI, EFQM). Advances two testable propositions: cascade-position prioritization and bidirectional traceability completeness.
OST Companion
Verification as Operator: Why Acceptance Testing Succeeds Where Conventional Audit Fails
Formalizes organizational acceptance testing as a full-rank projection operator and conventional audit as a rank-1 projection. Using the projection-operator identity, the paper proves that rank-1 audit systematically misses ~90% of specification deviation across all noise levels — confirmed by Python simulation. Power (1997) serves as the critical foil: audit failures are reinterpreted as failures of operator rank, not auditor effort or methodology. The Discussion adds a cross-domain validation subsection citing independent work in capital-markets and DeFi composability that converges on the same operator-theoretic structure. Target venue: Academy of Management Review.
Extended Theory
Organizational Metamerism: When Distinct Configurations Produce Equivalent Outputs
Introduces organizational metamerism as a state-equivalence concept, extending equifinality (Gresov and Drazin 1997) from path-equivalence to a structural account of why distinct organizational configurations executing the same process produce equivalent value outputs to a given evaluative observer. Equivalence is observer-relative: configurations metameric for one observer need not be metameric for another. The metamerism set M(P, O) expands as coordination logic is embedded in process specifications and shrinks with tacit knowledge intensity. Four propositions are stated with explicit confirming and refuting evidence criteria, including the prediction that AI-era organizations exhibit decoupled organizational restructuring frequency from process change frequency. Three empirical research designs are outlined.
A Six-Tier Ontology of Acquisition-Target Transferability: Dual Hierarchies and Failure-Propagation Mechanisms
Six-tier ontology of the acquisition target: Owner Intent, Business Model, Business Entity, Product, Process, and Organization. Each tier is defined by a unique governor, specification surface, and transferability mode. The tiers form dual overlapping hierarchies — service running upward, constraint running downward — that jointly determine integration sequencing. Seven falsifiable propositions on cross-tier failure cascades are derived from the dual-hierarchy structure. The framework is form-invariant across for-profit, NGO, cooperative, and state-owned organizational forms through explicit substitution rules. The Six-Tier Separability Diagnostic profiles each tier as Fused, Partial, or Independent for pre-close acquisition risk assessment. Target venue: Academy of Management Review.
OST shares theoretical foundations with Spectral Brand Theory. Cross-cutting papers on specification methodology, rendering problems, and meta-science are cataloged on the SBT Atlas — see Layer 4 (Cross-Domain) and Layer 6 (Meta-Science).
Prior Art: Structural Comparison
The framework builds on and differentiates from existing work in business process management, quality management, software engineering, and customer experience design. The right comparison is not "which methodology is best" — that depends on the decision being made — but "which structural properties does each methodology provide by design." The table below uses twelve properties chosen to be neutral with respect to popularity, tooling maturity, or training-base size. Each criterion tests what the methodology can express, not how widely it has been adopted.
Legend: ✓ — provides by design, ∼ — partial / domain-limited, — — does not provide.
| # | Property | BDD | BPMN | ISO 9001 | IaC | Svc BP | OKR + SLO | OST |
|---|---|---|---|---|---|---|---|---|
| 1 | Anchored in customer requirement, not process | ∼ | — | ∼ | — | ✓ | ✓ | ✓ |
| 2 | Machine-readable customer-requirement specification | ✓ | — | — | — | — | ∼ | ✓ |
| 3 | Machine-readable process / execution specification | ∼ | ✓ | — | ✓ | — | — | ✓ |
| 4 | Formal proof that the process satisfies the customer requirement | ∼ | — | — | ∼ | — | ∼ | ✓ |
| 5 | Orphan / waste detection (process without an upward trace) | — | — | — | ∼ | — | — | ✓ |
| 6 | Version control with git-style readable history | ✓ | ∼ | — | ✓ | — | ∼ | ✓ |
| 7 | Continuous validation instead of periodic audit | ✓ | — | — | ✓ | — | ∼ | ✓ |
| 8 | Works for non-human customers (API, algorithm, DPP) | ∼ | ∼ | — | — | — | ∼ | ✓ |
| 9 | Inputs, materials, and suppliers in scope | — | ∼ | ✓ | — | ∼ | — | ✓ |
| 10 | Schema / data separation as a first-class design principle | — | — | — | ∼ | — | — | ✓ |
| 11 | Forkability: replicate the tests, reimplement the execution | ∼ | — | — | ∼ | — | — | ✓ |
| 12 | Perceptual / brand dimensions as the upper-level specification language | — | — | — | — | ∼ | — | ✓ |
How to read this table without self-deception
The right-hand column is fully filled, and that pattern is suspicious. The reason it is filled is not that OST is magically superior — it is that the twelve properties were chosen to test the structural design of a cross-stack specification methodology, which is precisely what OST is. If the criteria changed to "number of certified organizations worldwide," "depth of consulting ecosystem," "number of trained practitioners on the labor market," or "production deployments at scale," the picture would invert: ISO 9001 would be near-fully covered, BPMN and IaC would have substantial coverage, and OST would have one reference deployment (Spectra Coffee) and a stack of working papers.
The table answers a specific question — "which structural properties does each methodology uniquely provide by design" — not the question "is OST the practically better choice today." Those are different questions, and conflating them is the easiest way to oversell a young framework.
What the table actually shows
Reading row by row, almost every property exists somewhere in an adjacent methodology. "Machine-readable customer specification" is provided by BDD (in the code domain). "Machine-readable process specification" is provided by BPMN. "Continuous validation" is provided by BDD, IaC, and partially SRE. "Supply chain in scope" is provided by ISO 9001. None of these properties is OST's invention.
What is uniquely OST is that all twelve properties are unified under one chain of artifacts in one format. No single adjacent methodology covers more than five or six cells. BDD is strong in the code domain but has no upward link to suppliers or perception. BPMN models processes but does not validate them against customer requirements. ISO 9001 covers supply chains but leaves machine-readable and continuous properties on the table. IaC is strong in infrastructure but is invisible to business operations and customer experience. Service Blueprint is a workshop drawing, not an executable specification. OKR + SLO link outcomes to operations but do not formalize the lower levels.
The structural risk in unification is real and worth naming. Bundling twelve properties under one roof can produce a methodology that is "average at everything and best at nothing." Specialization has historically won against unification in tooling adoption because narrow tools accumulate vastly more polish per unit of investment over time. The argument for OST is not that it will outcompete BDD on developer experience or BPMN on enterprise execution. The argument is that the seams between those tools become unbearable when AI agents start consuming organizational specifications directly — and at that point a unified machine-readable coordinate system stops being a luxury.
The honest one-sentence claim is this: OST is the first attempt to build a single version-controlled contract between customer experience, processes, executors, and suppliers, where consistency between levels is checked automatically and continuously rather than documented in prose and audited once a year.
The Convergence Thesis
Organizational Schema Theory and Spectral Brand Theory are two projections of a single system:
- SBT = the business observed from outside (observer-dependent perception across 8 dimensions)
- OST = the business observed from inside (operator-dependent specification across 6 levels)
Both frameworks sit within a broader six-tier ontology (Zharnikov) that decomposes any organization into Owner / Principal Intent, Business Model, Business Entity, Product, Process, and Organization. SBT measures Tier 4 (Product, via 8 perceptual dimensions). The OST cascade nests inside Tiers 4–6. The six-tier framework adds Tiers 1–3 above what SBT and OST already formalize, and is form-invariant across for-profit, NGO, cooperative, and state-owned entities. Read the article →
The interface between them is defined by an 8x6 activation matrix: which operational levels activate which SBT dimensions. The forward path (operations to perception) and reverse path (desired perception to required operations) are both formalized.
Neither framework is complete alone. SBT without orgschema is descriptive but not actionable. Orgschema without SBT is actionable but ungrounded.
Methodology
The paper follows Design Science Research methodology (Hevner et al. 2004, extended DSR). The artifact is the methodology itself, not the demo. Evaluation criteria:
| Criterion | Evidence |
|---|---|
| Feasibility | Spectra Coffee: 25 YAML files, 6 products, full cascade, CI/CD passing |
| Novelty | 10-entry prior art comparison. No existing work combines multi-level specification cascade + perception traceability + version control |
| Utility | Fork, validate, certify operations from a commit hash |
| Generalizability | Schema/data separation: methodology is publishable, parameters are competitive moat |