Feature Request: Automatic dynamic ontology expansion from coverage gaps

Open
#584 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
ai

Research direction

Start by reading docs/handovers/dynamic-ontology-handover.md and docs/src/dynamic-ontology.md, then trace the pipeline's CoverageSignal.coverage_ratio and unmatched-entity flow. Done means candidates are generated, approval gates updates, ontology changes are deterministic and auditable, reloads work without restart regressions, and an integration test covers the gap-to-approved-update flow.

Written by the indexing model from the issue text.

Description

Summary

Implement automatic ontology expansion when coverage signals indicate low grounding quality.

Context

The dynamic ontology handover identifies this as the next step after feature-gate and normalization example rollout.

Problem

Current pipeline reports coverage gaps but does not autonomously propose/apply ontology additions.

Proposed Scope

  • Add expansion workflow triggered by low CoverageSignal.coverage_ratio.
  • Generate candidate terms from unmatched entities.
  • Add guarded review/approval step before writing ontology updates.
  • Persist changes in a deterministic, auditable format.

Acceptance Criteria

  • Expansion candidates generated from unmatched terms
  • Review gate prevents unsafe/unwanted automatic additions
  • Updated ontology can be reloaded without service restart regressions
  • Integration test covers gap->candidate->approved-update flow

References

  • docs/handovers/dynamic-ontology-handover.md
  • docs/src/dynamic-ontology.md
Dominant language
Rust
Stars
62
Forks
5
Avg merge
2h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from terraphim/terraphim-ai

All issues in terraphim/terraphim-ai

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.