Complete aspect registry B3 parity fixtures #1

Open

opened 2026-08-04 05:56:20 +00:00 by agent.omo · 0 comments

agent.omo commented

2026-08-04 05:56:20 +00:00

Contributor

Stable ID: FM-B3-PARITY
Source: plans/ASPECT_REGISTRY_TICKETS.md#B3
Source status: tracked work item, partially implemented
Disposition: open operational work
Blocked by: owner deployment of the fixed bifrost and tamiel configurations

Problem

The parity machinery exists in modules/aspects/parity.nix, but B3 is incomplete until fixtures are captured from hosts actually switched to the fixed state. The capture correctly refuses to turn a same-tree evaluation into evidence of deployed reality.

Acceptance

Deploy the fixed configurations to bifrost and tamiel through the owner-operated path.
Run the parity capture only after it proves each host's /run/current-system equals the built toplevel.
Commit tests/aspects/fixtures/parity-bifrost.json and parity-tamiel.json.
The offline check compares compat activation with resolver ownership and prints actionable mismatches.
just check passes inside the repository devshell.

Provenance

Migrated from VCS operational planning data on 2026-08-04. The completed A1-A4, B1-B2, and C1-C3 campaign work remains provenance in the Forgejo wiki; it is not reopened.

Stable ID: FM-B3-PARITY Source: `plans/ASPECT_REGISTRY_TICKETS.md#B3` Source status: tracked work item, partially implemented Disposition: open operational work Blocked by: owner deployment of the fixed bifrost and tamiel configurations ## Problem The parity machinery exists in `modules/aspects/parity.nix`, but B3 is incomplete until fixtures are captured from hosts actually switched to the fixed state. The capture correctly refuses to turn a same-tree evaluation into evidence of deployed reality. ## Acceptance - Deploy the fixed configurations to bifrost and tamiel through the owner-operated path. - Run the parity capture only after it proves each host's `/run/current-system` equals the built toplevel. - Commit `tests/aspects/fixtures/parity-bifrost.json` and `parity-tamiel.json`. - The offline check compares compat activation with resolver ownership and prints actionable mismatches. - `just check` passes inside the repository devshell. ## Provenance Migrated from VCS operational planning data on 2026-08-04. The completed A1-A4, B1-B2, and C1-C3 campaign work remains provenance in the Forgejo wiki; it is not reopened.