Carried files reference the private template repo
The fleet rule now states that a carried file names the template repo in neither prose nor a link. The template is private, so any such reference 404s for this repo's readers, and it exposes coordination machinery a consumer of this repo should never have to see.
In this repo:
.github/copilot-instructions.md
The usual instance is the drift-reporting paragraph in .github/copilot-instructions.md, which hard-links the private repo twice - and one of those links targets an AGENTS.md section that no longer exists upstream, so it 404s even for a reader who does have access. That paragraph is stale carried content: upstream carries neither the paragraph nor the section it points at.
What to do
Remove the reference. Where the text expresses a real behavior - "report a rule discrepancy upstream" - state the behavior, not the destination; the maintainer supplies the destination out of band, so the instruction survives without a dead link in a public file.
Also watch for the softer form, which names no repo but still attributes a rule to a coordinator the reader cannot reach:
- "the template ships README + HISTORY as the default" -> "README + HISTORY are the default"
- "the template implements it as the literal
main" -> "it is implemented as the literal main"
Enforcement
The hub fleet audit now flags the named/linked form mechanically, so this will show as a DRIFT carried: ... finding until it is cleared. The attribution form is a judgment call and is not mechanically checked.
Filed from the hub as part of a fleet-wide sweep: 13 of 20 repos carry this, 8 of them public. No reply needed - this is actionable as written.
Carried files reference the private template repo
The fleet rule now states that a carried file names the template repo in neither prose nor a link. The template is private, so any such reference 404s for this repo's readers, and it exposes coordination machinery a consumer of this repo should never have to see.
In this repo:
.github/copilot-instructions.mdThe usual instance is the drift-reporting paragraph in
.github/copilot-instructions.md, which hard-links the private repo twice - and one of those links targets anAGENTS.mdsection that no longer exists upstream, so it 404s even for a reader who does have access. That paragraph is stale carried content: upstream carries neither the paragraph nor the section it points at.What to do
Remove the reference. Where the text expresses a real behavior - "report a rule discrepancy upstream" - state the behavior, not the destination; the maintainer supplies the destination out of band, so the instruction survives without a dead link in a public file.
Also watch for the softer form, which names no repo but still attributes a rule to a coordinator the reader cannot reach:
main" -> "it is implemented as the literalmain"Enforcement
The hub fleet audit now flags the named/linked form mechanically, so this will show as a
DRIFT carried: ...finding until it is cleared. The attribution form is a judgment call and is not mechanically checked.Filed from the hub as part of a fleet-wide sweep: 13 of 20 repos carry this, 8 of them public. No reply needed - this is actionable as written.