-
Notifications
You must be signed in to change notification settings - Fork 0
Define project units and geometry tolerances in RFC 0003 #12
Copy link
Copy link
Open
Labels
ai-readyPortable work packet ready for human-and-AI implementationPortable work packet ready for human-and-AI implementationarea:geometryGeometry contracts, kernels, topology, and tolerancesGeometry contracts, kernels, topology, and tolerancesarea:modelSemantic BIM model and validationSemantic BIM model and validationhelp wantedExtra attention is neededExtra attention is neededkind:rfcArchitectural decision proposalArchitectural decision proposalreview:bimBIM or VDC domain review requestedBIM or VDC domain review requestedreview:geometryCAD geometry or topology review requestedCAD geometry or topology review requestedreview:rustRust API or implementation review requestedRust API or implementation review requestedsize:sOne narrow crate sliceOne narrow crate slicestate:readyReady for a contributor to claimReady for a contributor to claim
Description
Metadata
Metadata
Assignees
Labels
ai-readyPortable work packet ready for human-and-AI implementationPortable work packet ready for human-and-AI implementationarea:geometryGeometry contracts, kernels, topology, and tolerancesGeometry contracts, kernels, topology, and tolerancesarea:modelSemantic BIM model and validationSemantic BIM model and validationhelp wantedExtra attention is neededExtra attention is neededkind:rfcArchitectural decision proposalArchitectural decision proposalreview:bimBIM or VDC domain review requestedBIM or VDC domain review requestedreview:geometryCAD geometry or topology review requestedCAD geometry or topology review requestedreview:rustRust API or implementation review requestedRust API or implementation review requestedsize:sOne narrow crate sliceOne narrow crate slicestate:readyReady for a contributor to claimReady for a contributor to claim
Outcome
Produce RFC 0003 defining the smallest project-wide units and tolerance policy needed for authored BIM parameters, kernel operations, fixtures, persistence, and IFC exchange.
Truth source
Use the existing metre-based
Point3,WallGeometry, Truck tolerance behavior, Wall Lab values, and primary IFC unit concepts. Clearly separate observed current behavior from proposed policy.Required questions
Invariants
IFC remains the semantic boundary; Truck remains replaceable; domain types must not depend on Truck constants.
Non-goals
Implementing unit conversion UI, surveying coordinate systems, georeferencing, or changing every numeric type.
Acceptance and evidence
cargo xtask verifypassDependencies: RFC 0001, RFC 0002, and #10.