Add joiner_timber truss fitting rules - #19
Open
waywardmonkeys wants to merge 1 commit into
Open
Conversation
waywardmonkeys
force-pushed
the
worktree-joiner-timber-rules
branch
3 times, most recently
from
August 30, 2026 06:16
7e9f711 to
804eab1
Compare
Introduce the `no_std` `exedra_measurements` core with exact linear and angular values. Distinguish positive `Length` from signed `Offset`, and nonnegative `Angle` from signed `AngularOffset`; retain joto iotas and microarcseconds until an explicit geometry lowering boundary. Build the `joiner_timber` rule library with typed fit allowances and participant-role resolution. Model housed heels, a keyed king-post through-tenon that makes the tie tension path explicit, full-section strut bearings, and paired rafter-head bearings. Represent every physical rule dimension and clearance as an exact `Length`, then lower each parameter family together when recipe construction needs meters. Keep runtime finite checks only for values derived from floating-point extents, frames, and intersections. Derive both sides of every fit from one carried-member section, apply clearance only to receivers, reject insufficient relish and incoherent setout, and exercise every rule through deterministic constructive evaluation. Keep the keyed slot line-to-line between its load-bearing faces so the generated rectangular key realizes the contacts the construction graph claims. Make emitted `RuleOutput`s read as joint contracts: name edits by their physical effect, contacts by their bearing role, generated pieces by purpose, and transfers by load direction. Retain prose where the tie-to-key-to-post suspension invariant cannot be expressed by the generic output types alone. Record the upper strut bearing without a directed transfer because it closes the truss internal force triangle; the acyclic `joiner` support explanation is not a statics model. Update `joiner` ADR 0001 now that interacting n-ary cutters are an `exedra` regression contract rather than a downstream limitation.
waywardmonkeys
force-pushed
the
worktree-joiner-timber-rules
branch
from
August 30, 2026 07:03
804eab1 to
25c53f1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce the
no_stdexedra_measurementscore with exact linear and angular values. Distinguish positiveLengthfrom signedOffset, and nonnegativeAnglefrom signedAngularOffset; retain joto iotas and microarcseconds until an explicit geometry lowering boundary.Build the
joiner_timberrule library with typed fit allowances and participant-role resolution. Model housed heels, a keyed king-post through-tenon that makes the tie tension path explicit, full-section strut bearings, and paired rafter-head bearings.Represent every physical rule dimension and clearance as an exact
Length, then lower each parameter family together when recipe construction needs meters. Keep runtime finite checks only for values derived from floating-point extents, frames, and intersections.Derive both sides of every fit from one carried-member section, apply clearance only to receivers, reject insufficient relish and incoherent setout, and exercise every rule through deterministic constructive evaluation. Keep the keyed slot line-to-line between its load-bearing faces so the generated rectangular key realizes the contacts the construction graph claims.
Make emitted
RuleOutputs read as joint contracts: name edits by their physical effect, contacts by their bearing role, generated pieces by purpose, and transfers by load direction. Retain prose where the tie-to-key-to-post suspension invariant cannot be expressed by the generic output types alone.Record the upper strut bearing without a directed transfer because it closes the truss internal force triangle; the acyclic
joinersupport explanation is not a statics model. UpdatejoinerADR 0001 now that interacting n-ary cutters are anexedraregression contract rather than a downstream limitation.