MetaLeX

• Name: MetaLeX
• URL: https://metalex-docs.vercel.app/
• Category: legal-engineering operating system / BORG policy layer / Safe-based governance-control infrastructure
• Summary: MetaLeX is better cataloged not as a generic crypto law firm or only a DAO-adjacent advisory brand, but as a law-plus-code governance stack that tries to turn legal entities into programmable policy machines. Its first-party materials repeatedly frame MetaLeX OS as a modular system for BORGs, cyberCORPs, and cyberDeals, with the practical core being a Safe-wrapped policy engine (borg-core), hierarchical access control (BorgAuth), configurable condition checks, implant modules, and explicit linkage to offchain legal documents. The important mechanism is not just legal wrappers for DAOs. It is that governance authority becomes programmable through role tiers, whitelist/blacklist modes, transaction constraints, condition managers, legal-document references, and DAO- or authority-BORG-overseen Safe operations. That makes MetaLeX a strong fit for the corpus and one of the cleaner examples where permissions-and-policy is genuinely central rather than merely adjacent.
• What it does:
  • Frames BORGs as legal entities whose governance and operations are partly delegated to smart contracts and related automation
  • Uses borg-core as a Safe guard / policy layer that can run in whitelist, blacklist, or unrestricted mode and constrain transactions down to recipients, methods, parameter ranges, cooldowns, and delegatecall policy
  • Uses BorgAuth as a hierarchical ACL system with Owner, Admin, and Privileged roles plus external auth adapters for more dynamic authority assignment
  • Uses a Condition Manager so actions can require additional checks such as time delays, external data, token balances, signatures, or other custom conditions
  • Stores references to legal agreements and DAO metadata onchain so legal documents and contract behavior are linked rather than treated as separate operational worlds
  • Extends the base stack with implants for grants, veto paths, ejection/removal, failsafes, and other organization-specific control logic
  • Expands the same design posture into adjacent product lines such as cyberCORPs and cyberDeals, where legal structure and contract execution are meant to interoperate rather than remain loosely coupled
• Key claims:
  • The docs homepage says MetaLeX builds legal and technical infrastructure for BORGs and other onchain entities, which is the clearest first-party explanation for why this should be treated as a protocol/control-plane note rather than only a service-firm profile.
  • The FAQ is especially important because it says the borgCORE wraps a Gnosis Safe with a policy layer and ERC-4824 interface, and presents MetaLeX OS as a composable operating system of smart-contract modules plus legal templates.
  • The same FAQ makes the policy surface unusually explicit: whitelist, blacklist, and unrestricted modes; BorgAuth ACL; Condition Manager checks; implants; and onchain references to legal documents. That is exactly the kind of hidden power surface the corpus should preserve.
  • The BorgAuth docs show a concrete role hierarchy of Owner (99), Admin (98), and Privileged (97), plus role adapters that can defer authorization to external governance logic. This matters because MetaLeX is not only encoding legal intent; it is encoding who may change or override organizational policy over time.
  • The borg-core README says Safe owners are limited to the scope set forth in the BORG’s legal documents and the approval of the adjacent DAO, which is strong evidence that MetaLeX’s real product is a bounded-governance operating layer rather than just legal commentary.
  • The borgCore.sol source is useful because it makes the enforcement posture concrete: recipient limits, method whitelists, cooldowns, parameter constraints, director-signature checks, and legal-agreement storage are first-class state, not vague governance promises.
  • The Vision Paper makes the broader ambition explicit: MetaLeX wants law and code to interoperate as an operating system for cybernetic organizations. That is analytically useful, but it also suggests a caution: the project is still partly an architecture-and-services umbrella, so the real control surfaces may depend heavily on who configures the templates, contracts, and surrounding legal entities in practice.
• Whitepaper: A first-party MetaLeX Vision Paper exists on the project Substack, but it is closer to a manifesto / concept paper than a narrow protocol specification. The strongest reviewed primary materials are summarized in ../whitepapers/metalex-primary-sources-2026-05-19.md.
• Sources:
  • https://metalex-docs.vercel.app/
  • https://metalex-docs.vercel.app/faq
  • https://metalex-docs.vercel.app/borg/borg-auth
  • https://raw.githubusercontent.com/MetaLex-Tech/borg-core/main/README.md
  • https://raw.githubusercontent.com/MetaLex-Tech/borg-core/main/src/borgCore.sol
  • https://metalex.substack.com/p/the-metalex-whitepaper

Internal linkages

• Closest smart-account substrate and execution-policy sibling: safe

• Governance-policy neighbor where durable authority also lives in role design, modules, and execution gates: llama

• Constitutional contrast where treasury legitimacy comes from credible minority exit rather than rich policy wrappers and legal-engineering layers: molochdao

• Last reviewed: 2026-05-19 UTC