Why it matters
Web contribution inbox gives ForkMesh a concrete mechanism for offline owners receiving signed web submissions for later review. Visitors can file issues and pull requests from the website even while the owner is offline. Signed submissions wait in an inbox; the owner reviews, commits, and the mesh syncs back.
Collaboration data becomes fragile when issues, reviews, and authorship only exist inside one hosted database. In ForkMesh, web contribution inbox 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 web contribution inbox 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: Visitors can file issues and pull requests from the website even while the owner is offline. Signed submissions wait in an inbox; the owner reviews, commits, and the mesh syncs back. Mirrors can verify provenance before accepting or displaying collaboration records.
Where it fits
Use web contribution inbox when project context needs to survive migrations, forks, offline work, and mirror failover.
It pairs with the rest of Signed, portable collaboration because Web contribution inbox keeps offline owners receiving signed web submissions for later review connected to the repository, its signatures, and the nodes that serve it.