feat(acms): operationalize UKO runtime with provenance tracking and temporal versioning #891

Closed
opened 2026-03-13 23:27:53 +00:00 by freemo · 3 comments
Owner

Metadata

  • Commit Message: feat(acms): operationalize UKO runtime with provenance and temporal versioning
  • Branch: feature/m6-uko-runtime

Background and Context

The specification describes the Universal Knowledge Ontology (UKO) as an "RDF-based, inheritance-driven ontology representing resources at multiple abstraction levels with provenance and temporal versioning." The UKO has four layers: universal foundation, domain specializations, paradigm/format specializations, and technology-specific.

The codebase has UKO infrastructure:

  • domain/models/core/uko.py: UKOPrefix, UKONode, UKOVersion, UKOOntology
  • domain/models/acms/provenance.py: ProvenanceMetadata, ProvenancedTriple, IndexResult
  • application/services/uko_indexer.py: UKO indexing service
  • application/services/uko_loader.py: Ontology loader

However, no existing Forgejo issue tracks the operationalization of this subsystem. The UKO indexer exists but its runtime integration with the ACMS context pipeline — specifically the semantic relationship inference, temporal versioning, and provenance tracking described in the spec — is not tracked.

Expected Behavior

The UKO should:

  1. Maintain an RDF-based ontology that classifies indexed resources
  2. Track provenance metadata (source, confidence, extraction method) for each triple
  3. Support temporal versioning so context strategies can query historical states
  4. Infer implicit relationships from content analysis
  5. Feed classification data into the ACMS context assembly pipeline

Acceptance Criteria

  • UKO indexer produces typed triples with provenance metadata
  • Temporal versioning tracks ontology state across indexing runs
  • ACMS context strategies can query UKO for resource classification
  • Four ontology layers are populated: universal, domain, paradigm, technology
  • Implicit relationship inference runs during indexing
  • UKO data persists across application restarts

Subtasks

  • Verify UKO indexer produces provenance-annotated triples
  • Implement temporal versioning (revision chain) for UKO state
  • Wire UKO query interface into ACMS context strategies
  • Populate four ontology layers during resource indexing
  • Add implicit relationship inference (semantic analysis)
  • Persist UKO graph to storage backend
  • Tests (Behave): Indexing produces typed triples, temporal query, provenance
  • Verify coverage >= 97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
## Metadata - **Commit Message**: `feat(acms): operationalize UKO runtime with provenance and temporal versioning` - **Branch**: `feature/m6-uko-runtime` ## Background and Context The specification describes the Universal Knowledge Ontology (UKO) as an "RDF-based, inheritance-driven ontology representing resources at multiple abstraction levels with provenance and temporal versioning." The UKO has four layers: universal foundation, domain specializations, paradigm/format specializations, and technology-specific. The codebase has UKO infrastructure: - `domain/models/core/uko.py`: `UKOPrefix`, `UKONode`, `UKOVersion`, `UKOOntology` - `domain/models/acms/provenance.py`: `ProvenanceMetadata`, `ProvenancedTriple`, `IndexResult` - `application/services/uko_indexer.py`: UKO indexing service - `application/services/uko_loader.py`: Ontology loader However, no existing Forgejo issue tracks the operationalization of this subsystem. The UKO indexer exists but its runtime integration with the ACMS context pipeline — specifically the semantic relationship inference, temporal versioning, and provenance tracking described in the spec — is not tracked. ## Expected Behavior The UKO should: 1. Maintain an RDF-based ontology that classifies indexed resources 2. Track provenance metadata (source, confidence, extraction method) for each triple 3. Support temporal versioning so context strategies can query historical states 4. Infer implicit relationships from content analysis 5. Feed classification data into the ACMS context assembly pipeline ## Acceptance Criteria - [ ] UKO indexer produces typed triples with provenance metadata - [ ] Temporal versioning tracks ontology state across indexing runs - [ ] ACMS context strategies can query UKO for resource classification - [ ] Four ontology layers are populated: universal, domain, paradigm, technology - [ ] Implicit relationship inference runs during indexing - [ ] UKO data persists across application restarts ## Subtasks - [ ] Verify UKO indexer produces provenance-annotated triples - [ ] Implement temporal versioning (revision chain) for UKO state - [ ] Wire UKO query interface into ACMS context strategies - [ ] Populate four ontology layers during resource indexing - [ ] Add implicit relationship inference (semantic analysis) - [ ] Persist UKO graph to storage backend - [ ] Tests (Behave): Indexing produces typed triples, temporal query, provenance - [ ] Verify coverage >= 97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.
freemo added this to the v3.6.0 milestone 2026-03-13 23:30:33 +00:00
Author
Owner

Dependencies / Related Issues:

  • Related: #872 (graph backend — UKO triples need a graph backend for persistence and SPARQL queries)
  • The UKO runtime operationalization depends on a functional graph backend. If #872 is not yet complete, the UKO can use InMemoryGraphBackend as a temporary store.
**Dependencies / Related Issues:** - Related: #872 (graph backend — UKO triples need a graph backend for persistence and SPARQL queries) - The UKO runtime operationalization depends on a functional graph backend. If #872 is not yet complete, the UKO can use `InMemoryGraphBackend` as a temporary store.
freemo self-assigned this 2026-04-02 06:13:59 +00:00
Author
Owner

[Backlog Groomer - groomer-1] 📋 Label state mismatch. This issue has State/Verified but PR #1312 (feat(acms): operationalize UKO runtime with provenance and temporal verification) is open and references this issue. The state should be updated to State/In Review.

**[Backlog Groomer - groomer-1]** 📋 **Label state mismatch.** This issue has `State/Verified` but PR #1312 (`feat(acms): operationalize UKO runtime with provenance and temporal verification`) is open and references this issue. The state should be updated to `State/In Review`.
Author
Owner

PR #1312 reviewed, approved, and merged.

The UKO runtime has been operationalized with:

  • Provenance tracking (sourceResource, validFrom, isCurrent)
  • Temporal versioning via revision chains
  • ACMS context strategy integration via UKOQueryInterface
  • Four-layer ontology population (universal, domain, paradigm, technology)
  • Implicit relationship inference (sibling, containment, dependency)
  • Graph persistence across application restarts

47 BDD scenarios verify all acceptance criteria.

PR #1312 reviewed, approved, and merged. The UKO runtime has been operationalized with: - Provenance tracking (sourceResource, validFrom, isCurrent) - Temporal versioning via revision chains - ACMS context strategy integration via `UKOQueryInterface` - Four-layer ontology population (universal, domain, paradigm, technology) - Implicit relationship inference (sibling, containment, dependency) - Graph persistence across application restarts 47 BDD scenarios verify all acceptance criteria.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#891
No description provided.