# Functional equivalence

`kaal:entity:functional-equivalence`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `functional-equivalence`. 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 1 works, 2025 to 2025.

**2025**

- [5886342-013](https://wulfkaal.github.io/claims/5886342-013) [definitional/asserted] -- A signature under the Codex is defined functionally as the technical proof of the link between an identifier and a piece of digital information, not as a handwritten or format specific formality.
  > (1) The Signature is the technical proof between the Identifier and any Digital Information.
  Furrer Andreas, Wulf A. Kaal, Stephan D. Meyer, Universal Digital Law Codex (UDLC) (2025). SSRN: https://ssrn.com/abstract=5886342
- [5886342-027](https://wulfkaal.github.io/claims/5886342-027) [condition/asserted] -- Contracts under the Codex are form free by default: formation does not require any particular form unless applicable mandatory law imposes one that cannot be substituted by the principle of functional equivalence.
  > formation of a contract does not require any particu-
  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/functional-equivalence.md | sha256sum

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