Articles on Specification-First Business Design

Introduces the Organizational Schema Theory through its most counterintuitive consequence: an entire business — products, processes, quality gates, sourcing — specified in version-controlled YAML files. AI is a resolution upgrade: like microscopes changed biology from organism-level to cell-level observation, orgschema changes business operations from narrative summaries to testable specifications. The AI-augmented operator does not run the same business faster — they operate at a different level of structural granularity. Fork it, adapt it, deploy it.

A brand is not a logo. It is the total pattern of perception constructed from every signal the organization emits — most of them undesigned operational by-products. The bathroom cleaning schedule emits a "we care about details" signal whether anyone intended it or not. Orgschema bridges the gap between brand strategy (which specifies 10-15% of signals) and operations (which produce the other 85-90%). When brand signals and operational processes live in the same specification, coherence is built into the architecture.

By 2027, every battery sold in the EU needs a digital passport. By 2028, every garment. The DPP requires machine-readable product data: materials, carbon footprint, recyclability, supply chain provenance. For most businesses, this is a new documentation burden. For orgschema businesses, it is a format conversion from data they already maintain. Continuous certification from a commit hash replaces annual audits. When AI shopping agents query DPP registries, specification-first businesses are discoverable. The rest are invisible.

The traditional franchise model ships procedures (how to do things) and enforces compliance through audits. Orgschema ships contracts (what must be achieved) and enforces compliance through CI/CD. The franchisee copies the test suite — L0 experience contracts, L2 process contracts, quality gates — and writes their own implementation. Local adaptation is a feature, not a violation. The fork model: same tests, different procedures, validated automatically.

ISO 9001 requires documented procedures, quality objectives, management reviews, and continuous improvement evidence. Orgschema specifications provide all of these natively: YAML files are the documented procedures, L0 contracts are the quality objectives, the git log is the management review trail, and every commit is evidence of continuous improvement. The auditor reads the specification and the CI/CD pipeline history. Certification becomes a property of the commit hash, not a point-in-time judgment.

McDonald's operational DNA — from the Speedee Service System to the modern Operations and Training Manual — is the most sophisticated business specification ever built. It achieves what orgschema formalizes: contract-procedure separation, executor-independent process contracts, multi-level validation, and relentless schema/data separation. The difference: McDonald's specification is proprietary and analog. Orgschema makes the pattern digital, version-controlled, and forkable.

Your next most important customer might not have eyes. It will not appreciate your origin story. But it will reject your API if response time exceeds 200ms. The specification cascade is observer-agnostic: for machine customers, L0 becomes a formal specification and L1 collapses — the signal IS the specification. No perception gap. No non-ergodicity. Validation becomes deterministic. For hybrid customers (AI shopping agents, procurement algorithms), the machine narrows and the human decides. Unspecified value is invisible value.

Brand perception is not something you design separately from operations. It IS your operations, perceived by observers through SBT's eight dimensions. The git log of an orgschema specification is a brand history: every process change, every sourcing decision, every quality gate adjustment emits signals that observers perceive. The convergence thesis: SBT and Organizational Schema Theory are two projections of a single system — the business observed from outside (perception) and from inside (specification).

A technical walkthrough mapping every parameter in the Spectra Coffee demo to SBT's eight perceptual dimensions. Extraction time is experiential. Hand-chalked menu boards are semiotic. Quarterly blend rotations are temporal. Direct-trade sourcing is ideological. The signal map contains 19 explicit mappings. When the customer is a machine, the dimensions transform from perceptual to functional — but the operational specification is the same YAML.

SBT and Organizational Schema Theory are not complementary tools. They are two descriptions of a single phenomenon — like light having wave and particle descriptions. SBT describes the business as observers perceive it (wave). Orgschema describes the business as operators specify it (particle). The 8x6 activation matrix formalizes the interface: which operational levels activate which perceptual dimensions. Neither framework is complete alone.

The brand/operations split is not a feature of business reality. It is an artifact of how management theory developed in the 20th century. The customer experience contracts ARE the brand strategy. Every YAML file in the operational specification is a brand decision. Every brand decision is an operational requirement. If the specification is the brand strategy, then whoever owns and maintains the specification owns the brand. The org chart separation between brand and operations is structural waste.