Publish the JCB contextual compilation architecture white paper

.github/workflows/publication.yml

@@ -2,7 +2,7 @@ name: Publication
 
 on:
   push:
-    branches: [main, vdmt-formal-specification]
+    branches: [main]
   pull_request:
   workflow_dispatch:
 
@@ -16,33 +16,35 @@ concurrency:
 jobs:
   build:
     runs-on: ubuntu-latest
-    timeout-minutes: 20
+    timeout-minutes: 25
     steps:
       - uses: actions/checkout@v6
         with:
           persist-credentials: false
       - name: Archive reviewed source
-        run: git archive --format=zip --prefix=vdmt/ HEAD > vdmt-source.zip
+        run: git archive --format=zip --prefix=jcb-architecture/ HEAD > jcb-architecture-source.zip
       - name: Retain source edition
         uses: actions/upload-artifact@v7.0.1
         with:
-          name: vdmt-source
-          path: vdmt-source.zip
+          name: jcb-architecture-source
+          path: jcb-architecture-source.zip
           retention-days: 14
       - uses: actions/setup-python@v6
         with:
           python-version: '3.12'
           cache: pip
       - name: Install publication dependencies
         run: python -m pip install -r requirements.txt -r requirements-dev.txt
-      - name: Test abstract contracts and publication tooling
+      - name: Test architectural mechanisms and publication tooling
         run: python -m unittest discover -s tests -v
-      - name: Run the complete reference demonstration
+      - name: Run the reference demonstration
         run: |
           mkdir -p validation
           python examples/demo.py > validation/reference-demo.json
       - name: Acquire versioned browser assets
         run: python scripts/vendor.py
+      - name: Verify pinned blueprint and product evidence
+        run: python scripts/prepare_evidence.py
       - name: Build Markdown-first publication
         run: python scripts/build.py
       - name: Archive built publication for review
@@ -51,15 +53,15 @@ jobs:
         run: python scripts/check_site.py
       - name: Install browser
         run: python -m playwright install --with-deps chromium
-      - name: Check rendering, navigation, math, and theme behavior
+      - name: Check rendering, navigation, math, and theme behaviour
         run: python scripts/browser_check.py
       - name: Retain publication and review evidence
         if: always()
         uses: actions/upload-artifact@v7.0.1
         with:
-          name: vdmt-publication
+          name: jcb-architecture-publication
           path: |
-            vdmt-site.zip
+            jcb-architecture-site.zip
             validation/
             vendor/manifest.json
           if-no-files-found: warn

.gitignore

@@ -4,6 +4,8 @@ __pycache__/
 site/
 vendor/
 validation/
-vdmt-source.zip
-vdmt-site.zip
+jcb-architecture-source.zip
+jcb-architecture-site.zip
 .DS_Store
+
+web/static/evidence/

AUTHORS.md

@@ -1,7 +1,9 @@
-# Authorship and contribution record
+# Authorship
 
-**Llewellyn van der Merwe** — originator of the architecture, author of the originating JCB implementation, source of the practical account and independent-development testimony, and intended author/publisher of the VDMT research exposition through Vast Development Method.
+**Llewellyn van der Merwe** is the author of this white paper and the originator and principal implementer of the Joomla Component Builder architecture it describes.
 
-This 2026 documentation edition and its original reference implementation were prepared with AI assistance for the originator's review. The publication does not imply that a degree has been awarded, that an institution has endorsed it, or that independent peer review has been completed.
+**Vast Development Method** is the publisher and the engineering organisation supporting the work. Research, editorial, and tooling assistance support the author's account; they do not replace its authorship or present the publication as an external assessment of the project.
 
-Earlier mathematical and architectural work is credited in `DOCS/foundations/related-work.md` and `DOCS/reference/bibliography.md`. JCB contributors retain attribution for their work. Future contributors should be recorded with their actual contributions rather than silently incorporated into a sole-authorship claim.
+The account of independent development is the author's history of building and maintaining JCB. Related mathematical and software-engineering work is credited as prior work and retrospective correspondence, without implying an influence that did not occur.
+
+The publication's authorship does not imply authorship of Joomla, third-party libraries, cited research, or every application generated with JCB. Those works retain their own attribution and licenses.

CHANGELOG.md

@@ -1,9 +1,11 @@
-# Changelog
+# Publication history
 
-## 0.1.0 — 15 September 2026
+## 1.0.0 — 16 September 2026
+
+Recast the publication as **Joomla Component Builder: Contextual Compilation Architecture**. The compiler, portable blueprint graph, entity discovery, structured intent, extrusion, and complete generated products define the scope. The mathematical exposition follows the implemented operations and is linked to public examples and source correspondence.
 
