Allo is best categorized as modular capital-allocation infrastructure rather than as a grants site. The docs explicitly distinguish the protocol from Gitcoin’s Grants Stack product layer.
The core mechanism is the split between three things: project identities in the registry, pools of capital, and strategy contracts that determine recipient eligibility, allocation inputs, payout logic, and distribution method.
The strategy layer is the most important analytical surface. Allo’s own docs reduce funding design to recipients, allocation, payouts, and distribution, which makes it easy to compare different grant and treasury systems without treating them as totally separate products.
Pools are permanently linked to their chosen strategy once created. That means strategy selection is a governance and control decision with path dependence, not just a configuration toggle.
The registry matters because it creates persistent project profiles that can both receive/distribute funding and accumulate reputation/discoverability. The docs also note strategies can use attestations or SBT balances for automated eligibility checks, which means off-protocol credential systems can become hidden gatekeepers.
The repo README and Registry documentation show additional power surfaces in profile ownership, pool-manager/admin permissions, and the Allo owner’s treasury/fee controls.
The Anchor-contract framing is worth retaining because it means profiles are not just listings; they can become controlled execution/receiving addresses tied to a registry identity.
Specific source signals worth retaining
Docs landing page: says Allo is a set of smart contracts for democratic capital allocation and explicitly contrasts Allo Protocol with Grants Stack.
Overview page: identifies Allo.sol, strategy contracts, and Registry.sol as the core onchain components.
Project Registry page: describes the registry as a universal onchain registry of anyone receiving or distributing capital through Allo, with discoverability and reputation as explicit goals.
Pool page: explains that pools are created/owned by registry profiles and are only meaningful in combination with a strategy.
Allocation Strategy page: compresses the mechanism into recipient eligibility, allocator eligibility/input form, payout computation, and distribution style.
Allo.sol page: confirms strategy immutability per pool, pool manager/admin roles, and fee structure.
Strategies page: confirms Allo generalizes funding rounds into a register-allocate-distribute flow and that custom strategies are first-class.
allo-v2.1 README + Registry.md: show the profile / anchor / pool-management architecture and the explicit actor model around profile owners, pool managers, and Allo owner.
Why this entry belongs in the corpus
Allo is a strong addition because it captures a reusable mechanism for decomposing funding systems into identity, pool, and strategy layers.
It sharpens future comparisons involving grants infrastructure, retroPGF, reputation gating, project registries, and any governance system where money flows are programmable but not authority-free.
The reusable insight is that “democratic capital allocation” often depends less on one headline mechanism like quadratic funding than on who controls strategy templates, registry inclusion, eligibility proofs, manager permissions, and the interface/product layer above the contracts.