bde961c6f2
PAF becomes saf/device (history kept), STATE.md dissolves into saf/state.md with the dated era archived, the substrate SAF moves up from souveraine, and every agreement points at saf/INDEX.md and nowhere else. one map, nothing to remember
48 lines
2.3 KiB
Markdown
48 lines
2.3 KiB
Markdown
# SouveraineOS working agreement
|
|
|
|
The personal agreement is `~/.codex/AGENTS.md`. The cross-repo map is
|
|
`../AGENTS.md`; read it when work crosses repository boundaries.
|
|
|
|
## This repository
|
|
|
|
- SouveraineOS is the umbrella and design of record. It holds doctrine,
|
|
cross-repo state, tasks, evidence, and the device spine. Component code
|
|
lives in its component repository.
|
|
- **The map is `saf/INDEX.md`. Read it first. Everything — architecture,
|
|
device, state, work — is reached from it. Nothing else asks where to look.**
|
|
- If the phone is broken, start with `START-HERE.md`, then the owning
|
|
`saf/device/` layer doc.
|
|
- `saf/state.md` is the resume anchor. Check its date and verify any material
|
|
claim against the current tree, CI, package, or device.
|
|
- `docs/tasks/README.md` is the live work index, reached from the SAF as
|
|
**work**. Extend the existing owner; archive completed or superseded
|
|
material rather than growing a second spine.
|
|
- The repo is often dirty from parallel work. Inspect first and stage only the
|
|
paths this task owns.
|
|
|
|
## Current authority
|
|
|
|
- `saf/device/` here is canonical (the PAF spine). `../Pixel3Arch/PAF/` is
|
|
historical. Device code, packages, overlays, tools, and the kernel remain
|
|
in `../Pixel3Arch/`.
|
|
- Where docs and code disagree, establish what runs and reconcile the owning
|
|
doc. Dated evidence remains evidence, not current state.
|
|
- Preserve the one-owner rule in session authority, device state, display,
|
|
USB role, charging, networking, and other actuators.
|
|
- No GNOME or KDE library dependencies.
|
|
|
|
## Delivery
|
|
|
|
- Ordinary Souveraine application and package builds go through Gitea Actions.
|
|
Casey's 2026-08-07 instruction supersedes any older ordinary-build recipe
|
|
that treats direct ArchDev commands as the primary path.
|
|
- Direct runner access is for focused diagnosis or an explicitly requested
|
|
experiment. It is not a release pipeline.
|
|
- Use `tools/ci-status.sh <repo>` for CI status and inspect the relevant job or
|
|
artifact when the question is what shipped.
|
|
- The Pixel 3 is Casey's daily driver. Prefer package-owned installation,
|
|
never build on it, do not toggle its VPN for convenience, and leave reboot or
|
|
flash decisions to Casey.
|
|
|
|
Keep docs tight: measured state, remaining work, proof, and the next useful
|
|
move. No AI attribution or session essays in commits.
|