Resources / Technical reference
Technical Reference: The Runcible Examination Pipeline
The representation, examination, output contract, and authority boundary in one compact specification.
In this article
- 1. Input, representation, examination, record
- 2. Normalize without erasing material distinctions
- 3. Construction is a test of possibility
- 4. Keep the result types distinct
- 5. Non-closure is an output contract
- 6. Enforcement belongs outside the generating model
- 7. Retention and refinement
- 8. Evaluate the whole chain
Runcible treats language as an operational representation that must retain enough information to test a claim. Foundation models supply candidate interpretations and constructions. The runtime reconstructs their dependencies, exposes possible defeat, and preserves the grounds and limits of the resulting disposition.
The compiler boundary is between plausible semantic content and an examinable operational claim. The authority boundary is between an examined recommendation and a permitted institutional action.
1. Input, representation, examination, record
Let C be a candidate claim, K the relevant context and evidence, and Q the requested reliance. The compiler constructs a representation O(C, K) and a set of material examination obligations T(O, Q). Executed tests and their artifacts produce a record R.
This notation specifies responsibilities; it does not prove completeness or termination. The representation can omit a dependency, the proposed tests can be insufficient, and a tool result can be unreliable. Those are objects of further examination.
2. Normalize without erasing material distinctions
Operational representation binds actors, objects, relations, operations, resources, sequence, evidence, scope, affected interests, and limits. RDL progressively formalizes that representation and the compiler’s handling of it.
Enumeration separates assertions. Operationalization identifies what would make each assertion testable. Serialization preserves temporal and dependency order. Adversarial disambiguation challenges substitutions, missing premises, scale changes, and unsupported causal relations. The sequence repeats as new dependencies appear.
A successful reduction preserves the distinctions required by the intended use. Compressing unlike obligations into one score is not commensurability unless the common measure and lost information are accounted for.
3. Construction is a test of possibility
Constructive falsification specifies what must exist and occur for the claim to hold. An impossible prerequisite or contradiction defeats the construction. A missing prerequisite leaves the claim unestablished. A surviving construction supports possibility under its conditions; actuality requires its own evidence.
Top-down decomposition starts from the asserted whole. Bottom-up reconstruction starts from identifiable entities, permissible operations, observations, and constraints. Their meeting point is an examined dependency graph, not merely a coherent narrative.
4. Keep the result types distinct
- Possibility: The operational construction and its constraints.
- Ethics and morality: Demonstrated interests, obligations, consent, transferred costs, reciprocity, and remedies.
- Truth and testifiability: Correspondence, evidence, inference, scope, and the surviving examination.
- Warrantability and liability: Permitted reliance, responsible parties, residual risks, and correction or restitution.
Legal, cultural, class, sex-related, organizational, and individual alignments are explicit contextual conditions where relevant. They do not determine factual truth by preference. A detected omission also does not establish deceptive intent without additional evidence.
5. Non-closure is an output contract
The record must distinguish a defeated condition from an unresolved one. It should identify missing evidence, disputed interpretation, incomplete search, conflicting obligations, or the need for an authorized adjudicator. A repair is a new candidate requiring examination.
Contextual decidability does not repeal algorithmic undecidability. It identifies the disposition available for a specified matter and reliance. Verification that a test ran is necessary where execution is required; it is not equivalent to survival from an adequate falsification attempt.
6. Enforcement belongs outside the generating model
Runcible and the generating model produce and examine candidates. Oversing maintains institutional state and governs decisions and authorization. It issues a bounded mandate to a separate executing model or tool. The generating model cannot grant itself permission, and the executor must not enlarge the mandate.
Oversing’s state is broader than an access-control table: strategy, organization, people, skills, customers, contracts, work, resources, accounting, and history supply the context in which an action has consequences.
7. Retention and refinement
The Decidability Record retains the exact claim, dependencies, sources, tests and execution artifacts, results, repairs, open conditions, and applicable limits. Oversing connects the record to authorization, action, and observed outcomes.
Reviewed cases improve RDL, protocols, compiler behavior, and evaluations. The immediate path is more precise and economical control of existing models. Specialized training, attention refinements, and new learned representations are further engineering paths, not automatic effects of storing an audit.
8. Evaluate the whole chain
Test representation fidelity, missing-test discovery, actual execution, false closure, unnecessary rejection, repair quality, unauthorized-action denial, and total cost. Compare against strong prompting, retrieval, model critique, tool use, and formal verification where applicable.
The mechanism is described in full in Constructibility from First Principles. The system boundary is developed in From Language to Institutional Action.
