# © GreenSeal, Lda. — https://greenseal.dev
# SPDX-License-Identifier: CC-BY-4.0
version: 1.0.1
# 'levels' is REQUIRED on every requirement — the converter will error if it is missing.
# levels: [2]      → L2 audit only  (existing requirements)
# levels: [1, 2]   → appears in both L1 and L2 audit outputs
# levels: [1]      → L1 audit only
categories:
  - category: Governance & Culture
    requirements:
      - id: GSP-L2-GOV-01
        levels: [2]
        title: Organisational Awareness of Software Sustainability
        requirement: >
          The organisation shall promote internal awareness of software
          sustainability principles among relevant stakeholders.
        rationale: >
          Awareness is a foundational step toward adopting sustainable software
          practices and enabling organisational change.
        evidence_examples:
          - Internal presentations or training materials
          - Awareness campaigns
          - Sustainability onboarding content
          - Internal knowledge base or documentation
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2
      - id: GSP-L2-GOV-02
        levels: [2]
        title: Sustainability in Technical Decision-Making
        requirement: >
          The organisation shall consider sustainability aspects when making
          technical decisions related to software development and operation.
        rationale: Embedding sustainability into decision-making ensures environmental considerations influence system design and evolution.
        evidence_examples:
          - Architecture decision records (ADRs) referencing sustainability
          - Decision guidelines including sustainability criteria
          - Design review checklists
          - Trade-off analyses considering resource efficiency
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3
      - id: GSP-L2-GOV-03
        levels: [2]
        title: Developer Engagement in Resource-Efficient Practices
        requirement: >
          The organisation shall encourage developers and technical staff to
          actively consider resource efficiency as part of their everyday
          software development activities.
        rationale: >
          Embedding resource efficiency awareness at the individual developer
          level ensures sustainability considerations are applied consistently
          throughout the development lifecycle, not only at formal decision points.
        evidence_examples:
          - Code review checklists including resource efficiency criteria
          - Internal communities of practice focused on green software
          - Team or department-level efficiency goals
          - Recognition programmes or incentives for sustainability contributions
          - Developer guidelines referencing efficiency expectations
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2
      - id: GSP-L2-GOV-04
        levels: [2]
        title: Communication of Sustainability Goals
        requirement: >
          The organisation shall communicate sustainability-related
          goals or ambitions internally.
        rationale: >
          Clear communication aligns teams and supports
          coordinated sustainability efforts.
        evidence_examples:
          - Internal sustainability strategy
          - Company OKRs or KPIs including sustainability
          - Internal newsletters or announcements
          - Roadmaps including sustainability objectives
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2
      - id: GSP-L2-GOV-05
        levels: [2]
        title: Assigned Responsibility for Software Sustainability
        requirement: >
          The organisation shall assign responsibility for promoting or
          coordinating software sustainability initiatives.
        rationale: >
          Defined accountability increases effectiveness and continuity
          of sustainability efforts.
        evidence_examples:
          - Role descriptions
          - Sustainability working group or committee
          - Named sustainability champion
          - Governance structure diagrams
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-GOV-06
        levels: [2]
        title: Sustainability Requirements at Project Inception
        requirement: >
          The organisation shall define sustainability requirements and/or
          environmental KPIs for digital services at project inception, prior
          to or during the requirements gathering phase.
        rationale: >
          Defining environmental targets before a service is scoped ensures
          sustainability is treated as a first-class requirement rather than
          a post-hoc consideration. This aligns with the requirements gathering
          phase of ISO/IEC TS 20125-1:2026 and prevents lock-in to
          resource-intensive design paths.
        evidence_examples:
          - Project briefs or charters including sustainability criteria
          - Requirements documents with environmental acceptance criteria
          - Environmental KPI baselines defined before build starts
          - Sprint zero artefacts referencing sustainability targets
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2
        ts_alignment: "ISO/IEC TS 20125-1:2026 – Requirements gathering phase"

      - id: GSP-L2-GOV-07
        levels: [2]
        title: Decommissioning Responsibility
        requirement: >
          The organisation shall assign responsibility for planning and executing
          the responsible decommissioning of digital services, including data
          deletion, infrastructure shutdown, and hardware disposition.
        rationale: >
          Unplanned decommissioning results in residual resource consumption,
          orphaned data, and missed opportunities to reclaim infrastructure.
          Assigned responsibility ensures that end-of-life activities are
          planned, executed, and documented.
        evidence_examples:
          - Decommissioning plans or checklists
          - Named responsible role or team for end-of-life activities
          - End-of-life governance procedures or runbooks
          - Service retirement policies
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2
        ts_alignment: "ISO/IEC TS 20125-1:2026 – End of life phase"

  - category: Training & Knowledge
    completion_rules:
      minimum_total_score: 7
      minimum_core_requirements: 2
      allow_partial_credit: true
    requirements:
      - id: GSP-L2-TRN-01
        levels: [2]
        title: Formal Sustainability Training
        requirement: >
          The organisation shall provide structured training on green software
          and/or green AI practices to relevant roles.
        rationale: >
          Structured training ensures sustainability practices are understood
          and consistently applied across teams.
        evidence_examples:
          - Training curriculum or course materials
          - Training attendance records
          - Learning management system reports
          - Training schedules
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-TRN-02
        levels: [2]
        title: Sustainability Onboarding for Technical Roles
        requirement: >
          The organisation shall introduce new technical employees to documented
          resource-efficient software and AI development guidelines during onboarding.
        rationale: >
          Early exposure to sustainability practices increases long-term adoption
          and consistency in development practices.
        evidence_examples:
          - Onboarding documentation
          - Orientation training materials
          - Internal developer handbooks
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2

      - id: GSP-L2-TRN-03
        levels: [2]
        title: Sustainability Considerations in Recruitment
        requirement: >
          The organisation shall consider sustainability-related software or AI
          development skills or awareness during recruitment processes for relevant roles.
        rationale: >
          Recruiting sustainability-aware personnel accelerates organisational
          capability in green software development.
        evidence_examples:
          - Job descriptions including sustainability competencies
          - Interview evaluation criteria
          - Recruitment guidelines
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2

      - id: GSP-L2-TRN-04
        levels: [2]
        title: Sustainability in Continuous Professional Development
        requirement: >
          The organisation shall include resource-efficient software or AI development
          topics in continuous professional development programs for relevant roles.
        rationale: >
          Continuous learning enables teams to adopt evolving sustainability practices
          and technologies.
        evidence_examples:
          - Professional development plans
          - Training roadmaps
          - Learning budgets or approved training lists
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2

      - id: GSP-L2-TRN-05
        levels: [2]
        title: Maintained Best Practice Guidelines
        requirement: >
          The organisation shall maintain and periodically update documented best
          practices or internal guidelines for energy-efficient software and AI development.
        rationale: >
          Maintaining up-to-date guidance ensures sustainability knowledge is preserved
          and disseminated across teams.
        evidence_examples:
          - Internal guidelines repositories
          - Version-controlled documentation
          - Change logs or update records
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-TRN-06
        levels: [2]
        title: Documentation of Sustainability Improvements
        requirement: >
          The organisation shall document energy or performance improvements resulting
          from software or AI development activities.
        rationale: >
          Documenting improvements supports organisational learning and demonstrates
          measurable sustainability progress.
        evidence_examples:
          - Improvement reports
          - Performance benchmarking records
          - Post-release evaluations
          - Sustainability improvement logs
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2

  - category: Measurement & Observability
    requirements:
      - id: GSP-L2-MEA-01
        levels: [2]
        title: Systematic Resource Usage Measurement
        requirement: >
          The organisation shall systematically measure and store resource usage
          metrics for software systems, including at least CPU, memory, storage,
          or network usage.
        rationale: >
          Measuring resource consumption provides the foundation for identifying
          sustainability improvement opportunities.
        evidence_examples:
          - Monitoring system configurations
          - Observability platform reports
          - Stored historical metrics
          - Resource usage logs
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-MEA-02
        levels: [2]
        title: Energy or Carbon Monitoring
        requirement: >
          The organisation shall monitor or estimate energy consumption and/or
          carbon footprint of software systems using measurement or estimation tools.
        rationale: >
          Direct or estimated energy and carbon monitoring enables organisations
          to assess environmental impact and track sustainability progress.
        evidence_examples:
          - Energy measurement tooling
          - Carbon estimation platforms
          - Sustainability reporting dashboards
          - Energy or emissions reports
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 4

      - id: GSP-L2-MEA-03
        levels: [2]
        title: Automated Sustainability Observability
        requirement: >
          The organisation shall maintain automated dashboards or tooling that
          continuously visualise and/or alert on resource usage or sustainability-related metrics.
        rationale: >
          Continuous observability enables timely detection of inefficiencies
          and supports proactive sustainability management.
        evidence_examples:
          - Monitoring dashboards
          - Alerting configurations
          - Integrated observability tooling
          - Incident response workflows related to resource usage
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-MEA-04
        levels: [2]
        title: Resource Usage Attribution Capability
        requirement: >
          The organisation shall attribute software resource usage and/or energy
          consumption to identifiable software components, systems, or infrastructure layers.
        rationale: >
          Attribution enables targeted optimisation efforts and improves
          accountability for sustainability improvements.
        evidence_examples:
          - Service-level or feature-level resource breakdowns
          - Platform or system-level attribution reports
          - Cost or sustainability allocation models
        assessment_scale:
          - Fine-grained Attribution
          - Medium-grained Attribution
          - Coarse Attribution
          - Not Implemented
        assessment_guidance:
          Fine-grained Attribution: >
            Resource usage is attributed to individual software components such
            as services, features, AI models, or queries.
          Medium-grained Attribution: >
            Resource usage is attributed to logical systems or domains composed
            of multiple components.
          Coarse Attribution: >
            Resource usage is attributed at application or infrastructure level.
          Not Implemented: >
            No attribution capability exists.
        scoring:
          Fine-grained Attribution: 1
          Medium-grained Attribution: 0.5
          Coarse Attribution: 0.25
          Not Implemented: 0
        priority: Supporting
        weight: 4

      - id: GSP-L2-MEA-05
        levels: [2]
        title: Lifecycle Resource Profiling
        requirement: >
          The organisation shall conduct performance and resource profiling at
          defined stages of the software development lifecycle.
        rationale: >
          Lifecycle profiling ensures sustainability considerations are integrated
          into development and operational processes.
        evidence_examples:
          - Profiling reports from CI/CD pipelines
          - Performance testing documentation
          - Production monitoring integration
          - Benchmarking reports
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-MEA-06
        levels: [2]
        title: Decommissioning Resource Footprint
        requirement: >
          The organisation shall estimate or measure the resource footprint
          associated with decommissioning activities, including data migration,
          deletion processes, and infrastructure shutdown.
        rationale: >
          Decommissioning is itself an energy- and resource-consuming activity.
          Measuring or estimating its footprint enables organisations to
          minimize it, plan migrations efficiently, and account for end-of-life
          impacts in the full lifecycle environmental record of the service.
        evidence_examples:
          - Decommissioning impact assessments
          - Migration or data deletion energy estimates
          - Infrastructure shutdown records including resource consumption data
          - Storage reclamation reports
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 1
        ts_alignment: "ISO/IEC TS 20125-1:2026 – End of life phase"

  - category: Software & Architecture Practices
    requirements:
      - id: GSP-L2-ARC-01
        levels: [2]
        title: Resource Efficiency in Architecture and Design
        requirement: >
          The organisation shall explicitly consider resource efficiency during
          software and AI architecture and design decisions.
        rationale: >
          Early design decisions significantly influence long-term software
          sustainability and resource consumption.
        evidence_examples:
          - Architecture decision records referencing efficiency
          - Design review checklists including sustainability considerations
          - Architecture guidelines or design principles
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-ARC-02
        levels: [2]
        title: Efficiency Trade-off Evaluation
        requirement: >
          The organisation shall evaluate trade-offs between resource efficiency
          and other software quality attributes such as correctness, accuracy,
          user experience, or maintainability.
        rationale: >
          Sustainable software engineering requires balancing environmental
          impact with functional and non-functional requirements.
        evidence_examples:
          - Trade-off analysis documentation
          - Architecture decision records
          - Performance versus quality evaluation reports
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-ARC-03
        levels: [2]
        title: Optimisation of Data Pipelines and AI/ML Models
        requirement: >
          The organisation shall apply optimisation techniques to data pipelines
          and AI/ML models to improve resource efficiency where applicable.
        rationale: >
          Data processing and AI models often represent significant sources of
          computational and energy consumption.
        evidence_examples:
          - Model optimisation reports (e.g., pruning, quantisation)
          - Data pipeline optimisation documentation
          - Performance benchmarking results
          - Efficiency improvement tickets or change logs
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 3

      - id: GSP-L2-ARC-04
        levels: [2]
        title: Reduction of Unnecessary Computation and Data Movement
        requirement: >
          The organisation shall identify and reduce unnecessary computation,
          data transfer, and data storage in software and AI systems.
        rationale: >
          Eliminating unnecessary processing and data movement directly reduces
          resource consumption and environmental impact.
        evidence_examples:
          - Refactoring initiatives
          - Caching or batching optimisation implementations
          - Data lifecycle management policies
          - Architecture improvement proposals
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-ARC-05
        levels: [2]
        title: Efficiency Review of Dependencies and Third-Party Components
        requirement: >
          The organisation shall periodically review software dependencies and
          third-party components to identify opportunities for improving resource efficiency.
        rationale: >
          External dependencies can introduce hidden sustainability impacts and
          optimisation opportunities.
        evidence_examples:
          - Dependency review reports
          - Component evaluation documentation
          - Software bill of materials (SBOM) analysis
          - Upgrade or replacement decisions linked to efficiency
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2

      - id: GSP-L2-ARC-06
        levels: [2]
        title: Feature Necessity and Scope Assessment
        requirement: >
          The organisation shall assess the environmental justification of
          proposed features or functionality during requirements gathering,
          including consideration of whether features are necessary to deliver
          the intended user value relative to their resource cost.
        rationale: >
          Features that are not needed generate unnecessary computation, data
          transfer, and maintenance burden throughout a service's life. Upstream
          scope discipline is one of the highest-leverage sustainability
          interventions available to a development team.
        evidence_examples:
          - Feature prioritization records referencing environmental cost
          - Scope review documentation with necessity assessment
          - Value-versus-environmental-impact analysis artefacts
          - Backlog refinement notes referencing sustainability criteria
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2
        ts_alignment: "ISO/IEC TS 20125-1:2026 – Requirements gathering phase"

      - id: GSP-L2-ARC-07
        levels: [2]
        title: Infrastructure and Hosting Sustainability
        requirement: >
          The organisation shall consider the environmental performance of
          hosting providers and infrastructure choices during design, including
          energy source, data centre efficiency indicators (e.g., PUE, WUE),
          and geographic carbon intensity of the electricity grid.
        rationale: >
          Infrastructure and hosting choices are among the largest determinants
          of a digital service's operational carbon footprint. Evaluating these
          factors at design time prevents lock-in to high-emission infrastructure.
        evidence_examples:
          - Hosting or cloud provider selection documentation referencing
            sustainability criteria
          - Procurement evaluation criteria including environmental performance
          - Green hosting or low-carbon region selection records
          - Architecture decision records (ADRs) referencing carbon intensity
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3
        ts_alignment: "ISO/IEC TS 20125-1:2026 – Design phase"

      - id: GSP-L2-ARC-08
        levels: [2]
        title: Carbon-Aware Workload Management
        requirement: >
          The organisation should consider the carbon intensity of the
          electricity grid when scheduling or deploying workloads, shifting
          non-urgent computation to lower-carbon windows where technically
          feasible.
        rationale: >
          Temporal flexibility in workload execution offers a high-impact,
          low-cost mechanism for reducing operational carbon emissions without
          architectural changes. This is particularly relevant for batch
          processing, model training, and data pipeline jobs.
        evidence_examples:
          - Scheduling policies referencing grid carbon intensity
          - Demand-shifting or carbon-aware deployment configurations
          - Carbon-aware tooling integration records (e.g., Carbon Aware SDK)
          - Documentation of workloads identified as shiftable
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2
        ts_alignment: "ISO/IEC TS 20125-1:2026 – Operations phase"

  - category: Continuous Improvement
    requirements:
      - id: GSP-L2-IMP-01
        levels: [2]
        title: Periodic Review of Efficiency-Related Design Decisions
        requirement: >
          The organisation shall periodically revisit software and AI design or
          architectural decisions that affect resource efficiency.
        rationale: >
          Efficiency assumptions and technological contexts evolve over time.
          Revisiting past design decisions helps organisations identify new
          optimisation opportunities and prevent efficiency regressions.
        evidence_examples:
          - Architecture or design review records
          - Retrospective documentation addressing efficiency trade-offs
          - Roadmaps including optimisation initiatives
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-IMP-02
        levels: [2]
        title: Internal Sharing of Efficiency Improvement Lessons
        requirement: >
          The organisation shall share lessons learned internally from initiatives
          aimed at improving resource efficiency in software and AI systems.
        rationale: >
          Sharing knowledge across teams promotes continuous improvement and
          accelerates adoption of efficiency practices across the organisation.
        evidence_examples:
          - Internal presentations or brown bag sessions
          - Knowledge base articles or internal documentation
          - Retrospective reports distributed across teams
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 2

      - id: GSP-L2-IMP-03
        levels: [2]
        title: Documented Evidence of Efficiency Improvements
        requirement: >
          The organisation shall maintain documented examples demonstrating reduced
          resource usage or energy consumption resulting from software or AI
          optimisation initiatives.
        rationale: >
          Documenting measurable improvements enables accountability, supports
          verification processes, and provides reusable optimisation knowledge.
        evidence_examples:
          - Performance or energy benchmark reports
          - Before-and-after efficiency measurements
          - Case studies of optimisation initiatives
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Core
        weight: 3

      - id: GSP-L2-IMP-04
        levels: [2]
        title: External Knowledge Sharing on Software Sustainability
        requirement: >
          The organisation should share lessons learned or best practices related to
          software and AI resource efficiency with the external community.
        rationale: >
          External knowledge sharing contributes to ecosystem-wide sustainability
          improvements and demonstrates organisational commitment to responsible
          software engineering.
        evidence_examples:
          - Blog posts or technical articles
          - Conference presentations or workshops
          - Open-source contributions related to efficiency
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2

      - id: GSP-L2-IMP-05
        levels: [2]
        title: Post-Service Sustainability Retrospective
        requirement: >
          The organisation shall conduct a sustainability retrospective at the
          end of a digital service's operational life, documenting lessons
          learned on resource efficiency, environmental impact, and design
          decisions that influenced sustainability outcomes, for use in
          future projects.
        rationale: >
          End-of-life retrospectives close the learning loop across the full
          service lifecycle. Insights from decommissioned services are among
          the most reliable inputs for improving the sustainability of future
          services, as they reflect real operational conditions rather than
          design-time estimates.
        evidence_examples:
          - Decommissioning retrospective reports
          - Post-service sustainability closure documents
          - Lessons-learned records referenced in subsequent project planning
          - Archived sustainability metrics from the full service lifetime
        assessment_scale:
          - Implemented
          - Partially Implemented
          - Not Implemented
        priority: Supporting
        weight: 2
        ts_alignment: "ISO/IEC TS 20125-1:2026 – End of life phase"
