Truth First. Reciprocity Always. Alignment After.
TL/DR;
Safety is intrinsic to Runcible because safety is not treated as tone, ideology, comfort, or brand preference. It is calculated through universal tests of truth, reciprocity, possibility, and liability before any output is adapted for a user, institution, audience, or brand.
Runcible separates safety from alignment. Safety determines whether a claim or action is true, reciprocal, possible, and within liability. Alignment determines how a surviving output should be presented: with what tone, context, detail, restraint, or institutional framing.
This distinction prevents two common AI failures: suppressing difficult truths in the name of safety, and stating truths irresponsibly without scope, reciprocity, or liability. Runcible discovers first, decides second, and aligns third.
The result is not a universal ideological constraint on all users. It is a governed system in which truth is tested, irreciprocity is prohibited, impossibility is blocked, liability is bounded, and presentation is adapted only after the underlying claim or action has survived adjudication.
In short: Runcible makes AI safe by making claims decidable before making them polite.
1. Truth
Truth asks:
Does the claim survive testifiability within its stated scope?
Runcible tests:
- referents,
- terms,
- evidence,
- operations,
- scale,
- correspondence,
- contradictions,
- missing facts,
- falsifiers,
- stated limits,
- unresolved dependencies.
A claim is not made safe by making it pleasant.
A claim is not made unsafe by making it unpleasant.
A claim is unsafe when it is false, misleading, unsupported, overgeneralized, unbounded, or presented with more warrant than it has earned.
Truth is the first safety condition because falsehood produces downstream harm: bad decisions, false confidence, misplaced responsibility, institutional error, and unaccounted liability.
2. Reciprocity
Reciprocity asks:
Does the claim or action impose costs, risks, obligations, deceptions, or externalities on others without warrant?
Runcible does not tolerate irreciprocity.
That means it does not authorize:
- fraud,
- deception,
- coercion,
- exploitation,
- theft,
- concealment of relevant risk,
- externalization of costs,
- unauthorized imposition,
- misuse of authority,
- breach of obligation,
- liability dumping,
- or action against demonstrated interests without reciprocal warrant.
This is where Runcible’s safety differs from conventional alignment.
Alignment often asks:
Will this offend?
Runcible asks:
Does this impose?
Does this deceive?
Does this violate demonstrated interests?
Does this evade responsibility?
Does this create unbounded liability?
Does this authorize an irreciprocal action?
Safety is therefore ethical in the operational sense: it prevents actions and claims that impose asymmetric costs without warrant.
3. Possibility
Possibility asks:
Can the proposed action actually be performed under current conditions?
An output may be true and reciprocal but still unsafe if it recommends an impossible, unavailable, or operationally incoherent action.
Runcible tests:
- actor,
- operation,
- resources,
- permissions,
- dependencies,
- sequence,
- implementation path,
- available evidence,
- available authority,
- institutional capacity.
A recommendation that cannot be executed safely is not action-ready.
A claim that cannot be operationally reduced is not warrantable.
Possibility prevents AI from producing elegant impossibilities.
4. Liability
Liability asks:
Can responsibility be assigned and bounded?
This is the institutional safety test.
Runcible asks:
- Who acts?
- Under what authority?
- On what evidence?
- Under what rule?
- With what residual risk?
- Who bears responsibility?
- Can the decision be reviewed?
- Can it be audited?
- Can it be defended?
- What remains unresolved?
- What must be escalated?
If responsibility cannot be assigned, the action cannot be authorized.
If risk cannot be bounded, the output cannot be warrantable.
If auditability is absent, the institution should not treat the output as action-ready.
This is why Runcible produces Decidability Records rather than mere answers.
1. Is the claim true within its stated scope?
What is the population?
What is the measure?
What is the variance?
What is the distribution?
What is the causal mechanism?
What is the confidence?
What are the limits?
2. Is the use reciprocal and permissible?
Does the claim justify an action?
Does that action impose costs?
Is the action lawful, reciprocal, and within authority?
Does the action violate demonstrated interests?
Does it treat individuals only as category members where individual adjudication is required?
3. How should the output be aligned?
Should the truth be stated directly?
Should it be contextualized?
Should uncertainty be emphasized?
Should group-level and individual-level claims be separated?
Should the answer be scoped to policy, science, law, or private reasoning?
Should the response be withheld from public output but retained for internal review?
This is how Runcible handles sensitive truths.
Not by denying reality.
Not by weaponizing reality.
But by testing claims first, then governing use, then aligning presentation.
1. Generate Candidate Meaning
The model may supply a hypothesis, explanation, summary, classification, or proposed action.
This is semantic supply.
2. Translate Into Testable Form
RDL converts candidate meaning into typed operational claims.
The system binds terms, referents, scale, scope, operation, evidence requirements, falsifiers, authority, and liability boundary.
3. Test Truth
Does the claim survive evidence, correspondence, scope, and falsification?
4. Test Reciprocity
Does the claim or action impose, deceive, exploit, coerce, externalize, or evade responsibility?
5. Test Possibility
Can the action be executed under current conditions?
6. Test Liability
Can authority and responsibility be assigned and bounded?
7. Assign Action State
The result may be:
- warrantable,
- non-warrantable,
- authorized,
- blocked,
- escalate,
- undecidable,
- requires evidence,
- requires authority,
- requires legal review,
- requires policy clarification,
- restricted for public output,
- safe for internal analysis,
- safe for publication after alignment.
8. Produce Decidability Record
The Decidability Record preserves:
- claim,
- evidence,
- rules,
- tests,
- failures,
- repairs,
- unresolved conditions,
- action state,
- warrantability status,
- liability boundary,
- alignment protocol applied,
- and publication constraints.
9. Apply Alignment
Only after adjudication does Runcible couch the output for:
- user,
- institution,
- role,
- domain,
- context,
- emotional load,
- brand,
- public/private channel,
- legal or policy boundary.
The output is aligned.
The truth-status is not rewritten.
Truth-Safe
The claim is sufficiently supported within stated scope.
Truth-Unsafe
The claim is false, unsupported, misleading, ambiguous, or over-warranted.
Reciprocity-Safe
The claim or action does not impose unauthorized cost, deception, coercion, exploitation, or externality.
Reciprocity-Unsafe
The claim or action enables irreciprocity.
Possibility-Safe
The action is operationally executable.
Possibility-Unsafe
The action is impossible, incoherent, unavailable, or lacks required dependencies.
Liability-Safe
Authority and responsibility can be assigned and bounded.
Liability-Unsafe
Responsibility is unclear, risk is unbounded, authority is absent, or auditability is insufficient.
Alignment-Safe
The output can be presented to the user in the current context without unnecessary confusion, escalation, humiliation, or misuse.
Publication-Safe
The output can be publicly or commercially presented under provider, institutional, legal, or channel constraints.
These states should be separate.
A claim can be true but not publication-safe.
A claim can be true but require careful alignment.
A claim can be useful but non-warrantable.
A claim can be private-analysis-safe but public-output-restricted.
A claim can be permitted for internal review but not authorized for action.
This is why Runcible provides records, not merely responses.
Failure 1 — Brutal Truth Without Responsibility
This occurs when truth is stated without scope, authority, consequence, or liability.
Runcible prevents this by requiring reciprocity, possibility, and liability tests.
Failure 2 — Polite Falsehood
This occurs when alignment suppresses or distorts truth to preserve comfort, ideology, or brand safety.
Runcible prevents this by separating truth-status from presentation protocol.
Both failures are unsafe.
Runcible rejects both.
Closing on Safety
Safety is intrinsic to Runcible because Runcible does not treat safety as a tone layer.
It treats safety as the result of decidable constraints on claims and actions.
A claim must be true within stated scope.
An action must be reciprocal.
A recommendation must be possible.
A decision must remain within authority and liability.
Only then does alignment decide how the output should be presented to this user, institution, audience, or publication context.
That is why Runcible does not confuse safety with alignment.
Safety is adjudication.
Alignment is manners, context, role, and presentation.
Truth comes first.
Reciprocity is never optional.
Possibility prevents fantasy.
Liability prevents irresponsible action.
Alignment couches what survives.
That is how Runcible makes AI safe enough for institutional use without turning safety into ideology, evasion, or brand theater.
See the Decidability Record
View the Technical Architecture
Request Investor Brief