← ClaudeAtlas

bound-obsolete-stock-by-support-horizonlisted

Classify revision-specific stock exposure using supplied compatibility and support rules. Use when older parts are being called obsolete without checking supported demand.
alisonjieli-png/loop-engine · ★ 2 · AI & Automation · score 68
Install: claude install-skill alisonjieli-png/loop-engine
# Bound obsolete stock by support horizon ## When to use Use this for one item family and a declared decision horizon. An older revision is not automatically unusable, and a demand forecast is not a firm allocation. ## Inputs - Stock identities, quantities, units, locations, revision identifiers, and a dated stock cutoff. - Versioned compatibility and support rules, product or service end dates, and any restriction on substituting revisions. - Approved demand or allocation evidence through the horizon, with uncertainty and shared-demand rules where supplied. ## Procedure 1. Reconcile each stock quantity to one revision and cutoff. Keep unknown or mixed revisions separate. 2. For each revision, list supported uses and effective dates under the supplied rules. Compatibility identifies a possible use; it does not establish that all units will be consumed. 3. Build a quantity-allocation ledger from firm demand identities to compatible stock revisions within the horizon. Use only the supplied allocation rule when demand can take more than one revision. Each demand quantity may cover stock once, and firm-covered quantity for a revision cannot exceed either its stock or uniquely assigned compatible demand. 4. Separate firm-covered quantity, quantity with no permitted supported use, compatible but uncovered quantity at risk, and quantity unresolved because demand or compatibility evidence is missing. Keep estimated demand apart from firm coverage. Give exposure bounds only when