ores
Table of Contents
This page is the node for the ores technical space in the codegen
physical-space address graph. Its title is its MASD address; it gathers the
facets generated for this technical space. Each facet is its own document,
linked from the table below. Codegen traverses this graph (root → technical
space → facet → archetype) to resolve which archetypes an entity generates.
Summary
(Two to four sentences: what kind of artefacts this technical space covers and which model elements drive them.)
Facets
Facets in this technical space — each links to its own node doc. Generated; do not edit by hand.
| Facet | Description |
Technical spaces
| Technical space | Facets | Description |
|---|---|---|
| ores.cmake | 2 | The CMake technical space: per-component build files (root, src, tests, modeling). |
| ores.cpp | 13 | The C++ technical space: domain types, repositories, mappers, Qt UI, services, messaging, generators. |
| ores.doc | 4 | The documentation technical space: org-mode doc scaffolds (facets, archetypes, agile artefacts) generated by doc_generate. |
| ores.plantuml | 1 | The PlantUML technical space: diagram generation (ER diagrams from the SQL schema). |
| ores.shell | 1 | The shell technical space: POSIX shell scripts that orchestrate service provisioning and environment setup. |
| ores.sql | 3 | The SQL technical space: bi-temporal schema, triggers, populate scripts, service-registry SQL. |
See also
- Parent: the
oresphysical-space root.