--- title: "Transparency" description: "You show how the thing works: the source, the roadmap, the pricing logic, the incident history." canonical: https://moa.giglabo.com/strategies/transparency/ locale: en --- # Transparency > Markdown twin of https://moa.giglabo.com/strategies/transparency/ — the same content as the HTML page, a fraction of the bytes. > Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL. > Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt Category: Collaboration · Role: Holds · Depth: 3 Gist: visible inner workings that build trust ## Moats - [#21 Community](https://moa.giglabo.com/moats/21/) (direct, depth 2 · Excavator) — Contributors, documenters and defenders gather around a project they can read, and they gather around the reference, not the clone; that labour and loyalty is the community moat. - [#20 Developer ecosystem](https://moa.giglabo.com/moats/20/) (direct, depth 3 · Drill rig) — Third parties build plugins, integrations and businesses on a platform whose internals and roadmap they can inspect, and their investment locks them and their users to you. ## Summary You show how the thing works: the source, the roadmap, the pricing logic, the incident history. Openness costs a rival nothing to read, so the edge is not in what is hidden. It is in who arrives because they can see: contributors who build on you and users who trust what they can inspect. It holds through the community and the developer ecosystem it attracts. ## How it works The mechanism is a trade of secrecy for participation. Once the inner workings are visible, three groups act on them. Users verify claims themselves instead of taking your word, which removes the cost of trust. Developers build on you because they can read the interface and see the roadmap will not pull the rug. Contributors fix, extend and document, because open work is work they can put their name on. The rival's problem is not that they cannot copy the code — they can. It is that the crowd around the code does not come with it. Trust accrues to the party that was open first and stayed open; plugins, forks and documentation accrue to the reference project, not to the clone. The clone starts with the artefact and none of the people. Openness that stops — a licence change, a hidden roadmap, a closed marketplace — reverses the mechanism in a season, because everything the crowd gave was given on the condition of seeing. ## Why it holds — or only takes This holds, though not through the artefact — an open artefact is by definition copyable. It holds through what openness attracts. Community, depth 2: the people who fix, document and defend a project do so because they can see it, and they identify with the reference rather than the copy. Developer ecosystem, depth 3: third parties invest in a platform whose internals they can inspect, and their plugins and businesses become your moat. Developer ecosystem is the deeper of the two, partly reachable alone, resistant to AI. The condition is that the openness be real and stay real; a licence change is the fastest way to lose both. ## Do you have it - You already have this if strangers send you fixes, docs and translations you did not ask for. - Third-party plugins for your product outnumber the features you shipped yourself. - Prospects quote your public incident history or pricing page back to you as a reason to buy. - A fork of your project exists, and nobody uses it. ## How to dig it - Open the interface and the roadmap before rivals do, and keep a public changelog that admits mistakes. - Publish pricing, uptime and post-mortems where a buyer can find them without asking sales. - Give contributors credit and a path to maintainer status, so the crowd has something to earn. - Choose a licence you can live with for a decade; changing it later is what ends the moat. ## How it erodes - A compatible fork takes the developer ecosystem: the plugins run on the clone from day one. - A licence change or a closed marketplace reads as betrayal, and contributors move to the fork in a month. - A large cloud vendor ships your open code as a managed service and keeps the customers. - AI reads your public internals and helps a rival rebuild them, so the artefact's head start shrinks to nothing. ## Solo, without capital This is the most natural moat for a single person without capital: build in the open, publish the source, the roadmap and the numbers, and let the crowd do what a team would. Community is reachable alone and resistant to AI. The developer ecosystem is only partly yours to build — it needs a platform others can earn on, which takes years and a product big enough to host their businesses. Expect forks; the moat is the people who stay. What the matrix says of its moats: - [#21 Community](https://moa.giglabo.com/moats/21/) — Solo: ✓ solo-reachable · Capital: ○ low · AI: ↑ AI-resistant · Rent: ✗ not for sale - [#20 Developer ecosystem](https://moa.giglabo.com/moats/20/) — Solo: ~ partly · Capital: ◐ medium · AI: ↑ AI-resistant · Rent: ~ partly ## In nature, in business Nature: — Business: open-source software - **Linux** — The kernel's source, mailing lists and decisions are public, and the contributors and companies that gathered around it never moved to any closed rival. - **Buffer** — The company published every employee's salary and its revenue dashboard, and the openness became the reason people trusted and talked about it. - **WordPress** — Open code and an open plugin model drew tens of thousands of themes and plugins, each a reason to choose it and a reason not to leave. ## Combines with - [Distributed ownership](https://moa.giglabo.com/strategies/distributed-ownership/) — Owners need open books; transparency is how a distributed stake becomes a felt one. - [Emergence](https://moa.giglabo.com/strategies/emergence/) — A crowd contributes when it can see the rule that turns its work into the whole. - [Authenticity](https://moa.giglabo.com/strategies/authenticity/) — Visible provenance is what makes traceability to the source checkable rather than claimed. - [Composability](https://moa.giglabo.com/strategies/composability/) — Open interfaces are what let others assemble your parts into their own configurations. [This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=transparency) [Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=transparency,distributed-ownership,emergence,authenticity,composability) ## Fights with - [Secrecy](https://moa.giglabo.com/strategies/secrecy/) — Protected knowledge and visible inner workings are opposite bets; you cannot hold both on the same artefact. - [Obscurity](https://moa.giglabo.com/strategies/obscurity/) — A strategy of staying unknown cannot publish its internals for the world to read. [Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=transparency,secrecy,obscurity) ## Source Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/ ## Related - HTML version of this page: https://moa.giglabo.com/strategies/transparency/ - Русский: https://moa.giglabo.com/ru/strategies/transparency/ - Previous: Distributed ownership — https://moa.giglabo.com/strategies/distributed-ownership/ - Next: Union — https://moa.giglabo.com/strategies/union/ - Atlas: https://moa.giglabo.com/ - Catalogue: https://moa.giglabo.com/moats/ - Calculator: https://moa.giglabo.com/calculator/ - Strategies: https://moa.giglabo.com/strategies/ - Site map for agents: https://moa.giglabo.com/llms.txt