# Environmental Knowledge Program — a regulatory DOMAIN, not an ISO-14001 project. # Machine-readable program definition consumed by the reference suite to track progress. # LAW-FIRST: Umweltrecht -> Obligations -> Capabilities -> ISO 14001 -> Delta (never the reverse). id: PROG-environmental name: "Environmental Knowledge Program" customer_question: "Welche Umweltanforderungen gelten für mein Produkt (z. B. Industriespülmaschine)?" status: started # planned | started | in_progress | complete principle: > ISO 14001 ist KEIN Umweltrecht, sondern ein Managementsystem. Wir starten beim Recht und fragen erst danach, welche vorhandenen Managementsysteme davon wahrscheinlich schon etwas abdecken. # the reusable production line, instantiated for this domain blueprint: [corpus, obligations, capabilities, transition_patterns, playbooks, reference_scenarios, completeness] stages: - id: B1 name: "Environmental Regulatory Corpus" owner: "Legal Knowledge / Obligation Registry" status: open # handed off — not built here note: "Zunächst NUR Rechtsquellen + Pflichten (noch keine ISO, keine Capabilities)." areas: # the six environmental obligation areas the customer actually faces - water # Wasser / Abwasser - chemicals # Chemikalien (REACH/CLP) - emissions # Emissionen - energy # Energie - waste # Abfall - product_responsibility # Produktverantwortung - id: B2 name: "Environmental Capability Model" owner: "Compliance Execution" status: open # depends on B1; Registry grows here depends_on: [B1] capabilities: - chemical_management - wastewater_management - emissions_monitoring - hazardous_substance_management - energy_data_capture - environmental_incident_management - id: B3 name: "Transition Patterns (ISO 14001 -> Environmental Corpus)" owner: "Reasoning (Knowledge Acquisition)" status: blocked # LAST — only once both sides (corpus + capabilities) are known depends_on: [B1, B2] note: "Erst jetzt sinnvoll: ISO 14001 als Quellzustand gegen den Umwelt-Korpus (User: law-first)." # once B1-B3 land these extend AUTOMATICALLY via the existing engines (no new runtime architecture) downstream_auto: [playbooks, reference_scenarios, optimization, scope, capability_delta, completeness] acceptance: > Regulatory Completeness kippt `Environmental` von unsupported/open auf assessed; die sechs Bereiche sind als Obligations + Capabilities im validierten Korpus, das ISO-14001-Delta als Transition Pattern. Messbar an der Reference Suite (Environmental-Zelle UNSUPPORTED -> PASS).