Glossary - Rejean-McCormick/Arketype GitHub Wiki
Glossary
| Term | Meaning in Arketype |
|---|---|
| Archetype | A proposed structural form with responsibilities and integrity rules. |
| Template | A neutral workspace scaffold linked to an archetype. |
| Instance | A separately initialized workspace with a distinct state_ref. |
| Visual pattern | A reusable reading motif such as tree, matrix, hub or timeline. |
| Situated diagram | A labeled noncanonical example of a pattern in a scenario. |
| Use-case profile | A concrete scenario identifying a principal archetype and support forms. |
| Composition recipe | Design-only description of potential relationships between archetypes. |
| Native model | The actual knowledge structure of a Kristal, not merely its UI layout. |
| Semantic ownership | Responsibility for meaning and domain statements within a boundary. |
| Canon | The set of formally committed artifacts in the relevant workspace. |
| Source provenance | Attribution and integrity information for material relied upon. |
| Epistemic status | Whether material is a report, observation, hypothesis, proof, interpretation, and so forth. |
| Logical contract | The domain-specific agreement governing what can be considered a valid logical artifact. |
check |
Local Authoring Kit consistency check, not factual qualification. |
build-v9 |
Creation of local v9 build output, not publication or activation. |
| Generated projection | A reader-facing HTML/PDF representation derived from descriptive JSON. |
English terminology on these pages is explanatory; stable source-file slugs and JSON format identifiers remain unchanged.