Citation and authorship

Llewellyn van der Merwe. Joomla Component Builder: Contextual Compilation Architecture. Edition 1.0.0. Vast Development Method, 16 September 2026.

Publication: architecture.joomlacomponentbuilder.com. Source: joomengine/architecture.

The author is the originator and principal implementer of the JCB architecture described. Research, editorial, and tooling assistance support the author's account. The publication does not present itself as an external certification of the project.

Machine-readable citation#

The repository provides CITATION.cff. A BibTeX form is:

@techreport{vandermerwe2026jcbarchitecture,
  author      = {van der Merwe, Llewellyn},
  title       = {Joomla Component Builder: Contextual Compilation Architecture},
  institution = {Vast Development Method},
  year        = {2026},
  month       = sep,
  version     = {1.0.0},
  url         = {https://architecture.joomlacomponentbuilder.com},
  note        = {Technical white paper, edition of 16 September 2026}
}

Citing an individual mechanism#

For a specific result, name the article and section in addition to the edition. For example, a citation of ordered placeholder replacement should identify Deferred execution and substitution semantics and its action definitions. A citation of the Greeting trace should identify the field article and the pinned blueprint/product commits.

The article manifest records article metadata, canonical and Markdown addresses, and source hashes. The exact Markdown alternate provides the article's source text. The complete edition archive preserves the corpus together for offline examination.

A moving publication URL and an immutable repository revision answer different needs. The former locates the current reading interface; the latter fixes the text used in a particular analysis. Record a commit or source hash when exact reproducibility matters.

Citing implementation behavior#

Use the official implementation paths and revisions in the source map. The publication's explanatory wording and the compiler source are separate works. Citing the paper for an architectural interpretation does not replace citing a particular implementation when discussing its exact branch behavior.

The integrated extrusion capture has its own edition scope and file fingerprints. Do not attach its behavior to an earlier core revision that lacks those files. Edition scope

Citing engineering measurements#

The repeated JCB self-build figure is an engineering record from the author. Its approximate blueprint size, output size, and elapsed time should be kept together with their scope and additional reusable inputs. The separate Hello World inventory has exact pins and an explicit counting rule.

A source-file inventory is not a newly executed compiler benchmark. A hypothetical seconds-per-line labor estimate is not measured development time. Performance, accounting

Attribution of related work#

The bibliography credits the prior research and official documentation used to explain related mechanisms. The author's independent development history is retained in provenance. Neither independent rediscovery nor retrospective similarity should be converted into an unsupported claim of first invention or direct influence.

Applications generated by JCB retain their own authorship. The Service Directory's application attribution, third-party library notices, and Joomla's attribution remain distinct from the authorship of this architectural white paper.