Plan pi-provider deployment repository contract #40

Merged
vnprc merged 2 commits from agent/pi-provider-repository-contract into master 2026-08-24 14:30:30 +01:00
Member

This plan fixes pi-provider so it follows the deployment's configured repositories and recipient graph.
It splits the work into an ordered secrets contract change and a final Nexus integration change.
Running machines remain unchanged until their deployment pins are updated and Nexus is rebuilt.
Synthetic split-key, staged-output, rollback, and existing-consumer checks are the executable proof.
If either slice is wrong, keep the old pins or revert the implementation PRs in reverse order.

Refs allod/nexus#29

Risk: R3. The implementation will change a shared recipient interface and the path that writes encrypted provider credentials. Two independent model reviews are recorded in the review prompt; both blockers are resolved in the final plan contract.

This plan fixes `pi-provider` so it follows the deployment's configured repositories and recipient graph. It splits the work into an ordered secrets contract change and a final Nexus integration change. Running machines remain unchanged until their deployment pins are updated and Nexus is rebuilt. Synthetic split-key, staged-output, rollback, and existing-consumer checks are the executable proof. If either slice is wrong, keep the old pins or revert the implementation PRs in reverse order. Refs allod/nexus#29 Risk: R3. The implementation will change a shared recipient interface and the path that writes encrypted provider credentials. Two independent model reviews are recorded in the review prompt; both blockers are resolved in the final plan contract.
vnprc approved these changes 2026-08-24 14:30:24 +01:00
vnprc merged commit 131f034add into master 2026-08-24 14:30:30 +01:00
vnprc deleted branch agent/pi-provider-repository-contract 2026-08-24 14:30:30 +01:00
Sign in to join this conversation.
No description provided.