Experience Architecture is the production and lifecycle system that reconstructs explicit candidate operational models from accumulated experience, observational evidence, and documentary or formal sources, then carries qualified models through verification, release, reuse, and maintenance.
Source and Reconstruction Layer
The architecture distinguishes production inputs from the mechanism used to process them. Generalized documentary and formal sources such as standards, regulations, manuals, research, technical specifications, and public documentation provide traceable descriptions, constraints, and evidence for the domain model. An LLM serves as a reconstruction mechanism whose learned statistical structure can help surface likely structures, terminology, and relationships while processing those sources.
These elements have different standing. The LLM's learned statistical structure is useful for discovery and reconstruction but is not itself documentary evidence and does not confer normative authority. Documentary and formal sources also differ in evidentiary standing: binding sources can establish mandatory constraints, while explanatory or illustrative material can support discovery and coverage without acquiring the same authority. Those distinctions must remain visible throughout production.
LLMs and deterministic processing can identify candidate entities, states, processes, facts, conditions, rules, actions, results, relationships, and boundaries. The objective is model reconstruction, not summary generation.
Model Layer
Candidate structure is assembled into explicit models with defined scope and relationships. The model is inspectable as explicit structure while remaining traceable to the source material and evidence from which it was reconstructed.
Evidence and Lineage
Each important model element should preserve a traceable relationship to the sources that support it. Lineage links source material, reconstruction decisions, model versions, and later releases.
This allows a reviewer to answer not only what the model says, but why it says it and which source change may require a new review.
Verification Layer
The structure is checked for source support, internal consistency, required coverage, contradictory rules, missing states, ambiguous actions, unresolved facts, and inappropriate extrapolation beyond scope.
Verification also determines readiness. A candidate model is ready for reusable release only when its required structure, source support, unresolved issues, and boundaries satisfy the release criteria for the intended class of use.
Lifecycle and Versioning
Models move through a lifecycle: candidate reconstruction, verification, release, reuse, review, new version, and retirement of obsolete releases. Source changes can trigger review because model lineage identifies what depends on the changed material.
Reuse Layer
Released models with explicit verification status and declared scope can support multiple applications: training, requirements, conformance, decision support, testing, software generation, AI systems, and automation.
The architecture can be summarized as:
accumulated experience and observational evidence
+ documentary and formal sources, including governing constraints where applicable
→ LLM-assisted reconstruction
→ explicit candidate model
→ evidence and lineage
→ verification and readiness
→ released reusable asset
→ multiple applications
Experience Architecture is the production and lifecycle system that makes Experience Capitalization repeatable.
Top comments (0)