# Summary
Firm protocol is our interpretation of what the software core of internet-native companies should be. The protocol is non-custodial and allows founders to create and run a company whose basic rules and rights are controlled and enforced with code. Firm protocol is open source and licensed under GPL-3.0. You can check the repo here: [firm-org/firm-protocol](https://github.com/firm-org/firm-protocol) Companies running on Firm have stronger guarantees and tighter controls than fiat companies. A fiat company (a company with a legal core) has to rely on the threat of post-hoc legal repercussions for misconduct and breaches of trust. Internet-native companies can be very explicit about how power is delegated all the way from shareholders and companies are inherently transparent due to the fact it runs on a public blockchain. At the same time, as Firm companies can also opt into having an off-protocol legal entity (bringing the same level of protections of a fiat company), and the nature of how companies are typically formed, we find ourselves in an environment which isn’t as adversarial as a DAO (e.g. a DAO that controls a large DeFi protocol needs to be designed in a highly adversarial way). It is with these principles that Firm protocol has been designed in a way to always respect an explicit delegation of power from shareholders but enabling a sane operating model which companies need to be effective. Firm protocol v1 is a system of smart contracts which revolves around two main feature groups: * **Captable and basic corporate governance:** the captable of the company is fully on-chain and shares are represented with fungible tokens for different classes of stock. Shareholders have the right to elect the board of directors on-chain (resulting in the addition/removal from the main company multisig). * **Hustle-free use of funds with on-chain guarantees:** in the same way that shareholders delegate their authority into the board, the board is able to delegate partial spending ability to the people running the daily operations of the company. This authority delegation pattern is recursively applied so that bucketed spending authority can go down to the lowest level of the company (e.g. a junior engineer can have a budget for out of pocket technical expenses, with an implicit authority delegation all the way from shareholders) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.firm.org/firm-protocol-v1/summary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.