The allocation policy distributes available capacity across eight areas. The sliders must always sum to 100%.
| Allocation | What it does |
|---|---|
| Ship | Converts lines of code into shippable value and revenue. |
| Open source | Generates community contribution, karma, and brand. |
| Quality | Reduces cyclomatic complexity and CQRS violations. |
| Security | Reduces CVE, XSS, SQL injection, shell injection, and CSRF debt. |
| Research / UX | Improves product-market fit and unlocks automation stages. |
| Marketing | Grows the human customer segment and brand awareness. |
| Civic action | Builds karma, slows alignment drift, and enables civic influence events. |
| Power infra | Expands power capacity, required for later stages. |
Policies take effect immediately. Changing the security allocation from 5% to 30% will reduce CVE debt accumulation starting from the next tick. Changing it back will reverse that effect.