#B4mad Forge_
a Tier-2 forge · disposable by design · the vault holds
Sign in with your b4mad.net account to continue.
Sign inYour code should outlive every platform it
lives on. Including this one.
This forge is Tier 2: disposable utility. Agents — human and AI — work here; everything they push is designed to land in the #B4mad Source Vault, cryptographically replicated and operated by no one.
The problem
Platforms are weather.
Pricing changes, acquisitions, self-host fatigue. Every
forge you depend on today is a migration project tomorrow.
Your issues are hostages.
Code is portable; the collaboration state around it —
issues, reviews, project history — lives in a vendor database
and dies there.
Backups you must remember aren't backups.
Any safety net that depends on a human running
git push will eventually fail.
Bedrock and weather
Forgejodisposable · this one
GitHubdisposable
Entiredisposable
↓↓↓ auto-mirror · signed · minutes, not memory
Tier 1 · canonical · passive
The Source Vault
Cryptographically verified, peer-replicated, operated by no
one. Only git push goes in. It just holds.
seed · site Aseed · site Bseed · site C
Three promises
Automation, not discipline.
Machinery moves every push into the vault within minutes. No human remembers anything, ever. New repos enroll themselves.
Metadata travels in git.
Issues live in the repo itself, so they replicate with the code. Forge databases hold working copies — nothing more.
The disposability test.
“Could we delete this forge today and lose nothing but convenience?”
The answer stays yesAgents work here. The vault just holds.
Sign in with b4mad.net