Kick-off: K-factor table (3O1) from the shop's STEP + corrected DXF pairs. Off-server git (3O2) first.
- ruling3D keeps its own number sequences: 3O (open items), 3DV (deviations)
Aristide 2026-11-11, option (a): prefixed so 3D never collides with the DEV/SPEED shared O sequence. Claim with pinlist/onum.py, never by hand.
- rulingWork the same way as DEV and SPEED
Aristide 2026-11-11: pin list (record/ruling/intent/question), numbered open items, DV for every deviation/error/sidestep, record moves in the same commit as the code (commit-msg gate).
- rulingPart of the code is C; we also do mm
Aristide 2026-11-11. Python geometry, C only for measured hot spots (2D pattern: *_native.c -> .so). Units: keep the file's native unit, every value carries its unit, convert only at the edges; table rows record the unit they were entered in.
- rulingK-factor is a table variable (inherited from 2D)
Jordan 2026-08-31: 'K-factor will have to be a variable on the table since it will vary by material and possibly by customer.' Per-row column with provenance; missing K raises, never a silent fallback. Same format as 2D materials.json.
- recordPin list is hosted at km3d-pins.jrlindsay.mycloudally.com
Aristide 2026-11-11 asked for a web address. Published with mca-host from pinlist/ (static). Regenerate with build_pins.py; the site updates instantly.
- record riskyPlatform auto-save commits into this repo
Seen 2026-11-11 (5e7b382): the platform's end-of-turn auto-save commits here. A km3d/ change left uncommitted would hit the record gate. Rule: I commit my own work, with its pin, before every turn ends, so auto-save never carries code.