Without a route record
Cross-repo work becomes one oversized plan, duplicated documentation, and status that cannot be traced back to the owning project.Operational route
Multi-repo initiative
Carry one durable outcome across repositories without copying project truth or losing which run produced each result.
Page evidence
- cross-project wikishared canon
- federation planchild targets
- merged resultssource tagged
- plugin wikiproject canon
- website wikiproject canon
- benchmark wikiproject canon
Read through the workspace manifest. Child page bodies remain in their owning repositories.
Route comparison
Same job. A visible operating record.
With Guild Stack
The workspace stores coordination facts, projects keep local runs and knowledge, and the initiative closes only when every leg resolves.Route stops
Request to verified result.
- 01
Define the durable goal
Create the initiative and make its acceptance and close gates explicit.
- 02
Classify ownership
Keep cross-project knowledge at the umbrella and project-specific truth in the child repo.
- 03
Attach runs by choice
Link each project run to the initiative without changing the run contract.
- 04
Close all three legs
Resolve execution, release, and docs reconciliation before closure.
Receipts
What the route leaves behind.
- 01 Path
.guild/initiatives/RoleDurable progress, acceptance, and close-gate evidence.
- 02 Path
.guild/workspace/RoleChild identities, paths, and relationship facts.
- 03 Path
project .guild/runs/RoleSource-tagged execution evidence at the owning root.
- 04 Record
Public documentationRoleThe shared product and implementation guidance reconciled to shipped behavior.
Next
