Plan pi-provider deployment repository contract #40
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/strategy!40
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/pi-provider-repository-contract"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This plan fixes
pi-providerso 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.
allod-agent referenced this pull request from allod/nexus2026-08-24 06:52:09 +01:00