# Joomla Component Builder: Contextual Compilation Architecture

> Structured intent · Contextual compilation · Portable blueprints

A compiler-centred architectural white paper by Llewellyn van der Merwe, published by Vast Development Method. Structured intent, portable blueprint graphs, contextual compilation, extrusion, and native extension products.

## Articles

- [Joomla Component Builder Architecture](https://architecture.joomlacomponentbuilder.com/markdown/index.md): A compiler-centred white paper on structured intent, portable blueprints, contextual processing, and complete extension generation.
- [Contextual Compilation Architecture — White Paper](https://architecture.joomlacomponentbuilder.com/markdown/white-paper.md): The integrated account of JCB's structured intent, portable definition graphs, contextual contributions, deferred work, staged generation, and reconstruction.
- [Reading guide](https://architecture.joomlacomponentbuilder.com/markdown/reading-guide.md): Routes from a concrete generated field to the compiler architecture, its mathematics, and its implementation in another language.
- [The architectural object](https://architecture.joomlacomponentbuilder.com/markdown/foundations/architecture.md): The complete object transformed by contextual compilation, from reusable definitions and use-site settings to coordinated output artifacts.
- [Structured intent as compiler input](https://architecture.joomlacomponentbuilder.com/markdown/foundations/structured-intent.md): How GUI-authored choices form a domain-specific application description whose consequences are supplied by compiler rules.
- [Identity across representations](https://architecture.joomlacomponentbuilder.com/markdown/foundations/identity.md): Typed entity keys, local database identities, contextual occurrences, and artifact locations in the JCB lifecycle.
- [Context and interpretation](https://architecture.joomlacomponentbuilder.com/markdown/foundations/context.md): How target, extension, view, role, and binding environment qualify the interpretation and reuse of definitions.
- [The complete development lifecycle](https://architecture.joomlacomponentbuilder.com/markdown/foundations/lifecycle.md): The distinct flows connecting editor intent, portable blueprints, installed artifacts, compilation, and regeneration.
- [Development and provenance](https://architecture.joomlacomponentbuilder.com/markdown/foundations/provenance.md): The author's independent development history, the public source record, and the relationship between implementation history and this formal account.
- [Blueprint representation](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/representation.md): The portable entity graph, its payloads, dependency descriptors, indexes, documentation, and assets.
- [Local-first entity discovery](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/discovery.md): Configured repository search across the supported entity catalogue, with local persistence, request guards, and explicit selection policy.
- [Dependency traversal and bounded discovery](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/dependencies.md): Relationship direction, embedded references, nested subforms, assets, and the queues that complete a requested blueprint graph.
- [Exporting the design graph](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/export.md): From local definitions to normalized repository payloads, relationship closure, generated indexes, and documentation.
- [Import, initialization, and reset](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/import.md): How portable definitions become local working records, with separate initialization and reset policies for shared and owned entities.
- [Assets and repository coordination](https://architecture.joomlacomponentbuilder.com/markdown/blueprints/assets.md): Files, folders, repository indexes, channel configuration, and the boundaries between portable design and external resources.
- [Compiler execution from entry to package](https://architecture.joomlacomponentbuilder.com/markdown/compiler/execution.md): The actual orchestration boundary, including constructor work, initialization, content preparation, file updates, and packaging.
- [Acquiring and enriching the application model](https://architecture.joomlacomponentbuilder.com/markdown/compiler/acquisition.md): Nested loading, reusable definition caches, occurrence-specific processing, and the transition from stored records to compiler-ready data.
- [Semantic classification and routing](https://architecture.joomlacomponentbuilder.com/markdown/compiler/classification.md): How a definition's contextual use produces coordinated contributions to schemas, queries, forms, policies, languages, and generated code.
- [Intermediate stores and information lifecycle](https://architecture.joomlacomponentbuilder.com/markdown/compiler/stores.md): Definition caches, concern-specific builders, dispensers, binding environments, and deferred work as different kinds of retained state.
- [Deferred work and staged readiness](https://architecture.joomlacomponentbuilder.com/markdown/compiler/deferred-work.md): Remembering operations whose prerequisites are established later, including linked admin views and configuration fieldset passes.
- [Binding in ordered stages](https://architecture.joomlacomponentbuilder.com/markdown/compiler/binding.md): Shared and contextual environments, ordered replacement semantics, introduced tokens, and the transition from staged text to file content.
- [Custom code, dispensers, and recovery](https://architecture.joomlacomponentbuilder.com/markdown/compiler/custom-code.md): Prepared code, reusable references, external resources, GUI-linked regions, and fingerprint-based placement across regeneration.
- [Powers, namespaces, and code placement](https://architecture.joomlacomponentbuilder.com/markdown/compiler/powers.md): Stable reusable code identity, local and remote acquisition, recursive dependencies, import aliases, target mappings, and generated source placement.
- [Host, target, and architecture selection](https://architecture.joomlacomponentbuilder.com/markdown/compiler/targets.md): Separating the Joomla installation running JCB from the platform conventions selected for generated output.
- [Extension hooks and observable effects](https://architecture.joomlacomponentbuilder.com/markdown/compiler/events.md): Events, configuration mutation, database reads, filesystem operations, and diagnostics as part of the compiler's operational semantics.
- [Schemas, storage, and update history](https://architecture.joomlacomponentbuilder.com/markdown/generation/schema.md): Field persistence, normalized database properties, derived keys, storage transformations, generated metadata, and migration contributions.
- [Queries, selections, and result structure](https://architecture.joomlacomponentbuilder.com/markdown/generation/queries.md): Dynamic Get definitions, aliases, joins, filters, list state, and generated model code.
- [Fields, forms, layouts, and nested presentation](https://architecture.joomlacomponentbuilder.com/markdown/generation/forms-layouts.md): From field-type definitions and view associations to form attributes, layouts, validation, conditional behaviour, and nested template dependencies.
- [Compiling access-control behaviour](https://architecture.joomlacomponentbuilder.com/markdown/generation/permissions.md): Action declarations, component and record assets, field-level form treatment, configured result redaction, and permission-sensitive storage.
- [Language keys and multilingual output](https://architecture.joomlacomponentbuilder.com/markdown/generation/languages.md): Contextual key construction, source-string collection, translation reuse, target catalogues, and inclusion policy.
- [Routing, API surfaces, and AJAX tasks](https://architecture.joomlacomponentbuilder.com/markdown/generation/routing.md): View-to-route mappings, request keys, target-specific API artifacts, and generated asynchronous controller/model boundaries.
- [Components, modules, and plugins](https://architecture.joomlacomponentbuilder.com/markdown/generation/extensions.md): Shared compiler services and extension-specific acquisition, context, structure, content, and packaging paths.
- [Materialization, packaging, and repository output](https://architecture.joomlacomponentbuilder.com/markdown/generation/materialization.md): Skeletons, file inventories, ordered content updates, late dependency completion, archives, and publication effects.
- [Extrusion from installed applications](https://architecture.joomlacomponentbuilder.com/markdown/extrusion/overview.md): Recovering represented design from installed component artifacts and returning it to the compiler's editable model.
- [Reading artifacts and resolving their meaning](https://architecture.joomlacomponentbuilder.com/markdown/extrusion/analysis.md): Static artifact readers, property-level provenance, configurable precedence, field recovery, and presentation classification.
- [Recovering classes as reusable definitions](https://architecture.joomlacomponentbuilder.com/markdown/extrusion/classes.md): Lexical class recovery, namespace/path interpretation, Power identity, reference reconstruction, and placement in the editable model.
- [Pairing, sharing, and ordered writes](https://architecture.joomlacomponentbuilder.com/markdown/extrusion/pairing.md): Matching recovered candidates to local definitions, retaining user decisions, consolidating shared fields, and writing dependent records in order.
- [Hello World — blueprint to three products](https://architecture.joomlacomponentbuilder.com/markdown/examples/hello-world.md): A public, identity-linked example connecting exported application definitions to a generated component, module, and plugin.
- [The Greeting field across the compiler](https://architecture.joomlacomponentbuilder.com/markdown/examples/field-trace.md): A stable field identifier, its contextual association, and the derived form, schema, index, language, list, and metadata outputs.
- [Tracing GUI code to its destination](https://architecture.joomlacomponentbuilder.com/markdown/examples/custom-code-trace.md): Identifiable authored comments, stored properties, contextual code preparation, generated locations, and reusable README expansion.
- [The module and plugin contexts](https://architecture.joomlacomponentbuilder.com/markdown/examples/extension-trace.md): Following module fields and code and a context-named plugin from portable definitions into distinct native extension structures.
- [Blueprint and product accounting](https://architecture.joomlacomponentbuilder.com/markdown/examples/accounting.md): Reproducible counts of payloads, indexes, descriptions, assets, and generated repository text at fixed revisions.
- [Service Directory and the wider definition ecosystem](https://architecture.joomlacomponentbuilder.com/markdown/examples/service-directory.md): A larger application blueprint/product pair and the surrounding repositories supplying reusable classes, fields, mappings, and distribution definitions.
- [Mathematical vocabulary and domains](https://architecture.joomlacomponentbuilder.com/markdown/formal/notation.md): A common notation for portable identity, occurrences, contexts, contributions, state, artifacts, and representation equivalence.
- [Operational state and execution traces](https://architecture.joomlacomponentbuilder.com/markdown/formal/state.md): A transition-system account of the compiler's stateful orchestration, effectful acquisition, intermediate contributions, and materialized products.
- [Resolution, reachability, and termination](https://architecture.joomlacomponentbuilder.com/markdown/formal/resolution.md): Typed local-first lookup, ordered repository selection, guarded dependency traversal, finite termination, and graph-completion conditions.
- [Context-qualified contributions and consistency](https://architecture.joomlacomponentbuilder.com/markdown/formal/classification.md): Contribution algebra, safe reuse, effect guards, occurrence expansion, and cross-artifact consistency relations.
- [Deferred execution and substitution semantics](https://architecture.joomlacomponentbuilder.com/markdown/formal/staging.md): Prerequisite ordering, phase boundaries, exact ordered replacement, filtered maps, and finite stage completion.
- [Transport equivalence and bounded reconstruction](https://architecture.joomlacomponentbuilder.com/markdown/formal/transport.md): Portable design preservation, local identity remapping, conditional regeneration equivalence, marked-region laws, and extrusion's reconstruction domain.
- [Implementing the architecture in another technology](https://architecture.joomlacomponentbuilder.com/markdown/engineering/implementation.md): A language-neutral decomposition of model authoring, typed discovery, contextual compilation, artifact generation, transport, and reconstruction.
- [Executable reference mechanisms](https://architecture.joomlacomponentbuilder.com/markdown/engineering/reference-model.md): Small executable models of typed resolution, precedence, contextual contributions, deferred work, ordered binding, and transport observations.
- [Build measurements and cost structure](https://architecture.joomlacomponentbuilder.com/markdown/engineering/performance.md): Repeated self-build measurements, input/output accounting, acquisition and generation costs, and the practical resource tradeoffs of retained state.
- [Self-generation and maintenance propagation](https://architecture.joomlacomponentbuilder.com/markdown/engineering/regeneration.md): JCB's own blueprint-driven application, reusable library inputs, and how shared compiler changes propagate through regenerated products.
- [Verification and traceability](https://architecture.joomlacomponentbuilder.com/markdown/engineering/verification.md): How source correspondence, public artifacts, executable mechanisms, mathematical arguments, and runtime builds establish different parts of the account.
- [Implementation and evidence source map](https://architecture.joomlacomponentbuilder.com/markdown/reference/source-map.md): Pinned compiler paths, inspected responsibilities, integrated extrusion fingerprints, and public blueprint/product sources.
- [Related mechanisms and bibliography](https://architecture.joomlacomponentbuilder.com/markdown/reference/bibliography.md): Primary references for model-driven engineering, contextual attributes, staged generation, memoization, modularity, and bounded bidirectional transformations.
- [Edition scope and engineering record](https://architecture.joomlacomponentbuilder.com/markdown/reference/edition.md): The publication's authorship, implementation scope, source captures, mathematical conventions, and measurement boundaries.
- [Architectural glossary](https://architecture.joomlacomponentbuilder.com/markdown/reference/glossary.md): Product terms and language-neutral concepts used consistently throughout the white paper.
- [Citation and authorship](https://architecture.joomlacomponentbuilder.com/markdown/reference/citation.md): How to cite the white paper, an individual article, a source revision, or a generated example.
- [Publication, downloads, and maintenance](https://architecture.joomlacomponentbuilder.com/markdown/reference/publication.md): The Markdown-first website contract, domain configuration, reproducible build, review artifacts, and deployment boundary.
- [Rights and reuse](https://architecture.joomlacomponentbuilder.com/markdown/reference/licensing.md): Attribution and license boundaries for the white paper, executable examples, branding, and cited implementation.