diff --git a/_data/nav.yml b/_data/nav.yml
index 294ea75..36d6dfd 100644
--- a/_data/nav.yml
+++ b/_data/nav.yml
@@ -4,12 +4,12 @@
 - name: Releases
   submenuitems:
     - name: Latest Release
-      link: /releases/1.4.0/
+      link: /releases/1.5.0/
     - name: Archived Releases
       link: /releases/archive/
     - name: SPACE
-    - name: Under Development (1.5.0)
-      link: /releases/1.5.0/
+    - name: Under Development (1.6.0)
+      link: /releases/1.6.0/
     - name: Under Development (2.0.0)
       link: /releases/2.0.0/
 - name: Ontology
diff --git a/_data/releases/releases.yml b/_data/releases/releases.yml
index 1450973..bb1aa64 100644
--- a/_data/releases/releases.yml
+++ b/_data/releases/releases.yml
@@ -40,3 +40,6 @@
 - title: 1.4.0
   date: 2025-05-28
   desc: UCO 1.4.0 includes additive updates and further preparations for backwards-incompatible changes in preparation for UCO 2.0.0.  New classes include subclasses of <code>types:Dictionary</code> that respond differently to key non-uniqueness.  New properties include <code>core:informalType</code> and <code>core:objectStatus</code>.  New property associations include <code>observable:cpeid</code> on <code>observable:DeviceFacet</code>.  <code>core:ContextualCompilation</code> is now permitted to have 0 contained objects.  Revisions for UCO 2.0.0 now have warnings in place for current data behaviors that would be either passively addressed or considered errors in UCO 2.0.0, for <code>observable:AlternateDataStream</code>, <code>observable:Disk</code>, <code>observable:OperatingSystem</code>, <code>observable:ObservableRelationship</code>, <code>types:Thread</code>, <code>types:ThreadItem</code>, <code>core:UcoObject</code>, <code>core:UcoInherentCharacterizationThing</code>, and all semi-open vocabulary literals.
+- title: 1.5.0
+  date: 2026-07-24
+  desc: UCO 1.5.0 includes a mechanism for framework developers to manage a catalogue of enumerated classes of actions.  The UCO Action namespace now has UCO's first meta-class, `Technique,` whose instances are specialized, enumerable, and testable subclasses of `Action`.  The design also supports `Technique`s being extended by `Technique`s in separate frameworks.
diff --git a/releases/1.4.0/index.md b/releases/1.4.0/index.md
index 4b0d7a4..324c40e 100644
--- a/releases/1.4.0/index.md
+++ b/releases/1.4.0/index.md
@@ -11,6 +11,8 @@ custom_css: releases
 
 ## Ontology File(s)
 
+[GitHub](https://github.com/ucoProject/UCO/releases/tag/1.4.0)
+
 
 ## Release Notes
 
diff --git a/releases/1.5.0/index.md b/releases/1.5.0/index.md
index 15bc347..07f9c30 100644
--- a/releases/1.5.0/index.md
+++ b/releases/1.5.0/index.md
@@ -6,14 +6,20 @@ custom_css: releases
 
 # {{ page.title }}
 
-*Date: TBD*
+*Date: 2026-07-24*
 
 
 ## Ontology File(s)
 
+[GitHub](https://github.com/ucoProject/UCO/releases/tag/1.5.0)
+
 
 ## Release Notes
 
+UCO 1.5.0 incorporates required refinements and updates, building on the stable 1.0.0 release.  Following [SemVer](https://semver.org/spec/v2.0.0.html), additive improvements will continue to be accepted, but backwards-incompatible changes will be scheduled only for the 2.0.0 release, which will come after at least 6 months to possibly 12 months.
+
+This release introduces a mechanism for framework developers to manage a catalogue of enumerated classes of actions.  The UCO Action namespace now defines UCO's first meta-class, `Technique,` whose instances are themselves specialized subclasses of `Action`.  This adds a third tier above the usual two-tier class structure: the `Technique` meta-class, the `Technique` classes that instantiate it, and the `Actions` that instantiate those.  This design allows a specific `Action` to *follow* a general `Technique` explicitly by being typed with that `Technique` class, and enables SHACL validation of requirements specific to that `Technique`.  For instance, a disk imaging `Technique` can require a device of a certain class, such as a hardware write blocker.  Then an `Action` can *follow* this `Technique` using a specific disk imaging tool with a given hardware write blocker. A `Technique` class can refine one or more parent `Techniques` bringing the benefits of inheretance and multi-classing. The design supports controlled collection of `Action`-subclasses within a framework, and also supports extension of one framework's `Techniques` by another, while keeping clear the framework within which any `Technique`---extension or not---is defined.
+
 
 ### Focus
 
@@ -41,3 +47,11 @@ custom_css: releases
 
 
 ## Documentation
+
+Generated documentation is available at this site:
+
+[https://ontology.unifiedcyberontology.org/](https://ontology.unifiedcyberontology.org/)
+
+Be aware that the documentation at that site will only show the most recent release.  The upper-left corner of the documentation pages shows the ontology version being reviewed.
+
+After the following UCO release, users interested seeing the rendered documentation at this version "Back in time" should locally clone the repository, check out [this branch](https://github.com/ucoProject/ontology.unifiedcyberontology.org/tree/archive/release-1.5.0), and follow the deployment directions in `CONTRIBUTE.md`.
diff --git a/releases/1.6.0/index.md b/releases/1.6.0/index.md
new file mode 100644
index 0000000..15cb77b
--- /dev/null
+++ b/releases/1.6.0/index.md
@@ -0,0 +1,33 @@
+---
+title: 1.6.0 Release
+layout: releases
+custom_css: releases
+---
+
+# {{ page.title }}
+
+*Date: TBD*
+
+
+## Ontology File(s)
+
+
+## Release Notes
+
+
+### Focus
+
+
+#### Breaking Changes
+
+*(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)*
+
+
+#### Changes
+
+*(These are changes to ontologies, classes or properties in the preexisting ontology.)*
+
+
+#### Bug Fixes
+
+*(These are bugs found within the preexisting ontology that have been fixed.)*