Runcible
01 / Mission

Company

Why did one company build both an institutional operating system and an epistemic engine?

Runcible turned a science of cooperation into an operating system and an epistemic engine.

One research program. Three organizations. Two products. One institutional capability.

Institutions create extraordinary capability by letting people specialize, coordinate, delegate, and act together. Runcible exists to preserve the conditions that keep that cooperation productive as complexity, intelligence, responsibility, and consequence expand.

The ambition is enabling: let institutions understand more, coordinate more, delegate more responsibly, adapt sooner, and pursue larger purposes without becoming less able to tell what is true or correct what has gone wrong.

01 / ExperienceOperate institutions.Carry responsibility for people, programs, decisions, and results.
02 / ScienceMake cooperation testable.Define truth, reciprocity, decidability, responsibility, and consequence.
03 / ProductsMake the science operate.Build the institutional world and epistemic engine.
04 / ConsequenceLet reality decide.Observe, correct, remember, and improve.
02 / Learned in Operation

The Operating Origin

The company began with responsibility for operating companies, not an AI market.

How can an owner build, acquire, and manage companies with operational excellence and deep transparency without waiting for delayed, filtered reconstructions of reality?

The question emerged through more than two decades of founding and building consulting companies, serving large enterprises and domestic and international governments, and carrying responsibility for clients, programs, people, delivery, resources, decisions, and financial results.

An owner remains accountable for the whole while causes become local and consequences arrive later. Departments, managers, applications, definitions, incentives, and close cycles each create a partial account.

The problem was not management. Institutions need managers who exercise judgment, coach people, coordinate scarce resources, remove constraints, and accept responsibility. The problem was dependence upon any layer’s privately assembled account of what the institution was doing and why.

The required alternative became one shared institutional model in which purpose, programs, people, dependencies, responsibility, decisions, time, money, action, consequence, correction, and history remain connected.

01Responsibility for the wholeCompanies, people, clients, commitments, and financial consequence.
02Different private accountsDepartments, systems, definitions, timing, and incentives.
03Delayed knowledgeCauses remain local while consequence reaches the owner later.
04Shared operating worldPurpose, work, decisions, resources, and history become related.
05Earlier correctionIntervene, contest, adapt, and retain what was learned.

The software problem appeared only after the institutional problem had been experienced often enough to become a theory.

03 / The Failure Mechanism

What Scale Can Break

Opacity allows divergence to become institutional power.

Four pathologies describe what becomes visible. The causal progression explains why it can become self-reinforcing.

01Organizational myopia

The part optimizes its measures while losing the institution’s purpose.

02Parkinson’s expansion

Work and bureaucracy grow without an examinable relation to value.

03Self-determination

Groups direct institutional resources toward preferred objectives.

04Political capture

Coalitions control information, procedure, resources, decisions, and incentives.

OpacityState becomes private or delayed.
AdvantageSome roles control interpretation.
Self-interestPreserving advantage becomes rational.
CaptureProcedure protects divergence.
DeclineCorrection weakens recursively.

Runcible does not assume corrupt intent or claim to eliminate human nature. It changes observability, attribution, contestability, and the value of privately controlling the institutional narrative.

An institution remains adaptable only while it can discover and correct divergence from within.

04 / The Science

Making Cooperation Testable

A problem this deep required a science of cooperation, not another management doctrine.

The research program worked toward operational definitions and tests for truth, reciprocity, cooperation, ethics, decidability, responsibility, liability, and sustainable institutional order.

Truth

What survives examination?

Exact propositions, evidence, tests, repair, and what remains open.

Reciprocity

What is supplied and demanded?

Satisfaction, transferred cost, affected parties, and sustainable exchange.

Responsibility

Who must decide?

Role, decision rights, delegation, liability, action, and revocation.

Practicability

What can actually work?

Constraints, resources, sequence, consequence, and limits.

Decidability

What can close?

Support, failure, qualification, repair, deferral, or explicit open state.

Institutional order

What keeps the whole coherent?

Purpose, roles, work, judgment, action, consequence, and memory.

Institutional Conditions

Runcible OS

World, purpose, identity, roles, internal law, resources, coordinated action, accounting, consequence, and memory.

Epistemic Conditions

Runcible AI

Curation, scientific testing, economic decidability, reciprocity, repair, explicit limits, and warrantability.

The research was not built to explain Runcible after the fact. Runcible was built because the research was intended to operate.

05 / Three Organizations

One Program, Three Forms of Work

Science, institutional software, and machine judgment could not honestly be treated as the same job.

01 / Research

The science

Question
What makes truthful, reciprocal, decidable cooperation possible?
Work
Definitions, reductions, tests, responsibility, liability, and institutional theory.
Contribution
Method and constraints supplied to both products.
Tested by
Coherence, evidence, adverse cases, and expert challenge.
02 / Product

