Anymal OSDraftv0.1
SHED · INCEPTION REFERENCE

Joint procurement + sustainability shed scorer

A second lens on the same substrate as /enterprise/pilots/procurement: score a sub-jurisdictional supply shed (per GHG Protocol LSRG) on margin + Scope 3 + water resilience + MRV maturity, simultaneously, with parcel-level evidence. Live working view at /shed.
INCEPTION REFERENCE
What a supply shed is (and why both Nestlé + Tyson care)

The supply shedis the formal GHG Protocol Land Sector and Removals Guidance (LSRG) term for the region serving a known first-collection point or processing facility. When per-supplier traceability is impossible (common in beef sourcing), Scope 3 inventories report at the shed level. Nestlé and Tyson are jointly defining a shed where the cattle Tyson processes for Nestlé's beef products simultaneously meet a multi-criteria threshold:

Architectural composition

Same Earth Layer substrate as the existing agents. This lens composes:

@anymal/cattle-agent
per-cohort carcass margin → shed margin rollup
@anymal/carbon-agent
methane intensity per kg beef + soil carbon stock
@anymal/water-agent
irrigation per parcel → drought resilience scoring
@anymal/soil-agent
SSURGO productivity + ecological-site forage potential
spine parcels + CDL
defines the candidate shed's parcel set
CERES Tag occupancy
per-parcel confirmed animal presence · the moat signal
Planned shed scorecard (preview)
MetricWho caresSource signalBuild state (at inception)
Predicted shed margin per headTyson procurementcattle-agent carcass-model over shed cohortssubstrate ready
Methane intensity per kg beefNestlé Scope 3carbon-agent enteric pathway + cattle-agent intakesubstrate ready
Soil carbon stock + sequestration potentialNestlé insettingcarbon-agent + SSURGO organic mattersubstrate ready
Regen-ag practice densityBoth (joint claim)irrigation + ecological-site condition + operator self-claim portalneeds new lens math
Drought / water resilienceBoth (supply reliability)water-agent + RAP forage outlookneeds roadmap signal
MRV maturity (% CERES-tagged operators)Nestlé audit defensibilityCERES Tag adoption per parcelneeds roadmap signal
Deforestation-free attestationBoth (EUDR + brand)CDL forest-loss time series within shed boundaryneeds roadmap signal
Supply volume sufficiencyTyson procurementhead-count estimate from CERES + parcel-level stockingneeds new lens math
Composite shed scoreJointweighted blend with adjustable sliders per stakeholderneeds new lens math
substrate ready = uses existing agents as-is · needs roadmap signal = depends on Rangeland Analysis Platform, real CERES API, or operator self-claim portal · needs new lens math = the shed-scorer composite logic itself
Post-inception update (2026-06-01): the "substrate ready" row covering soil-carbon headroom has shipped at /shed backed by /api/shed/score/counties. The other 8 rows still match this plan.
What the page will do, when fully built
  1. Input: a Tyson processing facility location + Nestlé's threshold requirements (regen-ag %, deforestation-free, head-count target, max-haul radius)
  2. Materialize the candidate shed: every TX/OK/NM parcel within the radius, by CDL + ownership + soil + water + CERES presence
  3. Run the 9 metrics in the scorecard above, per-parcel and rolled up to shed level
  4. Render a shed map colored by composite score, with two-stakeholder sliders (Tyson margin emphasis ↔ Nestlé Scope 3 emphasis)
  5. "Compare alternative sheds" · Amarillo vs Hereford vs Dalhart, which boundary scores best
  6. Export an audit-grade evidence packet (the shed equivalent of the diligence memo)
WHY THIS IS A SEPARATE LENS

The /enterprise/pilots/procurement page answers a SINGLE-stakeholder question (Tyson procurement: should I take this bid?). The supply-shed scorer answers a TWO-stakeholder question (Nestlé sustainability + Tyson procurement, jointly: which geographic boundary do we both want to source from this contract year?). Different audience, different decision moment, different commercial cycle, same substrate. Building it as a separate lens keeps each surface focused.

Inception reference · development artifact, not a customer surface. Live working view at /shed.