s3dgraphy 1.6.0.dev16__tar.gz → 1.6.0.dev17__tar.gz

{s3dgraphy-1.6.0.dev16/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev17}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: s3dgraphy
-Version: 1.6.0.dev16
+Version: 1.6.0.dev17
 Summary: 3D Stratigraphic Graph Management Library for archaeological and heritage applications
 Author-email: Emanuel Demetrescu <emanuel.demetrescu@cnr.it>
 Maintainer-email: Emanuel Demetrescu <emanuel.demetrescu@cnr.it>
@@ -274,7 +274,7 @@ The rule the other repos inherit, in one line: *if an endpoint needs to compute
 something about a graph, that something belongs here.* This library has no web
 framework and no socket on purpose — what it does can be proved on a table.
 
-**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../em-server/docs/ARCHITECTURE-SYSTEM.md).
+**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../stratigraph-server/docs/ARCHITECTURE-SYSTEM.md).
 
 ---
 

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/README.md

@@ -198,7 +198,7 @@ The rule the other repos inherit, in one line: *if an endpoint needs to compute
 something about a graph, that something belongs here.* This library has no web
 framework and no socket on purpose — what it does can be proved on a table.
 
-**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../em-server/docs/ARCHITECTURE-SYSTEM.md).
+**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../stratigraph-server/docs/ARCHITECTURE-SYSTEM.md).
 
 ---
 

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3dgraphy"
-version = "1.6.0.dev16"
+version = "1.6.0.dev17"
 description = "3D Stratigraphic Graph Management Library for archaeological and heritage applications"
 readme = "README.md"
 requires-python = ">=3.9"

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/JSON_config/datamodel_translations.json

@@ -1081,6 +1081,22 @@
    "label": {
     "en": "Annotation Region"
    }
+  },
+  "GCPSetNode": {
+   "description": {
+    "en": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete)."
+   },
+   "label": {
+    "en": "Ground control points"
+   }
+  },
+  "RegistrationTransformNode": {
+   "description": {
+    "en": "The 7-parameter similarity (rotation 3x3 row-major, translation [x,y,z], positive scale) that places a produced model, with data.rms and data.residuals — the error bar, stored beside the claim rather than in a log nobody keeps. data.crs is the frame the model lands IN; null means a site-local frame (mode 'local'), which is NOT the same sentence as an absent transform. Re-registration is a NEW node produced by a NEW crmdig:D7; the superseded one is never edited."
+   },
+   "label": {
+    "en": "Registration transform"
+   }
   }
  }
 }

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/JSON_config/em_visual_rules.json

