lg-ontology

Category: Tools & Productivity | Uploader: tteggu87 | Downloads: 0 | Version: v1.0（Latest）

Extend lightweight-ontology-core into a lightweight graph workflow without replacing canonical JSONL truth. Use when documents, notes, research memos, repository guidance, finance notes, chat logs, or educational material already use lightweight ontology registries and you want graph projection, graph-style neighborhood/path inspection, Ladybug-ready exports, or baseline-vs-graph comparison tests. Trigger for requests to copy or adapt lightweight-ontology-core for graph exploration, prepare a Ladybug projection layer, inspect multi-hop neighborhoods, or compare direct JSONL reasoning against graph-assisted exploration. Do not use this to replace canonical JSONL with a graph DB or to design a full GraphRAG platform from scratch.

Changelog: Source: GitHub https://github.com/tteggu87/DocTology

Directory Structure

Current level: tree/main/.agents/skills/lg-ontology/

📁 agents/
- 📄 openai.yaml 270 B
📁 assets/
- 📁 context/
  - 📄 context.template.jsonld 567 B
- 📁 docs/
  - 📄 ONTOLOGY_OPERATING_MODEL.template.md 2.2 KB
- 📁 intelligence/
  - 📄 document_types.template.yaml 1.5 KB
  - 📄 relations.template.yaml 3.5 KB
- 📁 packs/
  - 📁 education/
    
    📄 document_types.template.yaml 1.1 KB
    
    📄 inference.template.yaml 10 B
    
    📄 relations.template.yaml 2.9 KB
  - 📁 finance/
    
    📄 document_types.template.yaml 1.1 KB
    
    📄 inference.template.yaml 10 B
    
    📄 relations.template.yaml 3.1 KB
  - 📁 work-docs/
    
    📄 document_types.template.yaml 1.2 KB
    
    📄 inference.template.yaml 10 B
    
    📄 relations.template.yaml 3.0 KB
  - 📄 README.md 953 B
- 📁 retrieval/
  - 📄 chroma_collection.template.yaml 498 B
- 📁 rules/
  - 📄 inference.template.yaml 525 B
- 📁 schemas/
  - 📄 warehouse_core.template.sql 1.8 KB
- 📁 shapes/
  - 📄 core.template.yaml 1.1 KB
- 📁 warehouse/
  - 📄 claim_evidence.template.jsonl 765 B
  - 📄 claims.template.jsonl 1.0 KB
  - 📄 derived_edges.template.jsonl 328 B
  - 📄 documents.template.jsonl 303 B
  - 📄 entities.template.jsonl 240 B
  - 📄 segments.template.jsonl 989 B
