Resources / Safety architecture
Safety Is Built into the Work
Examine the claim, govern its use, authorize the action, and preserve the means of correction.
In this article
- 1. What “intrinsic” means here
- 2. Four burdens before consequential reliance
- 3. Truth and alignment have different functions
- 4. Protect inquiry and govern use
- 5. The separation of powers
- 6. Record distinct states, not one safety score
- 7. Test the boundary, including failure
- 8. Preserve the means of correction
Safety belongs in the representation, examination, authority, and execution of institutional work. It cannot be reduced to the tone of an answer or to whether the answer agrees with a preferred viewpoint.
Runcible examines claims through constructive falsification. Oversing governs decisions and authorized action. Their combined architecture keeps facts, interests, permissions, and consequences visible so that a plausible recommendation cannot silently become an institutional commitment.
1. What “intrinsic” means here
Safety is intrinsic to the architecture when its controls are part of how work proceeds: the claim must be represented, its material conditions examined, its limits recorded, and its proposed use authorized. They are not merely a final instruction to sound cautious.
This is a design principle and an engineering obligation. It does not mean that software abolishes error or that an audit record guarantees a safe outcome. The relevant controls must be implemented, tested under adversarial conditions, and maintained as the institution and its environment change.
2. Four burdens before consequential reliance
Possibility
The examination identifies the actors, objects, operations, resources, dependencies, and sequence the proposal requires. An elegant recommendation can fail because a prerequisite is unavailable, the timing is impossible, or a claimed transformation cannot occur under the stated conditions.
Constructing these relations is a means of falsification. A failed necessary condition defeats that construction. An unknown condition remains unresolved; it must not be silently filled with a convenient assumption.
Ethics and reciprocity
The examination identifies demonstrated interests, prior commitments, information, consent where required, costs, risks, and externalities. It asks whether the proposed benefit depends on deception, an unauthorized imposition, or an unaccounted transfer to another party.
A legitimate objective may survive while its proposed means fail. Constructive settlement examines alternative terms, compensation, sequencing, or scope that can preserve the objective and repair the imposition.
Truth and testifiability
The examination binds claims to evidence, distinguishes observation from inference, challenges causal relations, and preserves scope and uncertainty. A conclusion survives only within the conditions the examination supports.
Unpleasantness is not falsification. Agreement is not proof. An authentic source can still be misinterpreted, and multiple sources can repeat a common error. The relevant question is what the evidence and tests actually establish.
Warrantability and liability
The examination identifies the reliance being proposed, the responsible party, material risks, limits, and means of correction or remedy. An organization should be able to state what it is prepared to stand behind and what remains outside that undertaking.
The software supports this account; it does not become the legal bearer of a corporation’s duties simply by producing a verdict. Legal responsibility depends on the applicable facts, agreements, institutions, and law.
3. Truth and alignment have different functions
Runcible separates the examination of factual claims from contextual goals and norms. Legal, cultural, class, sex-related, organizational, and individual assumptions can shape a request or its use. Where material, they should be made explicit and examined rather than hidden inside a universal “aligned” label.
Communication can adapt to a reader’s expertise, role, language, and circumstances. Decisions can reflect legitimate institutional objectives. Neither should rewrite the underlying evidence status. A restricted disclosure is not a false statement; an approved objective is not an established causal mechanism.
Alignment is therefore broader than manners alone. It includes the goals and constraints a responsible institution chooses within its legitimate authority. The point of separation is to make those choices attributable.
4. Protect inquiry and govern use
A claim may require careful examination because it concerns conflict, protected information, or differences among groups. The method must preserve the unit of analysis, evidence quality, causal limits, and conditions of use.
A population pattern does not determine an individual’s properties. A factual description does not authorize an action against a person. A proposed explanation does not establish a motive. Those transitions each require additional grounds.
Privacy, data access, security, and harmful-use constraints also operate during inquiry. They cannot be postponed until after information has been obtained or disclosed. Separating truth from use means identifying the boundary at which each control belongs, not exempting internal analysis from every constraint.
5. The separation of powers
The generating model and Runcible produce and examine candidate work. Oversing supplies the institutional context and governs decision and authorization. A separate executing model or tool receives the permitted mandate.
Oversing’s context includes strategy, organizational structure, people and skills, customers, contracts, work, resources, budgets, accounting, and history. A permission is therefore related to a real role, object, procedure, and consequence rather than a free-standing sentence in a prompt.
- Human validation: Consequential decisions default to validation by the responsible person unless an explicit delegation governs them.
- Bounded delegation: The mandate identifies the allowed operation, scope, resources, conditions, and escalation requirements.
- Separate execution: The generating model cannot grant itself authority or expand the executor’s mandate.
- Continuing control: Changed evidence, permissions, or conditions can block, revoke, or reopen the action.
The security of this boundary depends on enforcement outside the generating model and on the behavior of every connected tool and integration. A diagram alone does not establish that no path can bypass it.
6. Record distinct states, not one safety score
| State to retain | Example | Why it matters |
|---|---|---|
| Evidence status | Supported within scope; contradicted; unresolved. | Missing evidence must not be confused with falsity. |
| Possibility status | Feasible under specified conditions; defeated prerequisite; incomplete construction. | A coherent story is not necessarily performable. |
| Obligation and reciprocity status | Obligations satisfied; imposed cost identified; settlement required. | A local benefit can conceal costs elsewhere. |
| Reliance limits | Suitable for exploration; qualified for a bounded decision; additional review required. | The same information supports different uses differently. |
| Authorization status | Approved within mandate; blocked; escalated; revoked. | A finding does not grant authority. |
| Disclosure status | Permitted recipient and purpose; restricted publication. | Truth and access rights are separate questions. |
These are conceptual distinctions for the record and workflow. Exact field names and states belong to the applicable implementation and output contract.
7. Test the boundary, including failure
Useful evaluation presents missing evidence, altered sources, contradictory rules, unauthorized requests, prompt injection, revoked permissions, and attempts to enlarge a delegated task. Inspect both the disposition and the actual execution artifacts.
The system should also face cases where abstention would be excessive. A control that blocks every useful action is not an adequate commercial solution. Measure false closure, unnecessary rejection, escalation quality, recovery, and total operating cost together.
Model-based judgments can vary. Deterministic authorization controls should enforce the mandate despite that variation. The evaluation must show where each kind of control operates and how failures are detected.
8. Preserve the means of correction
The Decidability Record retains the examined claim, evidence, tests, defects, repairs, open conditions, and limits. Oversing connects it to the responsible decision, action, and consequence. Later evidence can challenge the conclusion without erasing the earlier record.
Reviewed corrections improve protocols, RDL, compiler behavior, and evaluation. Customer-private cases retain their permissions and reuse boundaries. Learning should make the control system more reliable; it must not silently change the authority under which the institution operates.
The governing principle is to examine what can be responsibly concluded, authorize what may be done, and preserve what happened. Safety comes from maintaining those distinctions throughout real work.