The institutional world

Question
How do the conditions become everyday operation?
Work
Programs, structures, roles, workflows, time, goals, communication, finance, and history.
Contribution
Runcible OS: world, internal law, accounting bridge, and memory.
Tested by
Product behavior, institutional use, and operating result.
03 / AI

The epistemic engine

Question
How can information be understood, tested, repaired, bounded, and recorded?
Work
Propositions, demands, evidence, scientific method, decidability, open states, and records.
Contribution
Runcible AI: embedded capability and separate license.
Tested by
Adverse cases, repeatability, integration, and consequence.
01Research constrained the products.
02Operation exposed new questions.
03The OS supplied an institutional world.
04AI made more of the world useful.

Three organizations were the cost of refusing to pretend that science, institutional software, and machine judgment were one problem.

06 / Historical Sequence

World Before Institutional Intelligence

The operating system revealed what an institutional intelligence would need.

The platform was needed to discover what AI capable of institutional participation would actually have to know, test, remember, and do – and to give judgment a world in which it could acquire accountable consequence.

  1. ScienceDefine the institutional and epistemic problem.
  2. Institutional worldRepresent identity, state, work, responsibility, resources, action, and memory.
  3. Feasible AI methodApply the scientific and economic method through language-native models.
  4. Integrated intelligenceLet world and mind work upon the same accountable matters.

Historical order describes what happened. World and epistemic mind working together describes what the products are.

07 / Present Architecture

Built in Sequence. Coupled in Operation.

Today the program is tangible as two products and one complete system.

Implement

Runcible OS

The institutional world and memory. Connect purpose, programs, people, responsibility, resources, work, time, financial state, consequence, and history.

License

Runcible AI

The epistemic engine. Curate, improve, test, repair, adjudicate, bound, and record consequential information inside a qualified environment.

Use Both

The Runcible System

AI improves information. Responsible people decide. Authorized action changes state. Consequence returns through accounting, correction, and memory.

Storing information does not make it true. Reaching a supported judgment does not grant the AI responsibility or permission to act.

08 / The People

Disciplines Required by the System

The team spans the forms of judgment Runcible must join.

The current public leadership roster is preserved here for factual continuity while names, titles, engagement, contribution descriptions, biographies, and publication consent are reconfirmed.

B. E. Curt DoolittleFounder and CEOMethod, institutional theory, product architecture, and program direction.
Bradley H. Werrell, D.O.President and Co-AuthorMethod development, medical application, and external representation.
Eric AdamsChief Operating OfficerOperations, finance, legal coordination, growth, and transaction execution.
Moritz BierlingEVP, Outreach and OperationsOutreach, communication, customer relationships, platform execution, and market translation.
Francis ZhouChief Product and Program OfficerProduct requirements, engineering coordination, quality, and customer problem translation.
Luke WeinhagenChief Compliance OfficerScience of cooperation, technology consulting, delivery, and compliance discipline.
Noah RevoyEVP, TrainingBehavioral science, agency, manipulation resistance, and training strategy.
Brandon HayesEVP, Strategy and Legal SystemsLegal systems, policy, strategy, and legal-domain application.
The broader program includes distributed research, training, protocol, engineering, and domain contributors. Final publication requires current-role and consent verification.
09 / Evidence, Not Mythology

The Burden Created by the Origin Story

The longer the program, the greater the obligation to prove it.

A twenty-year narrative is not evidence because it is ambitious or coherent. Each part requires the kind of proof appropriate to it.

OperatingDated operational records

Companies, clients, programs, acquisitions, responsibility, and results that may lawfully be disclosed.

ScientificVersioned method and challenge

Definitions, papers, contrary cases, open questions, and expert review.

ProductCurrent artifacts and complete traces

Demonstrations, operating records, maturity labels, limits, and corrections.

AIRecords and adverse cases

Repeatability, method boundaries, failures, open states, and integration evidence.

CorporateEntity and asset records

Ownership, licenses, rights, relationships, dates, and corporate authorization.

CommercialBuyer and implementation evidence

Customer need, adoption, operating consequence, and bounded economic measures.

Not a model labNot a think tankNot ERP plus chatbotNot retrospective brandingNot mission without discipline

Research is what we propose. Products are what we built. Consequences are what will decide whether the program is true.

10 / Mission Made Operational

The Commercial Consequence

The mission advances one institution, one product, and one consequential loop at a time.

Implement Runcible OS to make an institution more visible, coordinated, accountable, and adaptable. License Runcible AI to improve consequential information inside another qualified environment. Use both to build an AI-native institution in which human and machine intelligence learn from the same accountable reality.

Make cooperation durable enough for people and institutions to keep growing.

RuncibleScience made operational. Products made accountable to consequence.