Forge an organization.
Launch a governed community. Set rules for votes, treasury moves, roles, and agents. OrgForge checks every action before it runs.
For DAO founders, creator communities, contributor networks, treasury-governed groups, and agent-assisted teams.
Most organizations write rules. Then nothing checks them.
Policies live in documents. Approvals live in email threads. Permissions are spread across dashboards. When the moment comes, the rules are out of date, out of sight, or out of band.
- The rule was written down, but never checked.
- The approval was rubber-stamped because the threshold was never set.
- The role was supposed to expire, but nobody removed it.
- The limit lived in a policy doc instead of in the system enforcing it.
- The agent had keys, and the keys were the whole authorization.
In practice, governance is a narrative layered on top of execution, not a mechanism inside execution.
From the OrgForge whitepaper
Governance that runs.
Most platforms help you launch a token, post a vote, or wire up a multi-sig, then leave the actual rule-following to good intentions and group chats.
Every organization launched on OrgForge has an OrgSpec. A machine-readable constitution. Spending limits, approval thresholds, role permissions, agent restrictions, freeze states. Every action is checked against it before anything moves.
Propose an action. Check the rules. Execute with proof.
Anyone in the organization can propose an action. The protocol checks it against your OrgSpec. If the rules are satisfied, a signed authorization is issued. Execution systems verify that signature before anything happens.
Someone in your org wants to do something.
A human, a multi-sig, an agent. They submit what they want to do. Who they are. The amount, the target, the parameters.
action: send_payment
amount: 5,000 USDC
to: contractor.eth
Your community's constitution is the source of truth.
The protocol reads your OrgSpec. Spending limit, role permission, approval threshold, freeze state. Every condition has to pass.
treasury_lead.allowed = [send_payment]
org_state = NORMAL
quorum.required = 2 of 3
A signed proof, or no proof at all.
If the rules are satisfied, the protocol issues a cryptographic authorization. Execution systems check the signature, then act. If the rules fail, no proof exists, and nothing can run.
× BLOCKED → logged, halted
proof_id: 0x9a3f...c104
issued_at: 2026-04-30T22:14Z
Four organization shapes. One protocol underneath.
Pick the shape that fits how your group already works. Add governance tokens, treasuries, and approval flows. The protocol enforces the rules whether the actor is a member, a delegate, or an agent.
These aren't templates. They're patterns. All four run on the same OrgSpec enforcement layer.
A community with shared rules.
A DO. Members govern jointly. Useful for fan communities, treasury-backed creator collectives, cooperatives, and civic groups. Every group decision runs through the protocol.
Forge a DO → TreasuryA group where tokens vote.
A DAO. Launch a governance token, fund a treasury, vote on proposals. Token votes don't just record an outcome. They trigger the action only after the proof verifies.
Forge a DAO → DelegationA collective with delegated power.
A DAC. Authority is split across roles and committees. Contributor groups, working groups, multi-sig signers. Each acts inside their lane. The OrgSpec keeps everyone in scope.
Forge a DAC → AgentsAn org where agents are members too.
An AAO. Software agents and humans operate under the same rules. Hard limits, scoped access, no root keys. Agents act inside policy, not above it.
Forge an AAO →Bitcoin showed how money can move by proof instead of permission. OrgForge applies that pattern to authorization.
Execution proceeds when the proof verifies, and only when the proof verifies.
Cryptographic proof, not bank approval. Money moves when the proof verifies. No counter-signing institution required.
Cryptographic proof, not committee approval. Actions execute when the proof verifies. No manual authority check required at execution time.
This is what it looks like when permission stops being a trust call.
From hosted protocol to authorization network.
OrgForge runs as hosted infrastructure today. The path to a fully open authorization network is staged. Each phase is a real milestone, not a marketing line.
Hosted protocol with SDK
The protocol runs as managed infrastructure with a dedicated validator. Organizations are forged through the platform. Authorization artifacts are issued and verified in the current demo environment.
ActiveAuthorization network
Multiple independent validators evaluate intents in parallel. Threshold signatures replace single-validator trust. Quorum is the security model.
NextFully decentralized
Validation and anchoring move out to the network. The protocol becomes neutral infrastructure for organizational authority. Like DNS or TLS, but for permission.
FutureForge yours. Set the rules. Watch them hold.
A guided wizard takes you from idea to running organization. Bring your community. Bring your rules. The protocol does the rest.