Why it matters
Everything lives in Git gives ForkMesh a concrete mechanism for collaboration records committed beside the code they describe. Issues, pull requests, discussions, and release notes are files committed to the repository. Clone the repo and you own the whole project history, code and conversation alike.
Collaboration data becomes fragile when issues, reviews, and authorship only exist inside one hosted database. In ForkMesh, everything lives in Git addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles everything lives in Git through the same split it uses across the product: local identities sign issue events, patch PRs, catalog records, and contribution inbox items before they travel through mirrors.
The behavior is intentionally narrow: Issues, pull requests, discussions, and release notes are files committed to the repository. Clone the repo and you own the whole project history, code and conversation alike. Mirrors can verify provenance before accepting or displaying collaboration records.
Where it fits
Use everything lives in Git when project context needs to survive migrations, forks, offline work, and mirror failover.
It pairs with the rest of Signed, portable collaboration because Everything lives in Git keeps collaboration records committed beside the code they describe connected to the repository, its signatures, and the nodes that serve it.