# Technology history

`kaal:entity:technology-history`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `technology-history`. 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, 2017 to 2021.

**2017**

- [2939127-007](https://wulfkaal.github.io/claims/2939127-007) [mechanism/argued] -- The first generations of Legal Tech did not reduce demand for lawyers; by making far greater volumes of legal material available faster, they created a need for additional lawyers to evaluate that material.
  > in fact, created the need for additional lawyers to evaluate the new and increasing numbers of legal materials made available faster and more easily accessible by technology.
  Mark Fenwick, Wulf A. Kaal, Erik P. M. Vermeulen, Legal Education in the Blockchain Revolution (2017). SSRN: https://ssrn.com/abstract=2939127

**2021**

- [3808859-001](https://wulfkaal.github.io/claims/3808859-001) [mechanism/asserted] -- The ethos of interoperability in software development arose from a survival calculation rather than altruism: developers recognized that software which could not work across platforms would not survive.
  > In turn, the realization in the software development community that interoperability of software means survivability, gave rise to an ethos of interoperability.
  Wulf A. Kaal, Decentralization – Why We Need Technology Infrastructure Upgrades (2021). SSRN: https://ssrn.com/abstract=3808859

## 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/technology-history.md | sha256sum

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