pi-ext

---
id: PX-PHASE-0ZJ4MHL_
type: phase
title: Daily Reliability
label: daily
---

## Sub-mission

Keep daily Pi use dependable while reducing concrete workflow friction.
Serve the [mission](../../MISSION.md) through bounded, useful improvements rather than another migration campaign.

## Ranked priorities

1. Reliable daily workflows and a usable installation.
2. Preserved behavior and explicit architectural boundaries.
3. Trustworthy verification of observable contracts and declared compatibility.
4. Fast focused iteration with minimal accidental complexity.

## Decision defaults

| Concern | Default |
| --- | --- |
| Stability | Preserve the last usable build; prefer bounded, reversible changes. |
| Architecture | Preserve [core law](../../SYSTEM.md): root installation unit, one version, isolated siblings. |
| Compatibility | Preserve declared support; change it only with evidence and explicit approval. |
| Quality | Verify public contracts; expose upstream defects rather than normalizing dependency patches. |
| Speed | Use the smallest decisive check during iteration; complete verification at integration boundaries under [repository rules](../../RULES.md). |
| Migration | Migrate only to resolve demonstrated daily friction or compatibility needs; preserve observable behavior. |
| Experimentation and debt | Isolate experiments in OS temp; remove superseded paths and debt encountered within the change. |

## Non-goals

Another architecture campaign, unrelated rewrites, speculative abstractions, or test-score targets.
Feature expansion without a concrete daily workflow need.
Unapproved changes to core law, specifications, or approved plans.

## Observable exit criteria

- [ ] Representative daily workflows run without recurring unresolved extension failures or manual recovery.
- [ ] Installation and routine supported upgrades have reproducible verification.
- [ ] Remaining priorities require a different operating posture, explicitly confirmed by the human.