Research Papers and Prior Art

Papers

Foundational

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.

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)

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: