Skip to content

Name this repository and the authorities that exist - #1

Merged
constantin-jais merged 1 commit into
migrate/recover-codefrom
feat/forge-realization
Oct 8, 2026
Merged

constantin-jais merged 1 commit into
migrate/recover-codefrom
feat/forge-realization

Conversation

@constantin-jais

Copy link
Copy Markdown
Contributor

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 now 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.

A false card and a broken build are not the same finding

Measured before changing anything: 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 single Cargo surface involved is the [package] repository metadata URL, which pointed at a deleted repository and now points at this one.

Where several entries 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.

https://claude.ai/code/session_01BRoYJKEsRC2BUSDPQBoNnA

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>
@constantin-jais
constantin-jais merged commit 64f1439 into migrate/recover-code Oct 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant