# Control

`kaal:entity:control`

**Status.** derived

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

6 claims across 3 works, 2021 to 2025.

**2021**

- [3782198-027](https://wulfkaal.github.io/claims/3782198-027) [normative/argued] -- Contrary to the common engineering view that automated processes remove regulation, the purpose of smart contracts is to deliver much more fine grained regulation and more control, not less.
  > In fact, the purpose of smart contracts is to give much more fine-grained regulation, more control, not less.
  Craig Calcaterra, Wulf A. Kaal, Contemporary Decentralization (2021). SSRN: https://ssrn.com/abstract=3782198
- [3936876-005](https://wulfkaal.github.io/claims/3936876-005) [definitional/asserted] -- Custody of a digital asset is not physical possession but ownership and control over a digital asset wallet, which in practice means holding the private keys and bearing responsibility for keeping the funds safe.
  > Custody of digital assets is typically associated with ownership and control over a digital asset wallet and its assets. Such ownership and control over a digital asset wallet typically means holding the private keys and the responsibility of keeping funds safe.
  Wulf A. Kaal, Hayley Howe, Custody of Digital Assets (2021). SSRN: https://ssrn.com/abstract=3936876

**2025**

- [5886342-016](https://wulfkaal.github.io/claims/5886342-016) [condition/asserted] -- Digital ownership under the Codex is control dependent: it requires direct or indirect control over the digital object, so ownership without any technical control is not recognised.
  > (3) Digital Ownership requires direct or indirect Control over the Digital Object.
  Furrer Andreas, Wulf A. Kaal, Stephan D. Meyer, Universal Digital Law Codex (UDLC) (2025). SSRN: https://ssrn.com/abstract=5886342
- [5886342-018](https://wulfkaal.github.io/claims/5886342-018) [mechanism/asserted] -- First ownership of a digital object arises from a factual event rather than from registration or grant: it is established once the first legal identity acquires digital control of that object.
  > The first digital ownership on a Digital Object is es- tablished once the first Legal Identity acquires Digi-
  Furrer Andreas, Wulf A. Kaal, Stephan D. Meyer, Universal Digital Law Codex (UDLC) (2025). SSRN: https://ssrn.com/abstract=5886342
- [5886342-021](https://wulfkaal.github.io/claims/5886342-021) [condition/asserted] -- Pledging a digital object requires the pledgor to hand over digital control, either to the pledgee, to a third party, or to a digital program capable of exercising that control, so the security interest is perfected by control rather than by filing.
  > (2) In order to pledge a Digital Object, the pledgor shall transfer the Digital Control to either the pledgee, a third party, or a digital program capable of exercising Digital Control.
  Furrer Andreas, Wulf A. Kaal, Stephan D. Meyer, Universal Digital Law Codex (UDLC) (2025). SSRN: https://ssrn.com/abstract=5886342
- [5886342-023](https://wulfkaal.github.io/claims/5886342-023) [mechanism/asserted] -- Rights embedded in a Digital Transfer of Rights Object are exercisable only by the digital controller of that object, which is what lets the transfer of control function as the transfer of the underlying entitlement.
  > be exercised by the Digital Controller of the DTRO.
  Furrer Andreas, Wulf A. Kaal, Stephan D. Meyer, Universal Digital Law Codex (UDLC) (2025). SSRN: https://ssrn.com/abstract=5886342

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

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