📁 evals/
- 📁 files/
  - 📁 accepted_only_derivation_bundle/
    
    📁 docs/
    
    📄 INDEXER.md 144 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 1.5 KB
    
    📄 relations.yaml 3.5 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 478 B
    
    📁 rules/
    
    📄 inference.yaml 525 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 733 B
    
    📄 claims.jsonl 983 B
    
    📄 derived_edges.jsonl 754 B
    
    📄 documents.jsonl 125 B
    
    📄 entities.jsonl 319 B
    
    📄 FIXTURE.md 285 B
  - 📁 doc_supersession_bundle/
    
    📁 docs/
    
    📄 NEW_DECISION.md 110 B
    
    📄 OLD_DECISION.md 120 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 1.5 KB
    
    📄 relations.yaml 3.5 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 478 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 1.5 KB
    
    📄 claims.jsonl 2.2 KB
    
    📄 documents.jsonl 280 B
    
    📄 entities.jsonl 587 B
    
    📄 FIXTURE.md 219 B
  - 📁 education_pack_bundle/
    
    📁 docs/
    
    📄 COURSE_MODULE_NOTE.md 362 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 404 B
    
    📄 relations.yaml 2.8 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 439 B
    
    📁 rules/
    
    📄 inference.yaml 10 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 1.9 KB
    
    📄 claims.jsonl 1.7 KB
    
    📄 documents.jsonl 158 B
    
    📄 entities.jsonl 536 B
    
    📄 FIXTURE.md 194 B
  - 📁 finance_pack_bundle/
    
    📁 docs/
    
    📄 RESEARCH_MEMO.md 303 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 417 B
    
    📄 relations.yaml 2.9 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 439 B
    
    📁 rules/
    
    📄 inference.yaml 10 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 1.9 KB
    
    📄 claims.jsonl 1.7 KB
    
    📄 documents.jsonl 147 B
    
    📄 entities.jsonl 646 B
    
    📄 FIXTURE.md 175 B
  - 📁 repo_dependency_claims/
    
    📁 docs/
    
    📄 ARCHITECTURE.md 116 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 1.5 KB
    
    📄 relations.yaml 3.5 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 478 B
    
    📁 rules/
    
    📄 inference.yaml 525 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 416 B
    
    📄 claims.jsonl 598 B
    
    📄 documents.jsonl 138 B
    
    📄 entities.jsonl 239 B
    
    📄 FIXTURE.md 397 B
  - 📁 repo_document_provenance/
    
    📁 docs/
    
    📄 PROVENANCE_NOTE.md 155 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 1.5 KB
    
    📄 relations.yaml 3.5 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 478 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 755 B
    
    📄 claims.jsonl 1.2 KB
    
    📄 documents.jsonl 147 B
    
    📄 entities.jsonl 385 B
    
    📄 FIXTURE.md 180 B
  - 📁 research_contradiction_bundle/
    
    📁 docs/
    
    📄 RESEARCH_NOTE.md 198 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 1.5 KB
    
    📄 relations.yaml 1.6 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 478 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 1.4 KB
    
    📄 claims.jsonl 2.3 KB
    
    📄 documents.jsonl 141 B
    
    📄 entities.jsonl 578 B
    
    📄 FIXTURE.md 331 B
  - 📁 work_docs_pack_bundle/
    
    📁 docs/
    
    📄 TEAM_WEEKLY_REVIEW.md 318 B
    
    📁 intelligence/
    
    📁 manifests/
    
    📄 document_types.yaml 425 B
    
    📄 relations.yaml 2.8 KB
    
    📁 retrieval/
    
    📄 chroma_collection.yaml 439 B
    
    📁 rules/
    
    📄 inference.yaml 10 B
    
    📁 warehouse/
    
    📁 jsonl/
    
    📄 claim_evidence.jsonl 2.0 KB
    
    📄 claims.jsonl 1.7 KB
    
    📄 documents.jsonl 154 B
    
    📄 entities.jsonl 732 B
    
    📄 FIXTURE.md 196 B
- 📄 evals.json 10.9 KB
📁 references/
- 📄 chroma-integration.md 1.7 KB
- 📄 claim-lifecycle.md 1.2 KB
- 📄 comparison-workflow.md 1.2 KB
- 📄 graph-projection-model.md 1.5 KB
- 📄 pack-selection-guide.md 2.7 KB
- 📄 repo-adapter-boundary.md 1.3 KB
📁 scripts/
- 📄 _ontology_core_support.py 8.6 KB
- 📄 build_segments.py 11.0 KB
- 📄 compare_graph_modes.py 10.6 KB
- 📄 export_graph_projection.py 9.6 KB
- 📄 materialize_derived_edges.py 5.2 KB
- 📄 retrieve_with_chroma.py 3.2 KB
- 📄 sync_claims_to_duckdb.py 8.6 KB
- 📄 sync_segments_to_chroma.py 4.5 KB
- 📄 validate_ontology_graph.py 30.9 KB
📄 SKILL.md 8.0 KB

SKILL.md