-Initial formal documentation edition of Vast Development Method Theory. Separates the language-independent framework from the pinned JCB case study; defines contextual closure, scoped derivation, occurrence identity, staged materialization, and partial editorial reconciliation; supplies conditional propositions, counterexamples, a reference model, conformance tests, related work, and an experimental program.
+Publication identity moves to `architecture.joomlacomponentbuilder.com` and `joomengine/architecture`. The Markdown-first reading experience, small VDM mark, author attribution, and licenses are retained; the large homepage wordmark is removed.
 
-Adds a Markdown-first publication for theory.vdm.io with per-article Markdown alternates, a complete research corpus, machine-readable manifests, light/dark/system themes, search, mathematical rendering, diagrams, and a gated GitHub Pages workflow.
+## 0.1.0 — 15 September 2026
 
-Historical provenance is recorded separately: the originating public JCB implementation is dated 30 January 2016. This changelog does not backdate the 2026 manuscript or claim every modern feature existed at the root commit.
+The first manuscript collected the contextual-reuse and staged-generation account, a source study, mathematical preliminaries, and publication tooling. Its reviewed source is retained in Git history at commit `c833d39f606d2b237eeaecbd5c41a350dde823cb`. This edition replaces its framing and article structure; it does not backdate the present text or later implementation features.

CITATION.cff

@@ -1,30 +1,27 @@
 cff-version: 1.2.0
-message: "Please cite the white paper when discussing VDMT; cite a pinned source revision for implementation claims."
-title: "Vast Development Method Theory: Contextual Recollection, Staged Synthesis, and Persistent Editorial Reconciliation"
+message: "Please cite this architectural white paper when using its explanatory account or formalisation."
+type: article
+title: "Joomla Component Builder: Contextual Compilation Architecture"
+abstract: >-
+  A compiler-centred account of structured intent, portable blueprint graphs,
+  entity discovery, contextual classification, intermediate stores, deferred
+  processing, staged generation, extrusion, and regeneration in Joomla Component
+  Builder. The paper develops language-neutral operational and mathematical
+  descriptions with source correspondence and public worked examples.
 authors:
   - family-names: "van der Merwe"
     given-names: "Llewellyn"
-version: 0.1.0
-date-released: 2026-09-15
-url: "https://theory.vdm.io"
-repository-code: "https://github.com/vast-development-method/theory"
-license:
-  - CC-BY-4.0
-  - MIT
+    affiliation: "Vast Development Method"
+version: 1.0.0
+date-released: 2026-09-16
+url: "https://architecture.joomlacomponentbuilder.com"
+repository-code: "https://github.com/joomengine/architecture"
+license: CC-BY-4.0
 keywords:
-  - contextual closure
-  - staged synthesis
-  - round-trip engineering
   - compiler architecture
-  - scoped memory
-preferred-citation:
-  type: report
-  title: "Vast Development Method Theory: Contextual Recollection, Staged Synthesis, and Persistent Editorial Reconciliation"
-  authors:
-    - family-names: "van der Merwe"
-      given-names: "Llewellyn"
-  year: 2026
-  version: 0.1.0
-  institution:
-    name: "Vast Development Method"
-  url: "https://theory.vdm.io"
+  - model-driven engineering
+  - contextual compilation
+  - code generation
+  - portable blueprints
+  - dependency resolution
+  - Joomla Component Builder

CONTRIBUTING.md

@@ -1,27 +1,25 @@
-# Contributing to VDMT
+# Contributing to the architectural publication
 
-The paper welcomes criticism, counterexamples, independent implementations, source corrections, and reproducible measurements. Agreement with the author's hypotheses is not a condition of contribution.
+This repository documents Joomla Component Builder's architecture. Proposed compiler changes belong in the official implementation repository; the white paper should explain implemented behaviour rather than quietly prescribe a different system.
 
-## One article, one source
+## Editorial standard
 
-Write each article in `DOCS/` as UTF-8 Markdown. Include YAML front matter with `title`, `description`, `section`, `order`, and `evidence`. Give the page one H1, then descriptive H2/H3 sections. Use ordinary relative `.md` links, fenced code, and `$...$` / `$$...$$` mathematics. Do not maintain separate HTML prose or separate hand-edited Markdown exports. The build creates both from the same source and checks their correspondence.
+Keep the compiler at the centre. Connect a mechanism's problem, operation, state, mathematical description, worked example, and source correspondence. Prefer precise ordinary terminology before introducing specialised notation. Define symbols once and use them consistently.
 
