Repository navigation
Pin the fleet authority at a declared generation - #2
Merged
Merged
Conversation
The 2026-10-07 consolidation (ADR-0041 of libre-ai/project-governance) admitted this repository under its long name and retired the short-name donors. Its card had not followed: `repository:` still declared the donor, a repository deleted the same day, so the card identified this project as something that no longer exists. Its dependency pins named deleted repositories at commits now unreachable -- verified: each of those shas answers 422 on both surviving authorities, so no pin could be preserved as written. Each entry names the successor at a revision that exists: project-governance at generation 2024a4884b, which that authority's fleet-pins register declares, and schemas-and-contracts at d2767988. Measured before changing anything, because a false card and a broken build are not the same finding: 105 manifests across the 29 repositories of the organisation were read, and NO destination declares a build dependency on a deleted repository. The entries corrected here were declarations, not dependencies -- the one Cargo surface involved is the `[package] repository` metadata URL, which pointed at a deleted repository and now points at this one. Where several entries now name the same successor, they are kept separate: each states a distinct dependency reason, and one repository holding three capabilities is what a consolidation means. Validated against ecosystem/schemas/project.v1.schema.json. Claude-Session: https://claude.ai/code/session_01BRoYJKEsRC2BUSDPQBoNnA Signed-off-by: Constantin Jais <74049135+constantin-jais@users.noreply.github.com>
Signed-off-by: Constantin Jais <cjais@pm.me>
This repository pinned libre-ai/project-governance at a commit that exists but that the authority's own ecosystem/fleet-pins.v1.yaml does not declare as a generation. The repaired fleet-pins gate named it; before the repair the gate read a hardcoded `main` on every surface and reported "2 assertion(s) hold" over a fleet carrying twenty-four drifts, this one among them. The pin moves to 2024a4884b, a declared generation and the first a consumer can actually install -- proved by the act: `bun install` in libre-ai/signalement against it resolves 32 packages, where the two generations before it failed on a workspace-local specifier. Measured before changing anything: the `workflow_call` signature of validate-composition.yml is BYTE-IDENTICAL between the sha pinned here and 2024a4884b, so the inputs this repository supplies are unchanged. The three other reusable workflows did not exist at the old sha at all -- it predates the doctrine transfer. Claude-Session: https://claude.ai/code/session_01BRoYJKEsRC2BUSDPQBoNnA Signed-off-by: Constantin Jais <74049135+constantin-jais@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repository pinned
libre-ai/project-governanceat a commit that exists but that the authority's ownecosystem/fleet-pins.v1.yamldoes not declare as a generation.The repaired fleet-pins gate named it. Before the repair that gate read a hardcoded
mainon every surface —mainon the destinations carries three documentary commits whose tree holds no workflows — so it returned an empty tree for each one and reportedFleet pins verified: 2 assertion(s) holdover a fleet carrying 24 drifts, this one among them.The pin moves to
2024a4884b, a declared generation and the first a consumer can actually install, proved by the act:bun installinlibre-ai/signalementagainst it resolves 32 packages, where the two generations before it failed on a workspace-local specifier.Measured before changing anything
The
workflow_callsignature ofvalidate-composition.ymlis byte-identical between the sha pinned here and2024a4884b, so the inputs this repository supplies are unchanged. The three other reusable workflows did not exist at the old sha at all — it predates the doctrine transfer.https://claude.ai/code/session_01BRoYJKEsRC2BUSDPQBoNnA