---
name: lg-ontology
description: Extend lightweight-ontology-core into a lightweight graph workflow without replacing canonical JSONL truth. Use when documents, notes, research memos, repository guidance, finance notes, chat logs, or educational material already use lightweight ontology registries and you want graph projection, graph-style neighborhood/path inspection, Ladybug-ready exports, or baseline-vs-graph comparison tests. Trigger for requests to copy or adapt lightweight-ontology-core for graph exploration, prepare a Ladybug projection layer, inspect multi-hop neighborhoods, or compare direct JSONL reasoning against graph-assisted exploration. Do not use this to replace canonical JSONL with a graph DB or to design a full GraphRAG platform from scratch.
---

# LG Ontology

Use this skill to keep `lightweight-ontology-core` as the source of truth while adding a lightweight graph projection layer.
The goal is to improve graph-style inspection, path reasoning, and comparison testing without turning the canonical ontology into a graph-database-first system.

## Operating Model

Keep these layers separate:

- ontology definitions in YAML
- canonical extracted facts in JSONL
- canonical text-reference segments in JSONL
- derived edges in JSONL
- analytical mirror in DuckDB
- semantic retrieval in Chroma
- graph projection artifacts for graph-style querying
- optional Ladybug loading as a read-only graph layer

### Source Of Truth Hierarchy

Canonical:

- `intelligence/manifests/relations.yaml`
- `intelligence/manifests/document_types.yaml`
- `warehouse/jsonl/entities.jsonl`
- `warehouse/jsonl/documents.jsonl`
- `warehouse/jsonl/claims.jsonl`
- `warehouse/jsonl/claim_evidence.jsonl`
- `warehouse/jsonl/segments.jsonl`

Derived:

- `warehouse/jsonl/derived_edges.jsonl`
- `warehouse/ontology.duckdb`
- `warehouse/graph_projection/...`

Retrieval:

- `intelligence/retrieval/chroma_collection.yaml`
- `vector/chroma/`

Optional read-only graph serving layer:

- Ladybug or another embedded property graph loaded from projection artifacts

Do not promote graph projection outputs to canonical truth.

## What This Skill Adds Over The Core

Use this skill when the ontology core already exists and you need:

- graph-style neighborhood inspection around entities, claims, segments, and documents
- path-oriented reasoning such as `entity -> claim -> evidence -> segment -> document`
- lightweight multi-hop exploration before committing to a graph DB
- Ladybug-friendly export artifacts without changing ontology ownership
- baseline-vs-graph comparison tests to decide whether a graph layer is worth keeping

## Do Not Use This Skill For

- replacing canonical JSONL with a graph database
- auto-accepting facts because the graph looks connected
- full GraphRAG platform design from scratch
- broad ontology redesign before a domain adapter exists

## Bundled References

Read these references when needed:

- `references/claim-lifecycle.md`
- `references/chroma-integration.md`
- `references/repo-adapter-boundary.md`
- `references/graph-projection-model.md`
- `references/comparison-workflow.md`
- `references/pack-selection-guide.md`

## Starter Packs

`lg-ontology` stays generic. Starter packs are thin template helpers only.

Starter packs should live under:

- `assets/packs/<pack-name>/`

Current roadmap order:

1. `work-docs`
2. `education`
3. `finance`

Use starter packs to reduce schema-selection friction, not to turn `lg-ontology` into a domain bundle monolith.

## Bundled Scripts

Core scripts inherited from the ontology core:

- `scripts/validate_ontology_graph.py`
- `scripts/build_segments.py`
- `scripts/sync_segments_to_chroma.py`
- `scripts/retrieve_with_chroma.py`
- `scripts/materialize_derived_edges.py`
- `scripts/sync_claims_to_duckdb.py`

Graph workflow scripts added by this skill:

- `scripts/export_graph_projection.py`
- `scripts/compare_graph_modes.py`

## Workflow

### 1. Keep The Core Healthy First

Before any graph work, keep the ontology core valid.

Run:

```bash
python scripts/build_segments.py --repo-root <path>
python scripts/materialize_derived_edges.py --repo-root <path>
python scripts/sync_claims_to_duckdb.py --repo-root <path>
python scripts/validate_ontology_graph.py --repo-root <path>
```

Do not add a graph layer on top of broken canonical registries.
If the corpus is conversational or sequential, make sure a full-fidelity `messages.jsonl` or equivalent event registry exists before trusting graph-assisted report quality.

### 2. Export A Graph Projection

Generate graph-oriented node and edge artifacts from canonical JSONL plus derived edges.

Run:

```bash
python scripts/export_graph_projection.py --repo-root <path>
```

This writes graph projection artifacts under:

- `warehouse/graph_projection/nodes.jsonl`
- `warehouse/graph_projection/edges.jsonl`
- `warehouse/graph_projection/nodes/*.jsonl`
- `warehouse/graph_projection/edges/*.jsonl`
- `warehouse/graph_projection/summary.json`

Treat these files as derived outputs only.
If a downstream report or explorer consumes the projection, verify that it still reads canonical messages plus derived edges rather than silently falling back to claim samples.

### 3. Compare Baseline Reasoning Vs Graph-Style Expansion

Use the comparison script before deciding a graph layer is worth keeping.

Run:

```bash
python scripts/compare_graph_modes.py --repo-root <path> --query "<entity id or label>"
```

Use this to compare:

- direct canonical lookup around a seed entity
- graph-style neighborhood expansion
- extra reachable entities, claims, evidence rows, segments, and documents

Prefer this lightweight comparison before introducing Ladybug.

### 4. Add Ladybug Only If The Projection Proves Useful

If graph-style inspection clearly helps, load the projection artifacts into Ladybug as a read-only query layer.

The graph layer should serve:

- ad-hoc path queries
- neighborhood inspection
- lightweight multi-hop exploration
- graph-assisted context assembly

The graph layer should not own:

- fact approval
- provenance truth
- lifecycle decisions
- canonical edits

### 5. Keep Reporting Explicit

When you finish graph-layer work, report:

1. canonical ontology status
2. projection export status
3. projection counts by node and edge type
4. baseline-vs-graph comparison result
5. whether Ladybug is justified yet
6. contradictions or lifecycle concerns
7. next steps

## Projection Rules

Project these node families when useful:

- `Entity`
- `Document`
- `Segment`
- `Claim`
- `Evidence`

Project these edge families when useful:

- claim predicate edges from accepted claims
- derived relation edges
- claim-to-evidence edges
- evidence-to-segment edges
- claim-to-segment edges
- segment-to-document edges
- segment-to-entity mention edges
- conversational interaction edges such as author, mention, reply, and topic co-occurrence when the source corpus supports them

Keep `accepted` as the default fact graph.
Include non-accepted claims only when explicitly investigating review state or conflicts.

## Comparison Heuristic

Call the graph layer justified when at least one of these improves materially:

- multi-hop path inspection
- provenance chain explanation
- neighborhood expansion around seed entities
- graph-assisted context assembly
- analyst ergonomics for ad-hoc exploration

Do not call it justified just because it is visually pleasing or because the graph has many edges.
Also do not call it justified if the graph layer only looks useful because the baseline consumer regressed to claim-only or top-N summary fallback.

## Guardrails

Do not:

- treat graph projection artifacts as canonical
- bypass claim lifecycle rules because a graph query is convenient
- hide unresolved contradictions behind graph traversals
- replace the ontology core before comparison testing proves value
- add domain-specific relation sprawl to the base skill before an adapter exists
- let materializers collapse richer interaction edge families back into a narrower provenance-only graph without an explicit contract change

Use this skill as a graph-oriented extension of `lightweight-ontology-core`.
Keep canonical truth ownership in the ontology core.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

lg-ontology

Directory Structure

SKILL.md

Report

Notice