# Dynamic design

`kaal:entity:dynamic-design`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `dynamic-design`. 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

2 claims across 2 works, 2021 to 2021.

**2021**

- [3782193-037](https://wulfkaal.github.io/claims/3782193-037) [mechanism/argued] -- The separation of powers works because it makes each branch's power derive from the others, harnessing the natural human competitive impulse to stop any branch from usurping power not enumerated in the Constitution, which is what the checks and balances prevent.
  > In the cyclical system, the powers of each branch derive from the others. The natural human competitive impulse is har- nessed to prevent any branch from usurping power not enumerated in the Constitu- tion, the checks and balances to prevent centralization of power.
  Craig Calcaterra, Wulf A. Kaal, Historical Sketches of Centralization vs. Decentralization (2021). SSRN: https://ssrn.com/abstract=3782193
- [3782205-008](https://wulfkaal.github.io/claims/3782205-008) [condition/asserted] -- Keeping decentralized networks running productively requires a dynamic design with checks and balances combined with the incentive design insights of game theory.
  > A dynamic design with checks and balances and the incentive design insights of game theory are necessary to keep these networks running productively.
  Craig Calcaterra, Wulf A. Kaal, Eight Institutions for the Evolution of Decentralization (2021). SSRN: https://ssrn.com/abstract=3782205

## 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/dynamic-design.md | sha256sum

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