@mat3ra/esse 2026.8.27-0 → 2026.8.31-0

package/README.md

@@ -12,7 +12,7 @@ The latest variants of schemas and examples are available at [schemas.mat3ra.com
 
 - **[Documentation](https://schemas.mat3ra.com/docs/)** — how ESSE is put together and why: the schema layering, entity anatomy, categorization, conventions and the build pipeline. Start here if you are new.
 - **[Explorer](https://schemas.mat3ra.com/)** — a file browser over every resolved schema and example.
-- **[Entity Map](https://schemas.mat3ra.com/map/)** — an interactive map of all schemas and the references between them, laid out by architectural layer: primitives at the centre, root entities around them, catalogues on the rim. Search for a schema, fly to it, and follow what it extends, contains and is used by.
+- **[Ontology](https://schemas.mat3ra.com/map/)** — an interactive map of the ontology: every entity type and every relationship the schemas declare between them (`extends`, `contains`, `variant`), laid out by architectural layer — primitives at the centre, root entities around them, catalogues on the rim. Search for a schema, fly to it, and follow what it extends, contains and is used by.
 
 The map is built from `graph.json`, an extracted reference graph that is also published at [schemas.mat3ra.com/graph.json](https://schemas.mat3ra.com/graph.json) and doubles as a lint over the corpus.
 
@@ -160,7 +160,7 @@ The following outlines the development process workflow:
 2. Edit code and commit changes.
 3. Pre commit is used to regenerate the modules.
 4. Push the changes to GitHub.
-5. GH workflow is used to generate the fully resolved file (without "$ref"s and "$allOf" etc.) and examples, render the documentation and the Entity Map, and publish them to [schemas.mat3ra.com](http://schemas.mat3ra.com/). The site is assembled in a gitignored `site/` staging directory; internal links are checked before it deploys.
+5. GH workflow is used to generate the fully resolved file (without "$ref"s and "$allOf" etc.) and examples, render the documentation and the ontology map, and publish them to [schemas.mat3ra.com](http://schemas.mat3ra.com/). The site is assembled in a gitignored `site/` staging directory; internal links are checked before it deploys.
 6. Publish the new version of the package to PyPI and npm.
 
 The [pre-commit](.husky/pre-commit) is using both JS and PY runtime(s) to regenerate the schemas and examples.

package/dist/js/scripts/buildDocsPages.js

@@ -157,6 +157,28 @@ function categorizationSchemesFragment(graph) {
 
 Entities carrying a tiered \`categories\` field: ${carrierList || "_none_"}.`;
 }
+/**
+ * The three relation kinds, with their ontological reading alongside the JSON Schema
+ * keyword that expresses each. Counts come from the graph, so the prose calling these
+ * "the familiar ontological relations" cannot drift from what the corpus declares.
+ */
+function ontologyRelationsFragment(graph) {
+    const kinds = [
+        ["`extends`", "`allOf`", "**is a** (subsumption)", "extends"],
+        ["`contains`", "`properties` / `items`", "**has a** (composition)", "contains"],
+        ["`variant`", "`oneOf` / `anyOf`", "**is one of** (disjunction)", "variant"],
+    ];
+    const counts = graph.meta.edgeCountsByKind;
+    const rows = kinds.map(([relation, keyword, reading, key]) => [
+        relation,
+        keyword,
+        reading,
+        String(counts[key]),
+    ]);
+    return `${table(["Relation", "Declared by", "Reads as", "Edges"], rows)}
+
+Across ${graph.meta.nodeCount} entity types, ${graph.meta.edgeCount} declared relationships.`;
+}
 function layerInventoryFragment(graph) {
     const rows = Object.entries(graph.meta.layerCounts)
         .sort((a, b) => b[1] - a[1])
@@ -186,6 +208,8 @@ function expandFragments(body, graph) {
                 ]);
             case "layer-inventory":
                 return layerInventoryFragment(graph);
+            case "ontology-relations":
+                return ontologyRelationsFragment(graph);
             case "categorization-schemes":
                 return categorizationSchemesFragment(graph);
             case "hub-table":
@@ -215,18 +239,19 @@ function renderPage(page, pages, html) {
 <head>
     <meta charset="UTF-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>${escapeHtml(page.title)} — ESSE</title>
+    <title>${escapeHtml(page.title)} — AI4Materials</title>
     <meta name="description" content="${escapeHtml(page.summary)}">
     <link rel="stylesheet" href="docs.css">
 </head>
 <body>
 <div id="titlebar">
-    <span class="app-name">ESSE</span>
+    <span class="app-name">AI4Materials<span class="app-name-suffix">: data standards</span></span>
     <nav id="surfaces">
         <a href="index.html" class="current">Docs</a>
         <a href="../index.html">Explorer</a>
-        <a href="../map/index.html">Map</a>
+        <a href="../map/index.html">Ontology</a>
     </nav>
+    <span id="titlebar-tagline">ESSE &middot; materials science ontology</span>
 </div>
 <div id="workspace">
     <aside id="docs-nav">
@@ -283,10 +308,15 @@ body {
     z-index: 5;
 }
 #titlebar .app-name { color: var(--text-primary); font-weight: 600; }
+/* Completes the wordmark so the name never reads as a dangling fragment. */
+#titlebar .app-name-suffix { color: var(--text-muted); font-weight: 400; }
+@media (max-width: 700px) { #titlebar .app-name-suffix { display: none; } }
 #surfaces { display: flex; gap: 14px; }
 #surfaces a { color: var(--text-muted); text-decoration: none; }
 #surfaces a:hover { color: var(--text-primary); }
 #surfaces a.current { color: var(--text-primary); border-bottom: 2px solid var(--accent); }
+#titlebar-tagline { margin-left: auto; color: var(--text-muted); }
+@media (max-width: 640px) { #titlebar-tagline { display: none; } }
 #workspace { display: flex; flex: 1; align-items: flex-start; }
 #docs-nav {
     width: 250px;

package/dist/js/scripts/checkSiteLinks.js

@@ -8,7 +8,7 @@ exports.checkSiteLinks = checkSiteLinks;
  * Verifies that every internal link in the assembled site resolves.
  *
  * The site is stitched together from four sources — resolved schemas, the concept docs, the
- * explorer and the Entity Map — each of which links into the others. Nothing else checks that
+ * explorer and the ontology map — each of which links into the others. Nothing else checks that
  * those links land anywhere, and a stale href is invisible until someone clicks it.
  *
  * External URLs are not fetched; this is a build step, not a crawler.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@mat3ra/esse",
-    "version": "2026.8.27-0",
+    "version": "2026.8.31-0",
     "description": "Mat3ra's Excellent Source of Schemas and Examples (ESSE) for Digital Materials R&D",
     "scripts": {
         "transpile": "tsc -p tsconfig-transpile.json",