-A new nuance should receive a focused article when it has its own definitions, assumptions, example, failure conditions, or evidence. Link it to its prerequisites and implications. Do not split a sentence into several pages merely to inflate the count.
+Preserve the distinction between definitions, contextual occurrences, intermediate contributions, emitted artifacts, and repository indexes. Describe the actual ordering and effects of the implementation. Do not infer universal confluence, transactional publication, immutable stores, or a general inverse compiler from mechanisms that do not supply those guarantees.
 
-## Evidence discipline
+Describe measured builds with their input and output boundaries. Do not present generated volume as manually written code, or convert repeated engineering measurements into conjectures. Distinguish an archival artifact comparison from a fresh runtime compilation.
 
-Label claims using the taxonomy in `DOCS/foundations/epistemic-status.md`. Source observations require a repository revision, path, relevant method or line range, and an explanation of what was inspected. Experiments require input and environment descriptions and a procedure that another researcher can run. Propositions require all assumptions and an argument; a test does not become a proof by passing. Cite prior work at the point of comparison.
+## Sources and references
 
-Do not silently promote a proposed feature to an observed JCB property. Do not equate the historical public implementation date with the date of this manuscript. Do not use a marketing claim or a generated line count as evidence of cognitive optimality.
+Compiler citations use the official Joomla Component Builder repository and immutable revisions. A cited file must support the nearby statement. Newer implementation coverage must identify its edition scope rather than attribute absent code to an older revision. Public examples and documentation retain their own repository identities.
 
-## Review workflow
+Credit primary research and official documentation for architectural correspondences. Preserve independent development history without inventing either intellectual influence or historical priority. Comparisons should explain mechanisms, not rank products.
 
-Create a branch from `main`. Make focused commits, run the repository tests, build the publication, and open a pull request explaining substantive changes. A formal change should state which definitions and propositions depend on it. A source correction should state whether it affects an implementation observation or the abstract specification. A historical correction must retain a transparent record of the prior wording.
+## Article and website contract
 
-PRs are checked but never deployed to the public domain. Only an approved merge to `main` publishes. Large changes to definitions should increment the specification version and explain compatibility.
+Every article belongs in `DOCS/`, has YAML metadata, exactly one first-level heading, a stable path, a description, a section, and a reading order. Relative links to other articles use `.md` paths. Inline mathematics uses `$...$`, display mathematics uses `$$...$$`, and diagrams use fenced `mermaid` blocks. Explain figures in prose as well.
 
-## Rights and attribution
+The build must publish exact source bytes as the Markdown alternate. Search, downloads, the article manifest, citation metadata, and canonical URLs must all agree with `site.json`. Keep navigation keyboard-accessible and mathematical content usable on narrow screens. Retain the small VDM mark and text-based JCB architecture identity; do not restore the oversized homepage wordmark.
 
-Contribute only material you have the right to share. Contributions to original paper text and diagrams are offered under CC BY 4.0; original software contributions under MIT. Contributors retain their own copyright unless separately agreed. Preserve upstream rights for quotations and dependencies. Do not add invented author identities, institutional affiliations, degrees, ORCID identifiers, DOIs, or publication dates.
-
-The theory's originator is Llewellyn van der Merwe. Maintain that attribution without erasing the contributions of collaborators or the priority of related published work.
+Run the complete checks in `README.md`. Submit coherent commits on a review branch and record the validation scope in the pull request. Do not merge or change production hosting as a side effect of editorial work.

DOCS/404.md

@@ -1,13 +1,15 @@
 ---
-title: Page not found
-description: Return to the VDMT reading guide or search the publication for the intended article.
-section: Reference
+title: Article not found
+description: Find the current JCB architecture article through the reading guide or publication search.
+section: Overview
 order: 999
 listed: false
 evidence: Publication navigation
 ---
-# Page not found
+# Article not found
 
-The requested article is not available at this address. Return to the [publication home](index.md), use the [reading guide](reading-guide.md), or search by concept in the navigation.
+This address does not identify an article in the current edition.
 
-Every published article has a corresponding Markdown source. A missing or moved article should not be replaced with a guessed scientific claim. The [publication guide](reference/publication.md) explains the stable HTML and Markdown URL structure.
+Start with the [architecture overview](index.md), the [white paper](white-paper.md), or the [reading guide](reading-guide.md). Publication search covers every article's title and full text. The [source map](reference/source-map.md) locates implementation references, and the [glossary](reference/glossary.md) locates terminology.
+
+Earlier editions remain in the repository history. [Publication details](reference/publication.md)