# Conways law

`kaal:entity:conways-law`

**Status.** derived

This node is assembled mechanically from the 3 claims that carry the concept tag `conways-law`. It is a roster of what the corpus says under this term. It is **not** an adjudicated definition: no single statement here has been ruled canonical, and no first-appearance call has been made. Read the claims and judge for yourself.

## Every claim under this term

3 claims across 3 works, 2020 to 2021.

**2020**

- [3652481-011](https://wulfkaal.github.io/claims/3652481-011) [mechanism/argued] *(failure mode)* -- DAO developers are themselves subject to path dependencies that undermine the evolution of decentralized DAO designs, because the communication structures of the developing organization invariably shape future designs.
  > DAO developers are also subject to path dependencies which undermines the evolution of decentralized DAO designs. The communication structures in organizations will invariably influence future designs.
  Wulf A. Kaal, Decentralized Autonomous Organizations – Internal Governance and External Legal Design (2020). SSRN: https://ssrn.com/abstract=3652481

**2021**

- [3808852-017](https://wulfkaal.github.io/claims/3808852-017) [failure/argued] *(failure mode)* -- DAO developers are subject to path dependencies that undermine the evolution of decentralized DAO designs, because the communication structures of the organizations that design systems invariably shape future designs.
  > DAO developers are also subject to path dependencies which undermine the evolution of decentralized DAO designs. The communication structures in organizations will invariably influence future designs.11
  Wulf A. Kaal, Decentralization and Feedback Effects (2021). SSRN: https://ssrn.com/abstract=3808852
- [3995709-010](https://wulfkaal.github.io/claims/3995709-010) [empirical/evidenced] -- Organizational metrics, such as the number of developers working on a component, organizational distance between developers, and organizational code ownership, are better predictors of defect proneness than traditional metrics like churn, complexity, coverage, dependencies, and pre release bug measures.
  > including the number of developers working on a component, organizational distance between developers, and organizational code ownership, are "better predictors of defect-proneness than traditional metrics like churn, complexity, coverage, dependencies, and pre-release bug measures."45
  Wulf A. Kaal, How DAOs Optimize Open-Source Code Reviews and Create Open-Source Standards (2021). SSRN: https://ssrn.com/abstract=3995709

## Verify

Every claim above resolves to a record carrying a verbatim source quote, the sha256 of the source PDF, and a preformatted citation. Nothing here asks to be taken on trust.

    curl -s https://wulfkaal.github.io/entities/conways-law.md | sha256sum

**Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.