When meaning is load-bearing
An engineer gives an AI reviewer a failed test, a proposed change and permission to inspect the supplied material and return a repair proposal. The failure challenges one specific claim about the change. Applying a repair requires separate authorization.
As the evidence becomes a reading, a review state and a handoff to another participant, that relation must remain operative. The recipient needs to see which claim is challenged, by which observation, what remains unresolved and which actions are permitted. A handoff such as “review complete; fix ready” can lose those distinctions while retaining a source link.
The required meaning must reach a form the recipient can inspect and use. The authority to act must be checked at each crossing. A supported finding and a valid grant answer separate questions.
I use “load-bearing” as a local, counterfactual test: fix the setting and the recipient's requirements, then remove or change a relation and observe the result. An observed difference makes the relation a candidate; the checks below establish whether it carries the required consequence through to the receiving system.
Tendora applies this test to each variable of a statement in its corpus fidelity check; Load-bearing as situated meaning documents the formalization below and how Tendora implements it.
Importance, repetition, source-grounding and graph degree do not earn the hard hat.
Open the inspection hatch: working formalization and measurement states
Select a semantic relation
where
The assessment frame shares
Changing a coordinate of
Let
The paired comparison holds
Let
The disjoint union keeps openings distinct from ordinary outcomes. Before the trials, the receiving owner fixes the comparison relation
Where the observations are defined, write
The candidate criterion is
Validity requires defined, independently captured observations, pinned input and intervention identities, an applicable comparison and retained trial records. A prediction specifies a test; measured participation requires the observations.
A candidate earns carriage only when independent checks establish:
- Required influence: each required trial satisfies
, including the direction or distinction required by . - Presentation invariance: irrelevant presentation changes preserve the required observable under
. - No hidden fallback: removing the connection that makes the required relation operative exposes the designated opening.
- Traceability: the result can be traced downward to source, selected asset, checked translation into executable form and evidence, and upward through the receiving projection to its consequence in the current system.
- Materialization: the required invariant is realized in a compatible receiving document span, asset field, program, state or projection.
The category set
- carried: the required influence survives the crossing and the carriage checks pass;
- coupled but misaligned: observed influence violates the consequence or distinction required by
; - cooled: adequate discriminating trials show that a retained declaration lacks the required operative influence within
; - unresolved: observations, counterfactuals, comparison or receiving realization are insufficient; and
- outside scope: the receiving owner's declared exclusion and independent scope check establish that
does not require the distinction.
Let
Failed checks and open obligations remain visible alongside the category. Each finding is scoped to the selected relation, locus, encounter, test domain and receiving promise.
Worked example: from failed check to review handoff
Consider one frozen software revision and a completed test of a selected claim. The review contract treats the captured failure as a reason to reconsider that claim within the test's stated scope. The capture, limitations and alternative explanations remain available. The reviewer may inspect the supplied material and return a candidate repair; applying it requires a separate grant.
This is an illustrative test design. Its expected outcomes do not establish measured carriage.
| Coordinates | Declaration |
|---|---|
| Body | One review body, at the grain of one claim; the place where the failure is made operative in the review state. |
| Role | The receiving reviewer; projection of that state into a handoff the reviewer can inspect. |
| Purpose | Make a bounded review contribution available for judgment; captured result → attributed reading → review state → handoff. |
| Baseline | The frozen software revision, claim, test capture, review contract and scoped grant; no repair has been applied. |
| Promise | The recipient can identify the claim's reason for reconsideration, its evidence and limits, any missing connection and the permitted operations; observe those fields in the actual handoff. |
| Degrees of freedom | The declared intervention on the governing relation and presentation controls; the result is admitted only as evidence from this captured test. |
Let
Use
The receiving owner fixes these expectations before the trials:
| Trial | Required observable in the handoff |
|---|---|
| With | The failure contributes an attributed reason to reconsider the selected claim; its scope and unresolved questions remain visible. |
| With | An explicit opening identifies the missing connection between the relation and the review state; retaining the source text alone cannot supply the review finding. |
| Presentation-only change | The same review finding, limits, openings and permitted operations. |
The explicit opening is an observable result in
Authority has its own checks. The grant to inspect and propose must not authorize applying a repair, even when the finding is supported or the proposal appears convincing. Expiry or revocation stops further use of the affected permission; it does not erase the earlier evidence. Access to that evidence is checked separately. A new grant or observation changes the relevant assessment frame and requires reassessment rather than rewriting the earlier finding.
Where the phrase came from
After I pointed out the phrase “load-bearing”, a model replied:
“Yes—the phrase is plausibly a compressed residual of that repeated
architectural pressure: don’t hang the upper layer before the lower boundary
can carry it. Not copied from one line, but reinforced until it became an easy
linguistic attractor. Nice catch ;-p”
The phrase stuck.
This page is the essay's home. It first appeared in the README of mirzahusadzic/mirzahusadzic (revision 3be3efb). Text © 2026 Mirza Husadzic, licensed under CC BY 4.0 (full text in LICENSES/CC-BY-4.0.txt). Separately attributed material retains its own terms.