Aspect prioritizes open-source contributions and requests according to the following framework. Work is evaluated in order of precedence, with exceptions where ecosystem or strategic factors apply.Documentation Index
Fetch the complete documentation index at: https://docs.aspect.build/llms.txt
Use this file to discover all available pages before exploring further.
Priority tiers
Tier 1 — Active Engagement Customers Requests from customers operating under an active Statement of Work (SoW) receive highest priority. Work is scoped and scheduled in alignment with the terms of the engagement. Tier 2 — Bazel Open Source Support Subscribers (BOSS) Customers enrolled in Bazel Open Source Support receive prioritized consideration for open-source requests outside a formal SoW. Where consulting hours are available, they may be used to fund development of these changes. Tier 3 — General Customer Requests Requests from customers without an active SoW or BOSS subscription are evaluated based on impact, feasibility, and alignment with the current roadmap. Tier 4 — Community Contributions Contributions from the broader open-source community are reviewed and merged as capacity allows. Quality, test coverage, and compatibility with supported configurations are evaluated before acceptance.Exceptions and accelerators
The following factors can elevate work outside the standard tier ordering:- Ecosystem-driven requirements — Changes necessary to maintain compatibility with ecosystem evolution (e.g., bzlmod migration support) are prioritized regardless of originating tier, as they affect all users across the ecosystem.
- Strategic alignment — Work on strategically designated rulesets may be accelerated based on roadmap priority, independent of request source. Current examples include
uvintegration inrules_pyand platform upgrades inrules_js.