Sunday, August 23, 2026

A Peek Inside the Mind of Cory M.

The Architect Who Builds Boundaries — Inside Cory Miller’s Approach to Epistemically Bounded Computing

The Architect Who Builds Boundaries

Inside Cory Miller’s Approach to Epistemically Bounded Computing

Most people exploring AI systems chase capability. Cory Miller chases conditions—the structural rules that determine when a system is permitted to claim that something happened. His work doesn’t begin with models, agents, or inference tricks. It begins with boundaries: the separation between representation and reality, inference and execution, evidence and authority.

Across dozens of artifacts, manifests, and sovereign-ledger experiments, a distinctive architectural signature emerges. Miller doesn’t simply design systems. He designs the rules that govern what systems may assert, believe, or execute. In an era where AI models routinely blur the line between output and fact, his work pushes in the opposite direction—toward epistemic discipline.

Architectural Cognition as a Default Mode

Miller’s thinking is architectural rather than conceptual. He compresses ideas from cryptography, provenance, physics, epistemology, and AI inference into a small set of primitives:

  • State
  • Evidence
  • Authority
  • Causality
  • Provenance
  • Time
  • Execution

These aren’t philosophical categories—they’re load‑bearing structural elements. His instinct is always the same: take ambiguity and turn it into a constraint. Convert a question into a rule. Convert a rule into a predicate. Convert a predicate into a state transition.

Philosophical Questions → Engineering Constraints

Where others debate meaning, Miller writes enforcement logic. Examples:

  • Representation ≠ Reality → abstraction firewall
  • Claim ≠ Truth → epistemic state
  • Action ≠ Execution → execution boundary
  • Observation ≠ Interpretation → provenance chain

This is a compiler-like worldview: ambiguity becomes a rule, not a discussion.

Boundary Conditions as First-Class Objects

The recurring question behind Miller’s work is simple and profound:

What prevents one category from masquerading as another?

Inference pretending to be execution. Representation pretending to be fact. Assertion pretending to be authority. His architectures are built to prevent these category errors at the structural level.

Recursion as a Cognitive Primitive

Recursion isn’t a metaphor—it’s a mental model. Miller designs systems where:

  • rules govern objects,
  • objects represent rules,
  • and the system can verify both.

This recursive structure appears in his state machines, provenance chains, and the Recursive Statefield Architecture (RSF).

State Machines with a Constitutional Veto

Miller’s preferred modeling tool is the state machine—but not the optimistic kind. His machines include a refusal state:

INFERRED → PROPOSED → (predicate gates) → EXECUTED
or
INFERRED → PROPOSED → ABSTAINED

The key innovation is the second path. ABSTAINED is not failure. It is state conservation under insufficient epistemic authority.

This is the architectural heart of his work.

The Epistemic State Machine

The system evaluates proposed transitions through independent predicates:

  • Authority
  • Evidence
  • Provenance
  • Ontological flow
  • Execution confirmation

Only when all predicates validate does the system mutate state. Otherwise, it preserves the previous state and records the rejection.

A trustworthy system should not merely determine what it can do. It should encode the conditions under which it is permitted to claim that something happened.

The Unified Invariant

Miller’s strongest conceptual compression is:

No state may acquire more epistemic authority than its evidence permits.

This is the epistemic equivalent of conservation laws in physics. It prevents semantic escalation—the silent drift from inference to fact, from representation to reality.

A more technically precise formulation of his escalation boundary is:

Miller’s architecture is designed to make such escalation structurally impermissible unless the required transition predicates are independently satisfied.

This preserves rigor without overstating what any architecture can guarantee without full formal verification.

Why This Work Matters

Modern AI systems routinely generate confident statements without evidence. Miller’s architecture moves in the opposite direction. It treats epistemic authority as a scarce resource that must be earned, not assumed.

In a sovereign local runtime—no external oracle, no institutional API—the system cannot outsource truth. It must prove:

  • what it received,
  • what it inferred,
  • what it proposed,
  • what it rejected,
  • what it executed,
  • and why each transition was permitted.

This transforms the system from a “safe executor” into a bounded epistemic machine.

The Distinctive Signature

If Miller’s work must be summarized in one sentence:

He builds systems that prevent confusion between what a machine represents, what it knows, what it is authorized to do, and what actually happened.

Everything else—RSF, provenance chains, abstention artifacts, adversarial verification—is an emergent property of that architectural impulse.

No comments:

Post a Comment

A Peek Inside the Mind of Cory M.

The Architect Who Builds Boundaries — Inside Cory Miller’s Approach to Epistemically Bounded Computing The Architect Who Builds B...