---
title: Rights and reuse
ndescription: Publication and executable companion licensing.
description: Attribution and license boundaries for the white paper, executable examples, branding, and cited implementation.
section: Reference
order: 96
evidence: Repository license notices and license texts
---
# Rights and reuse

The original prose, mathematical exposition, and authored diagrams in this publication are licensed under **Creative Commons Attribution 4.0 International (CC BY 4.0)**. The original publication tooling and executable reference examples are licensed under **MIT**. The repository's license and notice files identify the applicable material.

Author: **Llewellyn van der Merwe**. Publisher: **Vast Development Method**.

## Reusing the explanatory work

CC BY 4.0 permits sharing and adaptation, including commercial use, subject to its terms. Give appropriate credit, link the license, and indicate changes. Attribution must not suggest endorsement of an adaptation by the author or publisher. The [license deed](https://creativecommons.org/licenses/by/4.0/) summarizes the terms; the [legal code](https://creativecommons.org/licenses/by/4.0/legalcode) is authoritative.

A useful attribution names the paper, author, edition, publication address, and license. [Citation examples](citation.md)

## Reusing the executable companion

The original reference mechanisms and website tooling are covered by the repository's MIT license notice. Retain the required copyright and permission notice when redistributing covered software. The executable companion is a small explanatory implementation; its license does not relicense the Joomla Component Builder source referenced by the paper.

## Cited code and third-party material

JCB, Joomla, Powers, libraries, application examples, and browser dependencies retain their respective licenses and notices. A source link or discussion in this white paper does not transfer those rights or imply that all cited software is under the paper's license.

VDM branding is retained as publisher identity. The explanatory-text license does not grant permission to represent an unrelated project as VDM or as an endorsed JCB implementation. Third-party trademarks and marks remain with their owners.

## Implementing the architectural ideas

The publication is intended to help engineers understand and reuse the described approach. Its license governs the covered expression and software. It is not presented as exclusive ownership of every mathematical principle, design pattern, or independently implemented algorithm discussed in the account.

An implementation that copies covered code or prose should follow the applicable license for that material. An implementation that uses a cited third-party library must follow that library's terms separately. The [bibliography](bibliography.md) and [source map](source-map.md) keep those origins visible.

## Preserving attribution accurately

The white paper's author, the compiler's originator, and the authors of generated applications are not automatically the same person. The Service Directory example retains its own application attribution. Research references identify earlier work without implying that it was part of the original developer's influences.

The repository's `LICENSE`, `LICENSES/MIT.txt`, and `NOTICE.md` remain the primary local notices. This page explains the publication's intended boundaries and does not replace those texts.