Doctrine

Ontological Orchestration in AI-Assisted Development

Positions I've taken on how AI-assisted development is evolving, tracked against real-world evidence.

Core Thesis

Technology roles are shifting from discrete execution to ontological orchestration: the definition, constraint, and sequencing of meaning in systems where execution is increasingly abundant.

Claims

  1. Execution is no longer the dominant constraint

    For most software-driven organizations, the cost of producing artifacts (code, designs, drafts) is falling faster than the cost of deciding what should exist and how it should behave.

  2. Roles bifurcate in large enterprise and regulated contexts

    In large enterprises and regulated industries, AI may produce role bifurcation rather than convergence: a smaller tier of elite generalists who define harnesses and systems, and a larger tier of commoditized execution roles whose tasks are increasingly AI-mediated and narrowly scoped.

Working Definitions

Ontological orchestration
Defining what exists, what matters, how components relate, and what constitutes correctness in a system—before and during execution.
Harness
A structured package of intent, constraints, artifacts, and validation mechanisms that bounds and guides execution (human or agentic).
Intent hypothesis
A falsifiable statement describing a believed problem, its context, constraints, and success criteria.
Situated authorship
Authorship determined by surface-area expertise and problem context rather than formal role.