42. Exact cutting-tool and fixture lifecycle
Govern tool-crib custody, finite life, preset, inspection/regrind and immutable fixture composition by extending existing exact Manufacturing resource, physical identity, calibration, capacity and stock-ledger truth.
Purpose
Govern tool-crib custody, finite life, preset, inspection/regrind and immutable fixture composition by extending existing exact Manufacturing resource, physical identity, calibration, capacity and stock-ledger truth.
Manufacturing Engineer, different Production Manager, Production Planner, different Production Supervisor, Stores Officer, exact named Production Operator, different Quality Inspector and read-only Auditor
MTC-… cutting tool + MFC-… fixture v1 released → MDP-… pins exact versions/calendars → MTP-… preset → checkout → operation life event → return → MTS-… inspection/regrind → independent Quality release.
Before you begin
- Each tool/fixture already exists as one active approved TOOL or EQUIPMENT resource bound to one active serialized physical instance
- That exact identity exists as exactly one whole unrestricted stock unit in one same-site/classification crib
- Any required calibration remains valid through the existing Calibration authority
- Exact capacity calendars are active and approved
- CLEAN controlled evidence and distinct author/release/service/inspection users are available
Exact identity, custody and service boundaries
Registration extends—not creates or replaces—the current approved resource version, active physical instance, canonical serial, item identity and current-stock row. One resource/physical identity can have only one tooling control.
Crib, life metric/limit, warning, inspection interval, regrind ceiling, preset requirement and note form one SHA-256 version. The author submits and a different Production Manager approves/rejects.
A released fixture freezes ordered exact component controls, control/resource versions, single-unit capacity calendars, roles, positions, setup values and tolerances. An open dispatch pin prevents replacement.
A fresh readiness dispatch freezes control and optional fixture-configuration fingerprints. Each fixture component becomes an additional exact finite capacity load; legacy unmanaged tooling retains the established path.
When required, Stores records immutable named values/units and CLEAN evidence against the exact released dispatch and pinned control version before checkout.
Checkout and return move the same serialized unit through paired TOOLING_* ledger entries. The bundle remains tied to one dispatch, location and named operator; total quantity stays one per identity.
Operation execution consumes USES, MINUTES or CYCLES for each pin. A life limit or inspection interval blocks the exact stock in place. Inspection/regrind is recorded only in crib and a different Quality Inspector decides release.
Flow 38 exposes no arbitrary URL, executable content, callback, machine command, tenant JavaScript, SQL, generic workflow/template administration or alternate identity. It does not create item/resource/physical identity/quantity, calibration, maintenance, Assembly, receipt, material issue, payroll or accounting records.
Procedure
- 1
Verify the exact approved resource, active physical identity, canonical serial, one-unit unrestricted crib stock and any current calibration/capacity evidence.
- 2
Create control v1 with exact life/inspection/preset/crib values and CLEAN evidence; submit and release as different named users.
- 3
If it is a fixture, create and independently release its ordered exact component configuration with approved resource/calendar pins.
- 4
Plan and independently release a fresh dispatch; verify every tooling snapshot/fingerprint and finite resource load.
- 5
Record any required preset, then check out the exact bundle as Stores Officer. Complete the instruction gate and established operation as the assigned operator; inspect attributable life events and any automatic block.
- 6
Return to crib, record an inspection or permitted cutting-tool regrind, obtain independent Quality review, and reconcile total quantity, exact physical identities, ledger pairs, custody events, capacity loads, audit/outbox and unchanged unrelated-domain witnesses.
Expected result
- Definitions retain immutable rejected/replacement versions and independent release
- Fixture versions pin unique exact identities, current approved resource versions and active single-unit calendars
- Fresh dispatches freeze exact tooling/configuration fingerprints and finite component loads
- Required preset evidence fails closed before checkout
- Checkout/return produces paired append-only movements with zero net quantity change
- Only the exact assigned operator's established execution consumes life
- Life/inspection due state explicitly blocks rather than labels tooling serviceable
- Service/regrind evidence requires separate Quality review before release
- Site, clearance and classification filters apply to reads and transitions
- No alternate identity, hidden stock, generic workflow, executable or machine-control surface exists