@@ -1,6 +1,6 @@
 {
   "formal_language": "EM",
-  "version": "1.6.14",
+  "version": "1.6.16",
   "_note_material_vs_qualia_color": [
     "DUE COSE DIVERSE CHE SI CHIAMANO ENTRAMBE color. Non confonderle: e gia successo.",
     "1) QUI, in node_styles.<tipo>.style.material.rgba_color — il COLORE DEL MATERIALE BLENDER del proxy 3D, in float LINEARI. UNA sola chiave: `rgba_color`. Fino a S8 il file ne usava due (`color` sui 13 tipi stratigrafici, `rgba_color` sugli altri) e get_material_color() ne leggeva una sola, restituendo None per 21 tipi su 38; ora sono unificate e la vecchia `color` e letta solo come tolleranza verso file scritti prima. Un tipo che non diventa mai una mesh NON ha material affatto (i contenitori di gruppo, e da S7 i dieci nodi che rendono per icona): per loro get_material_color() torna None, ed e corretto.",
@@ -9,6 +9,8 @@
     "In breve: qui si decide di che colore DISEGNARE una US; li si registra di che colore ERA."
   ],
   "_changelog": {
+    "1.6.16": "Asset declarations made TRUE. Four styles named a 2D file that is not there — SE.png, TSU.svg, serUSD.svg and unknown.png (which never existed) — and GRAPH named two, so it drew no icon at all. icons.ts returns null for a missing file and the canvas quietly draws the shape, so all five failed silently. Now: graph.svg authored (neutral gray, three nodes and their edges, the meta-container), unknown points at the generic_node.svg that exists, the three stale halves name the file that is there. Enforced by tests/test_visual_assets.py; the 16 unmodelled .glb are REPORTED (there and in sync-datamodels.sh), not asserted \u2014 a placeholder that looks official is harder to notice than an absence.",
+    "1.6.15": "Georeferencing gets its symbol on the canvas: node_styles GCP (GCPSetNode, crosshair) and RGT (RegistrationTransformNode, axes + rotation arc), in the same #FF6600 reference family as GEO/SS/LINK, each with its own 2D icon. ADDITIVE. Also 1.6.14-era: dtc_kinds.process.photogrammetry. Note the limit of a per-TYPE rule: whether a transform is georeferenced or a site-local frame is an INSTANCE fact (data.crs) and is read from the has_gcp_set edge, not from the style.",
     "1.6.14": "BUGFIX-GLYPH follow-up (2026-08-05, E.D.): SE now renders its GLYPH in the scene (the new SE.svg, a stratigraphic-section box with a writable middle band) instead of a bare triangle, so a name can be written inside it. Added SE to 2d_render_glyph_types (aspect 1.331 from the SVG viewBox) and switched SE 2d_icon_prefer to vector (the raster SE.png is the stale stipple; the new symbol is the SVG). Dropped the interim shape_bbox=square. The shape:triangle stays declared for other consumers but the 2D scene draws the glyph. NOTE: verify the SVG carries a light background for dark-canvas legibility (like combiner.svg).",
     "1.6.13": "BUGFIX-GLYPH (2026-08-05): SE (StratigraphicEvent) gains shape_bbox=\"square\" on its style, like BR. Its triangle was drawn in the wide default 90x32 box, leaving the connect handle far from the glyph; a square bbox (side = min(w,h)) makes the triangle sit in a ~32x32 box with the handle adjacent, matching BR (diamond, square) and the glyph types. No shape_scale: unlike BR (a 0.7 marker) the SE triangle stays full-size. The SCENE representation of SE remains the triangle shape, not the raster icon (S10/POL5 decision unchanged).",
     "1.6.12": "EM3 - `2d_render_glyph_types` guadagna una tabella `aspect`: la larghezza del box di un nodo-glifo e la sua ALTEZZA per l'aspect del disegno, quindi tutti i glifi hanno la stessa altezza e differiscono solo in larghezza (regola E.D.). Default 1.0 = quadrato, che e cio che sono gli undici glifi DTC dopo l'autocrop di POL4 ed extractor/combiner per costruzione; l'unico davvero non quadrato oggi e `author` (0.875 = 448/512). I numeri sono STATICI e misurati una volta dai file: un aspect letto da naturalWidth a runtime farebbe dipendere il layout da quando un bitmap finisce di decodificare (box che salta, due run diversi sullo stesso documento). Il prezzo di un numero statico e che puo diventare stantio se un asset viene ridisegnato: da questa versione sync-datamodels.sh ri-misura ogni file vendorato e AVVISA se una dichiarazione sbaglia di oltre il 2%.",
@@ -224,7 +226,7 @@
     "serUSD": {
       "3d_file": "src/3D/serUSD.glb",
       "2d_file_rast": "src/2D/serUSD.png",
-      "2d_file_vect": "src/2D/serUSD.svg",
+      "2d_file_vect": "src/2D/serUSD.png",
       "style": {
         "material": {
           "rgba_color": {
@@ -287,7 +289,7 @@
     "TSU": {
       "3d_file": "src/3D/TSU.glb",
       "2d_file_rast": "src/2D/TSU.png",
-      "2d_file_vect": "src/2D/TSU.svg",
+      "2d_file_vect": "src/2D/TSU.png",
       "style": {
         "material": {
           "rgba_color": {
@@ -332,7 +334,7 @@
     "SE": {
       "_comment": "Stratigraphic Event: l'ATTO che crea, modifica o distrugge un'unita — un terremoto che fa cadere l'intonaco, una demolizione, l'inizio di un cantiere. Non e materia, e un processo, e per questo non appartiene a nessuna delle famiglie cromatiche della materia (rosso reale, verde/blu virtuale, arancio documentario, giallo special find, grigio negativo). Prende il TEAL della famiglia attivita: un ActivityNodeGroup e un fascio di atti e porta gia la linguetta ciano #CCFFFF, quindi il ciano e l'unico colore del linguaggio che dice gia 'e successo qualcosa' invece di 'qualcosa c'e'. Curato in S10 (2026-08-02): fino ad allora SE portava il segnaposto #BC0000 mai scelto, che per giunta contraddiceva il proprio bordo nero, e il node datamodel dichiarava il simbolo 'to be defined'. Il nero di BR e stato scartato di proposito: un material nero rende un proxy illeggibile in viewport, e i proxy SE si vedono (Heriverse li disegna fra i suoi stratigraphicTypes). POL5 (2026-08-04): l'ICONA e il raster (`2d_icon_prefer: raster`), come per NARR e per la stessa ragione — SE.svg e un tratteggio vettorializzato da 284 KB per un glifo che nessun renderer disegna oltre i 30 px. Il vettore resta dichiarato perche esiste; il flag dice quale dei due DISEGNARE. Il PNG a 256 px e reso DA quell'SVG, quindi i due non possono divergere. Nel grafo SE resta comunque un TRIANGOLO disegnato (shape), non l'icona: il raster serve a palette ed elenchi.",
       "3d_file": "src/3D/SE.glb",
-      "2d_file_rast": "src/2D/SE.png",
+      "2d_file_rast": "src/2D/SE.svg",
       "2d_file_vect": "src/2D/SE.svg",
       "2d_icon_prefer": "vector",
       "style": {
@@ -490,7 +492,7 @@
     "GRAPH": {
       "_comment": "Top-level container node representing the EM graph itself. Anchor for graph-wide metadata propagation (default author, license, embargo, epoch). Rendered as a dashed rounded rectangle to read as a meta-container, neutral gray to stay visually distinct from stratigraphic and paradata nodes. Graphml palette prefix: 'G.'.",
       "file_3d": "src/3D/graph.glb",
-      "2d_file_rast": "src/2D/graph.png",
+      "2d_file_rast": "src/2D/graph.svg",
       "2d_file_vect": "src/2D/graph.svg",
       "style": {
         "material": {
@@ -542,6 +544,32 @@
       },
       "label_position": "over"
     },
+    "GCP": {
+      "_comment": "Ground control points — the EVIDENCE behind a registration: which point was seen on which photograph at which pixel, and where it is in the world. The NODE IS THE SET, never the single GCP (data.points), which is why the icon shows one target among several marks. Same orange as the other reference/georeferencing nodes (GEO, SS, LINK) because it is that family; the crosshair shape distinguishes measurement-of-a-place from position-of-a-site. Graphml palette prefix: 'GC.'.",
+      "file_3d": "src/3D/gcp_set.glb",
+      "2d_file_rast": "src/2D/gcp_set.svg",
+      "2d_file_vect": "src/2D/gcp_set.svg",
+      "style": {
+        "border_color": "#FF6600",
+        "fill_color": "#FFFFFF",
+        "border_style": "solid",
+        "shape": "crosshair"
+      },
+      "label_position": "over"
+    },
+    "RGT": {
+      "_comment": "Registration transform — the SOLUTION: the 7-parameter similarity that places a produced model, with its RMS. Drawn as axes plus a rotation arc. NOTE, and it is a limit of a per-TYPE rule: whether a given transform is georeferenced (data.crs set) or a site-local frame (crs null) is an INSTANCE fact and cannot be encoded here — a reader tells the two modes apart by the presence of the has_gcp_set edge, which is why that edge exists. Graphml palette prefix: 'RG.'.",
+      "file_3d": "src/3D/registration_transform.glb",
+      "2d_file_rast": "src/2D/registration_transform.svg",
+      "2d_file_vect": "src/2D/registration_transform.svg",
+      "style": {
+        "border_color": "#FF6600",
+        "fill_color": "#FFFFFF",
+        "border_style": "solid",
+        "shape": "axes"
+      },
+      "label_position": "over"
+    },
     "GEO": {
       "file_3d": "src/3D/geo.glb",
       "2d_file_rast": "src/2D/geo_position.svg",
@@ -628,7 +656,7 @@
     },
     "unknown": {
       "file_3d": "src/3D/unknown.glb",
-      "file_2d": "src/2D/unknown.png",
+      "file_2d": "src/2D/generic_node.svg",
       "style": {
         "border_color": "#FF0000",
         "fill_color": "#FFFFFF",
@@ -835,6 +863,11 @@
       "topographic": { "label": "Topographic survey", "glyph": "01_topographicnetwork", "description": "Total-station / topographic-network acquisition." }
     },
     "process": {
+      "photogrammetry": {
+        "label": "Photogrammetry",
+        "glyph": "03_mesh",
+        "description": "Structure-from-motion reconstruction: a cluster of photographs becomes a 3D model. A specific kind of transformation, named because what a reader needs to know about a mesh is which family of process made it \u2014 and because the placement (RegistrationTransform) only means something for this one."
+      },
       "transformation": { "label": "Transformation", "glyph": "00_transformation", "description": "A processing/transformation step turning inputs into produced digital objects." }
     },
     "acquisition": {

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/JSON_config/node_registry.generated.json

@@ -1,6 +1,6 @@
 {
  "_generated": "by `python -m s3dgraphy.tools.sync_node_datamodel` — DO NOT hand-edit. The flat class hierarchy (parent/node_type/description) is derived from the Python Node subclasses; hand-authored semantics and CIDOC mappings live in s3Dgraphy_node_datamodel.json.",
- "s3Dgraphy_data_model_version": "1.6.3",
+ "s3Dgraphy_data_model_version": "1.6.4",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",
@@ -77,6 +77,11 @@
    "node_type": "FunctionalUnitNodeGroup",
    "description": "Typed aggregation of the stratigraphic units that make up one"
   },
+  "GCPSetNode": {
+   "parent": "Node",
+   "node_type": "gcp_set",
+   "description": "The ground control points a registration was (or will be) solved from."
+  },
   "GeoPositionNode": {
    "parent": "Node",
    "node_type": "geo_position",
@@ -157,6 +162,11 @@
    "node_type": "property",
    "description": "Nodo che rappresenta una proprietà associata a un altro nodo."
   },
+  "RegistrationTransformNode": {
+   "parent": "Node",
+   "node_type": "registration_transform",
+   "description": "The similarity that places a model — 7 parameters and what they cost."
+  },
   "RepresentationModelDocNode": {
    "parent": "RepresentationNode",
    "node_type": "representation_model_doc",

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/JSON_config/s3Dgraphy_connections_datamodel.json

@@ -1,5 +1,5 @@
 {
-  "s3Dgraphy_connections_model_version": "1.6.11",
+  "s3Dgraphy_connections_model_version": "1.6.13",
   "description": "s3Dgraphy connections datamodel including edge types with CIDOC-CRM mappings. v1.6.11 (batch ingestion, 2026-08-17): two widenings for bulk assets. has_author.source DTCProcessNode -> DTCNode, so an ACQUISITION event (D12) can carry the author of a whole lot; dtc_had_input.target += DTCNode, so a DECLARED derivation can name a whole acquisition as its input (one input, not 500 edges) — that case projects as prov:wasInformedBy, not prov:used/L10, which range over digital objects and would be wrong for an event. v1.6.8 (MIG1-A): graph-scope rights metadata become first-class nodes (DP-65). is_in_paradata_nodegroup.source += AuthorNode/LicenseNode/EmbargoNode and has_paradata_nodegroup.source += GraphNode, so the graph-self node (GraphNode) owns a graph-scope ParadataNodeGroup whose members are the AuthorNode/LicenseNode/EmbargoNode (+ the DP-65 GeoPositionNode shift), replacing the legacy graph.data['author_name'/'license'/'embargo'] fields. The Data Funnel canvas tier now reads these member nodes (one reader per scope); a one-shot load-time migration materialises the legacy fields into nodes. v1.6.7 (BUGFIX-CONN3): closes the two silent follow-ups of CONN2. has_documentation.source gains PropertyNode (judicious widening): the honest reading of a legacy yEd dashed PropertyNode→Document connector is P70i_is_documented_in ('the property is documented in this source'), NOT has_visual_reference (which CONN2 moved to PropertyNode→ResourceNode). The import heuristic (import_graphml.enhance_edge_type) now routes PropertyNode→Document to has_documentation and the rarer CombinerNode/ParadataNode→Document to generic_connection+warning (a combiner aggregates extractors and cites no document; the DTC chain is NOT synthesised at import). Shelf: hat_as_document no longer offers has_visual_reference (a Document attaches via has_documentation/extracted_from); a new hat_as_visual_resource attaches a ResourceNode image via has_visual_reference from a PropertyNode — the correct home after CONN2. No illegal edge is produced or expected. v1.6.6 (BUGFIX-CONN2): closes the two open domain questions on has_visual_reference (E.D. 2026-08-05). SOURCE narrowed to exactly [PropertyNode]: only a property (an asserted quale) is what a visual reference illustrates; the generic ParadataNode entry is dropped, which — because ExtractorNode, CombinerNode and DocumentNode are all subclasses of ParadataNode — now excludes them by class hierarchy (a PropertyNode is neither a sibling nor a parent of the others). The extractor/combiner denied_edges from v1.6.5 are therefore REDUNDANT for this edge but are KEPT as a defensive guard (they still bite if the source is ever broadened back to ParadataNode). TARGET changed from [DocumentNode] to [ResourceNode]: the oddity was that a visual reference pointed at a source-document (E31) rather than at a visual resource. It now points at the resource-layer image node (ResourceNode = E73 Information Object / ExternalResourceReference — the same P67 hinge RM/RMDoc use via has_linked_resource), keeping DocumentNode = fonte. CIDOC stays P138i_has_representation with the target co-typed E36 Visual Item: E36 is a subclass of E73, so co-typing a ResourceNode as E36 is range-consistent (it was NOT, strictly, for an E31 Document). FOLLOW-UPS flagged for E.D. (see end-of report): (a) import_graphml.enhance_edge_type still hardcodes PropertyNode/Combiner/Paradata→DocumentNode ⇒ has_visual_reference (legacy yEd heuristic, now produces an edge this datamodel refuses) — needs a domain decision on what legacy paradata→document edges become; (b) shelf.hat_as_document lists has_visual_reference among the Document-attach edges — it can no longer validate (target is ResourceNode), so a paradata attach silently no longer attaches; a hat_as_visual_resource(ResourceNode)+has_visual_reference path is the proper home. v1.6.5 (BUGFIX-CONN): has_visual_reference is no longer offered FROM an ExtractorNode or a CombinerNode. An extractor toward a document expresses ONLY extracted_from (its relation to the source is the extraction, not an illustration); a combiner aggregates extractors and illustrates nothing. Because ExtractorNode, CombinerNode and PropertyNode are all subclasses of ParadataNode, and has_visual_reference.source lists ParadataNode, simply dropping the two subtypes from the source list would not exclude them (they still match via the parent class). So this is expressed with node_type_restrictions (keyed by RUNTIME node_type, like USNt) using a new denied_edges blacklist (the mirror of allowed_edges): extractor/combiner deny has_visual_reference. PropertyNode and any other legitimate ParadataNode source keep it unchanged. OPEN domain question for E.D.: which paradata node-types may legitimately have a visual reference (today source = PropertyNode/ExtractorNode/CombinerNode/ParadataNode) — extractor/combiner removed; the rest left as-is, not invented. v1.6.1: has_paradata_nodegroup source extended to include EpochNode — an epoch can now own a ParadataNodeGroup holding its temporal-definition properties (e.g. absolute_time_start/end as PropertyNodes with paradata provenance), mirroring how a StratigraphicNode carries its paradata group. v1.6.0 (paired with node datamodel v1.6.0) introduces: bug fix on is_in_paradata_nodegroup (typo 'ProperrtyNOde' → 'PropertyNode'); semantic fix on has_documentation (P104_is_subject_to → P70i_is_documented_in — P104 means 'subject to a legal right', not 'has documentation'); deprecation of has_timebranch as duplicate of is_in_timebranch (the latter is the canonical one — used by import_graphml.py and graphml_patcher.py; the former exists only in config JSON); component list aligned with node datamodel (HDT-O, PROV-O added). HDT-O containment properties (hdto:contains_HDT, hdto:contains_SU, hdto:isPrimary) and physical-relation discriminator subproperties (em:abuts, em:cuts, em:fills, em:overlies, em:bonded_to, em:equals as rdfs:subPropertyOf crmarchaeo:AP11_has_physical_relation) to be added in v1.6.1. v1.5.3 introduced canonical/reverse directionality with verb-based labels for clear socket identification in node editors. v1.5.4 added 'has_visual_reference' edge type. v1.5.5 added 'is_in_location' edge type with context-sensitive CIDOC mapping (P53 for node→location, P89 for the recursive location→location hierarchy) and an optional 'is_primary' boolean attribute (s3d:isPrimary, proposed). v1.6.3: added node_type_restrictions — a per-node-type narrowing of the class-level edge rules (POL5): USN (the NEUTRAL stratigraphic unit, a risparmio) takes is_after/is_before and nothing else, because a void cannot cut, fill, abut or bond. v1.6.4 (POL6): the same restriction, moved to USNt — the tokens went back to their conventional meanings, USN = US negativa (all relations, it is a unit of the sequence) and USNt = US neutra (sequence only).",
   "components": [
     "CIDOC-CRM",
@@ -1311,6 +1311,7 @@
     },
     "dtc_had_input": {
       "name": "dtc_had_input",
+      "dtc_role": "chain",
       "label": "DTC process had input",
       "description": "DTC chain: a processing step (DTCProcess) consumed an input RESOURCE — a raw acquisition (photo/laser scan/…) = the ResourceNode (E73/D1). ECHOES DTC substrate profile. Dual projection CRMdig + PROV-O.",
       "reverse": {
@@ -1337,6 +1338,7 @@
     },
     "dtc_had_output": {
       "name": "dtc_had_output",
+      "dtc_role": "chain",
       "label": "DTC process had output",
       "description": "DTC chain: a processing step (DTCProcess) produced a RESOURCE (a file: mesh/orthophoto/table…) — the ResourceNode (E73/D1), which is the SHARED HINGE that a RepresentationModel and/or a Document may reference. The produced ResourceNode carries data.dtc_kind + resource_type. ECHOES DTC substrate profile. Dual projection CRMdig + PROV-O.",
       "reverse": {
@@ -1362,6 +1364,7 @@
     },
     "dtc_derived_from": {
       "name": "dtc_derived_from",
+      "dtc_role": "chain",
       "label": "DTC output derived from input",
       "description": "DTC chain: the produced RESOURCE (ResourceNode) was derived from an acquisition (DTCInput) — the direct provenance shortcut alongside the process. ECHOES DTC substrate profile. Dual projection CRMdig + PROV-O.",
       "reverse": {
@@ -1384,6 +1387,55 @@
         ]
       }
     },
+    "has_registration_transform": {
+      "name": "has_registration_transform",
+      "label": "Placed by",
+      "description": "A produced RESOURCE (a reconstructed model) is placed in space by a RegistrationTransform — the 7-parameter similarity solved for it. The absence of this edge is a statement too: a model nobody placed. Re-registration adds a NEW transform node and a new edge; the superseded one stays, because moving a model is provenance, not an edit.",
+      "reverse": {
+        "name": "places",
+        "label": "Places the model"
+      },
+      "mapping": {
+        "cidoc": "P67i_is_referred_to_by",
+        "cidoc_extension": "CIDOC-CRM",
+        "extension_mapping": null,
+        "extension_name": null,
+        "rationale": "The transform is an information object ABOUT the model, so the CRM property runs transform -P67_refers_to-> model. The EM-native edge reads from the model (the direction every consumer traverses: 'where do I put this file?'), so the projection is the inverse P67i. No PROV-O dual: PROV has nothing to say about spatial placement, and inventing one would be noise."
+      },
+      "allowed_connections": {
+        "_note": "Source is the ResourceNode (E73/D1), the shared hinge a RepresentationModel or a Document may reference — the same target the DTC output edge uses, so the model that was produced and the model that was placed are one node.",
+        "source": [
+          "ResourceNode"
+        ],
+        "target": [
+          "RegistrationTransformNode"
+        ]
+      }
+    },
+    "has_gcp_set": {
+      "name": "has_gcp_set",
+      "label": "Solved from control points",
+      "description": "A RegistrationTransform was solved from a GCPSet — the evidence behind the placement. Present ONLY in absolute mode: a transform with no such edge is a site-local frame, and the missing edge is what tells a reader so without having to trust a flag.",
+      "reverse": {
+        "name": "controlled_registration",
+        "label": "Controlled this registration"
+      },
+      "mapping": {
+        "cidoc": "L21_used_as_derivation_source",
+        "cidoc_extension": "CRMdig",
+        "extension_mapping": "prov:wasDerivedFrom",
+        "extension_name": "PROV-O",
+        "rationale": "The same argument dtc_derived_from already makes, applied one layer up: CRM routes derivation through the event, and the event (crmdig:D7) IS in the graph — this edge is the direct shortcut between the derived object (the transform) and its source (the control set), in the same direction, so it can be read without naming the process."
+      },
+      "allowed_connections": {
+        "source": [
+          "RegistrationTransformNode"
+        ],
+        "target": [
+          "GCPSetNode"
+        ]
+      }
+    },
     "generic_connection": {
       "name": "generic_connection",
       "label": "Generic connection",
@@ -1404,5 +1456,6 @@
         ]
       }
     }
-  }
+  },
+  "_dtc_role_note": "dtc_role marks an edge as part of the DTC CHAIN — the three edges a provenance walk may traverse. It exists because the classification used to be written twice: by name on the node (s3dgraphy.dtc) and by PREFIX in the client (startsWith('dtc_')). The prefix presumed every future dtc_* edge would be chain, so a dtc_* edge that is CONTEXT — a dtc_annotated_by, say — would have been a corridor on the client and not on the node: two rules with one name. Now the datamodel says it once and both sides read it. An edge WITHOUT dtc_role is context by construction: adding one is a JSON entry, and it is born non-traversable."
 }

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/JSON_config/s3Dgraphy_node_datamodel.json

@@ -1,6 +1,6 @@
 {
- "s3Dgraphy_data_model_version": "1.6.3",
- "description": "s3Dgraphy nodes datamodel including node types with CIDOC-CRM mappings. v1.6.3 re-reads SemanticShapeNode as a PAYLOAD carrier: the proxy of a unit is now a PropertyNode of qualia type 'geometry' that points at the shape (has_semantic_shape), so the proxy inherits the paradata chain it never had. Breaking for consumers that read the proxy as a standalone SemanticShape. v1.6.2 adds AnnotationRegionNode (em:AnnotationRegion, subclass of crm:E36_Visual_Item): the geometry of a 2D annotation in NORMALISED image space, distinct from SemanticShapeNode (3D scene geometry, crmgeo:SP5) - the semantics of the 2D annotator, defined before any canvas exists. v1.6.0 inaugurates a systematic CIDOC-CRM mapping revision: complete audit of all node types against CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMsci, CRMgeo; replacement of legacy 'cidoc_s3d' pseudo-class names (invented strings without IRI or superclass declaration) with formal em:/s3d: IRIs declared as proper subclasses of CRM classes; introduction of CRMinf as primary (not alternative) for the paradata chain (ParadataNode, PropertyNode interpretive case, ExtractorNode, CombinerNode); introduction of PROV-O for AuthorNode to cover both human and AI agents; alignment with the Heritage Digital Twin Ontology (HDT-O) for containment / granularity properties; LocationNodeGroup (v1.5.3) adopted as the reference pattern (CIDOC-native composition via P2_has_type → E55 Type instances, with explicit extension_status and rationale). Companion deliverables: em.ttl (formal EM extension ontology, dereferenceable via w3id.org/em/) and hdto_extension.ttl (HDT-O granularity properties: contains_HDT, contains_SU, isPrimary). v1.5.4 added RSF (Reused Special Find — spolia) as a stratigraphic subtype, octagon with red border, family=real, is_series=false. Originating DP: DP-26 (spolia project, last DP before the EM 1.5 cut). v1.5.3 added LocationNodeGroup (E53 Place + E55 Type) for spatial / locational membership orthogonal to ActivityNodeGroup (intention) and EpochNode (time). v1.5.2 added family + is_series classification metadata on stratigraphic subtypes.",
+ "s3Dgraphy_data_model_version": "1.6.4",
+ "description": "s3Dgraphy nodes datamodel including node types with CIDOC-CRM mappings. v1.6.4 adds the ADDITIVE georeferencing_nodes section (GCPSetNode = em:GCPSet, RegistrationTransformNode = em:RegistrationTransform, both subclasses of crm:E73_Information_Object with their own extension URIs so the RDF projection stays bijective): the CONTROL and the SOLUTION that place a produced model in the world, introduced with the photogrammetry processing connector. The two modes of that connector are the SHAPE of the graph (a transform with a CRS that has_gcp_set points at = absolute; a transform with crs=null and no control set = a site-local frame; no transform at all = nobody placed it), never a flag. No existing family changed. v1.6.3 re-reads SemanticShapeNode as a PAYLOAD carrier: the proxy of a unit is now a PropertyNode of qualia type 'geometry' that points at the shape (has_semantic_shape), so the proxy inherits the paradata chain it never had. Breaking for consumers that read the proxy as a standalone SemanticShape. v1.6.2 adds AnnotationRegionNode (em:AnnotationRegion, subclass of crm:E36_Visual_Item): the geometry of a 2D annotation in NORMALISED image space, distinct from SemanticShapeNode (3D scene geometry, crmgeo:SP5) - the semantics of the 2D annotator, defined before any canvas exists. v1.6.0 inaugurates a systematic CIDOC-CRM mapping revision: complete audit of all node types against CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMsci, CRMgeo; replacement of legacy 'cidoc_s3d' pseudo-class names (invented strings without IRI or superclass declaration) with formal em:/s3d: IRIs declared as proper subclasses of CRM classes; introduction of CRMinf as primary (not alternative) for the paradata chain (ParadataNode, PropertyNode interpretive case, ExtractorNode, CombinerNode); introduction of PROV-O for AuthorNode to cover both human and AI agents; alignment with the Heritage Digital Twin Ontology (HDT-O) for containment / granularity properties; LocationNodeGroup (v1.5.3) adopted as the reference pattern (CIDOC-native composition via P2_has_type → E55 Type instances, with explicit extension_status and rationale). Companion deliverables: em.ttl (formal EM extension ontology, dereferenceable via w3id.org/em/) and hdto_extension.ttl (HDT-O granularity properties: contains_HDT, contains_SU, isPrimary). v1.5.4 added RSF (Reused Special Find — spolia) as a stratigraphic subtype, octagon with red border, family=real, is_series=false. Originating DP: DP-26 (spolia project, last DP before the EM 1.5 cut). v1.5.3 added LocationNodeGroup (E53 Place + E55 Type) for spatial / locational membership orthogonal to ActivityNodeGroup (intention) and EpochNode (time). v1.5.2 added family + is_series classification metadata on stratigraphic subtypes.",
  "components": [
   "CIDOC-CRM",
   "CRMarchaeo",
@@ -1572,6 +1572,56 @@
    }
   }
  },
+ "georeferencing_nodes": {
+  "_section_note": "GEOREFERENCING — how a produced model got INTO the world, as two distinct things that fail differently: GCPSetNode = the CONTROL (evidence: which point was seen on which photograph at which pixel, and where it is in the world, in which CRS, with what uncertainty) — it can exist before any model and survives being reused by a second reconstruction; RegistrationTransformNode = the SOLUTION (the 7-parameter similarity the bundle adjustment settled on, with its RMS/residuals) — it is what the model is placed by and what gets REPLACED when better coordinates arrive, the old one staying in the graph because moving a model is provenance. The TWO MODES of the photogrammetry design are the SHAPE of the graph, not a flag: absolute = a transform with a crs that has_gcp_set points at; local = a transform with a scale and crs=null (scaled and oriented in a site frame, honestly NOT georeferenced); no transform at all = nobody placed it. Distinct from GeoPositionNode (where a STUDY/site is) and from SemanticShapeNode (3D geometry of a unit): this section is about the REGISTRATION ACT's evidence and result. Attached to the produced Resource, so the DTC genesis (crmdig:D7, dtc_had_input/dtc_had_output) is not duplicated here. Gated OUT of the stratigrapher palette, like dtc_nodes and hdto_nodes. Added 2026-08-29 with the photogrammetry processing connector; ADDITIVE — no existing family changed.",
+  "GCPSetNode": {
+   "class": "GCPSetNode",
+   "parent": "Node",
+   "abbreviation": "GCP",
+   "label": "Ground control points",
+   "description": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete).",
+   "s3Dgraphy_file": "georeferencing_node.py",
+   "mapping": {
+    "cidoc": "crm:E73_Information_Object",
+    "cidoc_s3d": null,
+    "alternative": "prov:Entity",
+    "rationale": "A control set is an INFORMATION OBJECT: a documented list of measured places and where each was observed. It is not itself a Place (crm:E53) nor a Measurement (crmsci:S21) — it CARRIES both. The individual observations stay payload literals in v1 and the explicit refinement is declared, not implied: each point would explode into an crmsci:S21_Measurement of an crm:E53_Place observed on a crmdig:D1 photograph. Doing that now would create three nodes per control point in a graph nobody yet reads that way."
+   },
+   "em_extension": {
+    "uri": "em:GCPSet",
+    "rdf_type": "owl:Class",
+    "subclass_of": [
+     "crm:E73_Information_Object"
+    ],
+    "extension_status": "proposed",
+    "rationale": "Named in the EM extension because 'the set of control points behind this registration' is the unit archaeologists actually hand each other, and CIDOC has no class for it above E73."
+   }
+  },
+  "RegistrationTransformNode": {
+   "class": "RegistrationTransformNode",
+   "parent": "Node",
+   "abbreviation": "RGT",
+   "label": "Registration transform",
+   "description": "The 7-parameter similarity (rotation 3x3 row-major, translation [x,y,z], positive scale) that places a produced model, with data.rms and data.residuals — the error bar, stored beside the claim rather than in a log nobody keeps. data.crs is the frame the model lands IN; null means a site-local frame (mode 'local'), which is NOT the same sentence as an absent transform. Re-registration is a NEW node produced by a NEW crmdig:D7; the superseded one is never edited.",
+   "s3Dgraphy_file": "georeferencing_node.py",
+   "mapping": {
+    "cidoc": "crm:E73_Information_Object",
+    "cidoc_s3d": null,
+    "alternative": "prov:Entity",
+    "rationale": "The transform is an information object that DESCRIBES a mapping between two spatial reference systems (crmgeo:SP4_Spatial_Coordinate_Reference_System). CIDOC/CRMgeo models coordinate systems and geometric expressions but has no class for the parameterised map between two of them, so E73 is the honest superclass and the specificity lives in em:RegistrationTransform. It is deliberately NOT an event: the ACT of registering is the crmdig:D7 that produced this object."
+   },
+   "em_extension": {
+    "uri": "em:RegistrationTransform",
+    "rdf_type": "owl:Class",
+    "subclass_of": [
+     "crm:E73_Information_Object"
+    ],
+    "extension_status": "proposed",
+    "relates": "two crmgeo:SP4_Spatial_Coordinate_Reference_System",
+    "rationale": "Proposed rather than asserted: the natural CRM-native alternative is to leave the parameters as literals on the D7 event, which loses the ability to point at 'the placement' as a thing that gets superseded — and superseding it is the whole reason mode (b) exists."
+   }
+  }
+ },
  "narrative_nodes": {
   "_section_note": "EM Narrative (DP-79, draft). A narrative is the story told OVER a graph: chapters anchored to the graph's lanes (epochs, activities), each carrying prose and embeds. It is a first-class node so it can be queried ('which narratives cite this US', 'which rest on a withdrawn source'), versioned and carried through the DTC. Chapters and blocks are NOT nodes: they are ordered structures inside node.data — EM has no ordered-edge primitive, and a chapter has no existence apart from its narrative. An embed holds only the stable id of the resource it shows, never a copy of it, so a narrative always says what the graph currently says.",
   "NarrativeNode": {

s3dgraphy-1.6.0.dev17/src/s3dgraphy/JSON_config/src/2D/gcp_set.svg

@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!-- EM · GCPSetNode. A survey target seen from above: the crosshair is one control point, the three small marks around it are the SET — the node is the set, never the single GCP. Drawn for Extended Matrix, same licence as the datamodel. -->
+<circle cx="256" cy="248" r="96" fill="#FFFFFF" stroke="#FF6600" stroke-width="26"/>
+<circle cx="256" cy="248" r="26" fill="#FF6600"/>
+<path fill="#FF6600" d="M242 96h28v72h-28zM242 328h28v72h-28zM104 234h72v28h-72zM336 234h72v28h-72z"/>
+<circle cx="72" cy="432" r="26" fill="#FF6600"/>
+<circle cx="256" cy="464" r="26" fill="#FF6600"/>
+<circle cx="440" cy="432" r="26" fill="#FF6600"/>
+</svg>

s3dgraphy-1.6.0.dev17/src/s3dgraphy/JSON_config/src/2D/graph.svg

@@ -0,0 +1,6 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!-- EM · GraphNode. The graph itself, as a container: three nodes and the edges between them. Neutral gray (#333333, the GRAPH style's own colour) so it stays visually distinct from stratigraphic and paradata nodes — it is the meta-container, not a unit. Drawn for Extended Matrix, same licence as the datamodel. -->
+<path fill="none" stroke="#333333" stroke-width="26" stroke-linecap="round" d="M256 132v120M256 252 148 372M256 252l108 120"/>
+<circle cx="256" cy="108" r="60" fill="#FFFFFF" stroke="#333333" stroke-width="26"/>
+<circle cx="124" cy="396" r="60" fill="#FFFFFF" stroke="#333333" stroke-width="26"/>
+<circle cx="388" cy="396" r="60" fill="#FFFFFF" stroke="#333333" stroke-width="26"/>
+</svg>

s3dgraphy-1.6.0.dev17/src/s3dgraphy/JSON_config/src/2D/registration_transform.svg

@@ -0,0 +1,6 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!-- EM · RegistrationTransformNode. Three axes and the arc that turns them: the 7-parameter similarity that places a model. The arc is the rotation, the axes the frame it lands in. Drawn for Extended Matrix, same licence as the datamodel. -->
+<path fill="none" stroke="#FF6600" stroke-width="28" stroke-linecap="round" d="M152 360V152M152 360h208"/>
+<path fill="#FF6600" d="M152 92l40 72h-80zM420 360l-72 40v-80z"/>
+<path fill="none" stroke="#FF6600" stroke-width="28" stroke-linecap="round" d="M152 360 262 250"/>
+<path fill="none" stroke="#FF6600" stroke-width="22" stroke-linecap="round" stroke-dasharray="34 30" d="M340 168a136 136 0 0 1 44 100"/>
+</svg>

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/__init__.py

@@ -1,4 +1,4 @@
-__version__ = "1.6.0.dev16"
+__version__ = "1.6.0.dev17"
 __datamodel_version__ = "1.5.5"  # s3Dgraphy connections datamodel version
 
 # s3Dgraphy/__init__.py

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/api.py

@@ -3,7 +3,7 @@
 A single, documented set of **pure operations** over the Extended Matrix graph:
 load/parse, validate, project → TTL/RDF, GraphML/XLSX interop, authority
 resolution. This is the stable contract that the local **em-bridge** sidecar and
-the future **em-server** (HTTP) both drive — the library itself stays pure:
+the future **StratiGraph Server** (HTTP) both drive — the library itself stays pure:
 
   * NO web framework here (no FastAPI/uvicorn/HTTP). Transports wrap this surface.
   * Heavy/optional deps (lxml for GraphML, pandas for XLSX, rdflib for RDF) are
@@ -349,7 +349,7 @@ def apply_op(section: Dict[str, Any], op: Dict[str, Any]) -> Dict[str, Any]:
 
     Returns a **dict** (`{applied, reason, node_id, fields}`), not the internal
     dataclass: this is the api surface, which is what another PROCESS talks to
-    (em-server puts the answer straight on a socket). Handing a caller across
+    (StratiGraph Server puts the answer straight on a socket). Handing a caller across
     that boundary an object it has to know the shape of is how a library leaks
     into a transport.
     """
@@ -453,7 +453,7 @@ def promote_resource(graph: Graph, resource_id: str, *, url: str, sha256: str,
 
     `residency` says which true sentence this is — `reference` (a store the study
     points at, the default and the original DP-76 one) or `resident` (the ROOM's
-    store: em-server is in the bytes' path, so the gate and the licence travel
+    store: StratiGraph Server is in the bytes' path, so the gate and the licence travel
     with them). `corpus` is the offline→online moment: hand it the container's
     DOCUMENTATION member and the D7 event is recorded THERE, with the asset
     mirrored into it under its own id — the shared leaf between the study and its
@@ -493,7 +493,7 @@ def dtc_corpus(container: Any, *, create: bool = True) -> Optional[Graph]:
 def merge_corpus(resident: Any, incoming: Any) -> Dict[str, Any]:
     """Fold one DTC corpus into another, per UUID. Returns the report as a dict.
 
-    On the api surface because another PROCESS performs it: em-server merges a
+    On the api surface because another PROCESS performs it: StratiGraph Server merges a
     project's **file** corpus into the instance's **resident** one when a study is
     promoted or joins a room, and it must not invent a second answer to "who
     wins". Same merge the container uses. See :mod:`s3dgraphy.dtc.corpus`.
@@ -535,7 +535,7 @@ def store_backed_geometry(graph: Graph) -> List[Dict[str, Any]]:
     `has_linked_resource` would drift the day a facet is added.
 
     `reference` resources are deliberately absent: their bytes are outside the
-    store (and outside em-server's gate), so a digest cannot fetch them and a
+    store (and outside StratiGraph Server's gate), so a digest cannot fetch them and a
     path is meaningful on one machine only. See
     :mod:`s3dgraphy.geometry.store_backed`.
     """
@@ -623,7 +623,7 @@ def study_metadata(container: Any, *, study_id: Optional[str] = None
     """The catalogue card of one study, derived from its em.json container.
 
     On the api surface because it is what another PROCESS asks for: a catalogue
-    (em-catalog, and 3DR's production one) turns containers into an index, and
+    (StratiGraph Catalog, and 3DR's production one) turns containers into an index, and
     the rule that makes the index safe is that it is a **projection** — every
     field comes from the container, so re-reading the containers rebuilds it.
     An indexer that had to know where a licence lives would be a second truth
@@ -645,7 +645,7 @@ def asset_rights(document: Any, digest: str, *, today: Any = None
 
     On the api surface for the same reason `study_metadata` is: another PROCESS
     asks it. An asset store must decide whether to serve bytes, and the decision
-    belongs to the graph — em-server CONSULTS this rather than keeping a second
+    belongs to the graph — StratiGraph Server CONSULTS this rather than keeping a second
     copy of an embargo that lives in a document people edit.
 
     See :mod:`s3dgraphy.rights` for how the walk works and why the rights are
@@ -774,6 +774,71 @@ def batch_summary(graph: Graph, acquisition_id: str) -> Dict[str, Any]:
     return _summary(graph, acquisition_id)
 
 
+# ── photogrammetry: what a reconstruction MEANS ──────────────────────────────
+#
+# The MEANING, not the machinery. Driving an engine (REST, a task queue, an
+# archive) is node-side plumbing and lives in StratiGraph Server; what is on this
+# surface is the semantic contract it calls with the result. A second engine —
+# COLMAP, MicMac, Aïoli — is a second driver calling the same function.
+
+def build_photogrammetry_delta(*, input_resources, output_model,
+                               transform=None, gcp_set=None,
+                               author: Optional[str] = None,
+                               mode: str = "local", **kwargs) -> Dict[str, Any]:
+    """The DTC provenance of one reconstruction, as a delta somebody applies.
+
+    `output_model` is a :class:`~s3dgraphy.photogrammetry.ProducedModel` (or
+    build one with :func:`produced_model`): the bytes are already published when
+    this is called, and their checksum is what the resource points at.
+
+    `mode` is `"local"` (scaled and oriented in a site frame — honestly NOT
+    georeferenced) or `"absolute"` (registered against ground control points).
+    The two are different SHAPES in the graph, not a flag, and the refusals that
+    keep them apart are in :mod:`s3dgraphy.photogrammetry.delta`.
+
+    Returns a dict — ids, the delta, the warnings — because the caller is on the
+    other side of an HTTP boundary.
+    """
+    from .photogrammetry import build_photogrammetry_delta as _build
+    return _build(input_resources=input_resources, output_model=output_model,
+                  transform=transform, gcp_set=gcp_set, author=author,
+                  mode=mode, **kwargs).as_dict()
+
+
+def produced_model(checksum: str, *, url: Optional[str] = None,
+                   media_type: Optional[str] = None,
+                   residency: str = "resident",
+                   name: Optional[str] = None,
+                   node_id: Optional[str] = None):
+    """The output of a reconstruction, described. Built here so a caller does
+    not import the class to state four facts."""
+    from .photogrammetry import ProducedModel
+    return ProducedModel(checksum=checksum, url=url, media_type=media_type,
+                         residency=residency, name=name, node_id=node_id)
+
+
+def gcp_set(node_id: str, points, *, crs: Optional[str] = None,
+            name: str = "Ground control points"):
+    """A control set, validated on construction. Raises on a point that
+    controls nothing (no id, no world coordinate, an observation with no image
+    or no pixel) — before an engine spends an hour on it."""
+    from .nodes.georeferencing_node import GCPSetNode
+    return GCPSetNode(node_id, name=name, points=list(points), crs=crs)
+
+
+def registration_transform(node_id: str = "registration", *,
+                           rotation=None, translation=None, scale: float = 1.0,
+                           crs: Optional[str] = None, rms: Optional[float] = None,
+                           residuals=None, name: str = "Registration"):
+    """A placement, stated. Optional: `build_photogrammetry_delta` makes the
+    canonical one for the mode when none is given — pass one only when the
+    engine reported real parameters."""
+    from .nodes.georeferencing_node import RegistrationTransformNode
+    return RegistrationTransformNode(node_id, name=name, rotation=rotation,
+                                     translation=translation, scale=scale,
+                                     crs=crs, rms=rms, residuals=residuals)
+
+
 # ── IIIF: the image layer, as a projection ────────────────────────────────────
 def iiif_manifest(graph: Graph, target_id: str, *, image_base: str,
                   manifest_id: Optional[str] = None,
@@ -2427,6 +2492,46 @@ def mapping_apply(mapping: Dict[str, Any], source: str, *, graph: Any = None,
                          mapping_name=mapping_name)
 
 
+def mapping_target_groups(*, include_direct: bool = True
+                          ) -> List[Dict[str, Any]]:
+    """The target catalog GROUPED BY ONTOLOGY — CIDOC-CRM · CRMarchaeo · CRMdig ·
+    CRMgeo · CRMinf · HDT-O · PROV-O — each group with the version the datamodel
+    declares for it.
+
+    A curated subset of CIDOC by construction: exactly what the datamodel
+    declares and not one class more. No OWL is parsed and no checkout of the
+    ontologies is read — so when E.D. refines the CIDOC/HDT-O mapping, the picker
+    follows on its own."""
+    from .mappings.authoring import target_groups
+    return target_groups(include_direct=include_direct)
+
+
+def mapping_edge_groups(source_type: Optional[str] = None,
+                        target_type: Optional[str] = None
+                        ) -> List[Dict[str, Any]]:
+    """The same grouping for the edges: the CIDOC property beside each EM edge,
+    under the ontology that defines it. `unmapped` holds the edges the datamodel
+    maps only through an extension property."""
+    from .mappings.authoring import edge_groups
+    return edge_groups(source_type, target_type)
+
+
+def mapping_ontologies() -> Dict[str, Dict[str, Any]]:
+    """The ontologies this datamodel speaks, with versions and sources — the same
+    `referenced_ontology_versions` block EMStudio's Reference-ontologies panel
+    prints."""
+    from .mappings.authoring import ontologies
+    return ontologies()
+
+
+def mapping_source_extensions() -> Dict[str, str]:
+    """`{extension: format}` for the sources a mapping can describe — so a file
+    picker's filter and a file browser's greying come from the library instead of
+    a list written beside them."""
+    from .mappings.authoring import source_extensions
+    return source_extensions()
+
+
 def mapping_property_node_type() -> str:
     """The node type a PROPERTY column produces, read from the datamodel — so an
     editor says "this field is a property" without typing a class name."""

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev17}/src/s3dgraphy/container.py

@@ -43,7 +43,7 @@ limit. Only a field they both wrote is a decision, and it is reported per field.
 
 What this module deliberately does NOT do:
 
-* **real-time transport.** The relay (em-server: fan-out + op-log + presence) is
+* **real-time transport.** The relay (StratiGraph Server: fan-out + op-log + presence) is
   P4.2, and the client is P4.3. The algebra converges without a coordinator,
   which is exactly why it can be built and proved first, on a table.
 * **tombstone GC.** Deletions stay as marks; compacting them belongs to the
@@ -348,7 +348,7 @@ def build_container(container: Container) -> Dict[str, Any]:
     #
     # The builder owns the keys that describe the FORMAT and nothing more. What a
     # header also carries is the caller's: `visibility` (which decides whether a
-    # study is served without a token — em-server reads it for rooms, em-catalog
+    # study is served without a token — StratiGraph Server reads it for rooms, StratiGraph Catalog
     # for studies), `title`, `description`. Rebuilding the header from scratch
     # DROPPED them, so a container that said "public" came back from its own file
     # saying nothing, and the default is restricted — a study quietly