Ontology Building
Build a structured ontology for a research domain. Extracts concepts from sources, types their relationships, constructs taxonomies, validates consistency, and iteratively refines until the ontology is coherent and complete.
Manifest
| Level |
Count |
Skills |
| Strategy |
5 |
domain-scoping, concept-extraction, relation-typing, taxonomy-validation, ontology-refinement |
| Tactic |
3 |
concept-decomposition, hierarchy-construction, consistency-checking |
| SOP |
10 |
seed-concept-search, source-gathering, concept-page-creation, alias-resolution, edge-batch-creation, hierarchy-visualization, gap-detection, merge-candidates, confidence-update, ontology-export |
Budget Table
| Metric |
Small |
Medium |
Large |
| Source pages ingested |
10 |
25 |
50 |
| Concept pages created |
15 |
40 |
80 |
| Edges created |
30 |
100 |
200 |
| Taxonomy depth (levels) |
2 |
3 |
4 |
| Validation passes |
1 |
2 |
3 |
Strategy Sequence (Reference, Not Prescription)
- domain-scoping — define boundaries, identify seed concepts, classify topic size
- concept-extraction — mine sources for concepts, create pages, resolve aliases
- relation-typing — identify and type relationships between concepts
- taxonomy-validation — check hierarchy consistency, detect gaps and conflicts
- ontology-refinement — merge near-duplicates, fill gaps, update confidence scores
CC may reorder, skip, or repeat strategies based on the domain's needs.
MCP Tools Used
vault_search — find existing concepts, detect duplicatesvault_add_edge — create typed relationshipsvault_query_graph — explore concept neighborhoodsvault_graph_stats — assess ontology coverage and connectivityvault_lint — validate structural integrityvault_index — maintain search index
Context-Management
Guiding Principles
- Breadth before depth. Map the concept landscape broadly before drilling into any sub-area.
- Edges over pages. A concept without relationships is useless. Prioritize connecting over creating.
- Aliases are enemies. The same concept with different names fragments the ontology. Resolve aggressively.
- Confidence is honest. Mark uncertain classifications explicitly. Low confidence is better than false certainty.
- The ontology is never finished. Each research session may reveal new concepts or invalidate old ones.
Available Strategies
Optional, no fixed order; the final leaf is always a sop.
| Strategy |
When to use |
| concept-extraction |
Strategy for mining concepts from sources — systematic extraction, page creation, alias resolution. |
| domain-scoping |
Strategy for defining ontology boundaries — identify seed concepts, classify topic size, establish scope constraints. |
| ontology-refinement |
Strategy for iterative ontology improvement — merge duplicates, fill gaps, update confidence, prune dead branches. |
| relation-typing |
Strategy for identifying and typing relationships between concepts — create edges with appropriate types and weights. |
| taxonomy-validation |
Strategy for validating ontology consistency — check hierarchy, detect cycles, verify completeness. |
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic |
When to use |
| concept-decomposition |
Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages. |
| hierarchy-construction |
Tactic for building is-a and part-of hierarchies — establish parent-child relationships, verify transitivity, detect cycles. |
| knowledge-compilation |
Tactic for compiling research findings into vault pages — orchestrates page creation, updates, edge linking, and index maintenance. Minimum yield ≥3 page operations per invocation. |
| knowledge-structuring-consistency-checking |
Tactic for verifying ontology consistency — detect contradictions, cycles, orphans, and type violations. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP |
When to use |
| context-checkpoint |
Append research process and results to the current Phase's context file. Covers both process and results with genuine substance. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. |
| context-init |
Create a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed. |
1---2name: ontology-building3description: Campaign for building domain ontologies — systematic concept extraction, relation typing, taxonomy construction, and iterative refinement. Produces a structured concept hierarchy in the wiki vault.4---56# Ontology Building78Build a structured ontology for a research domain. Extracts concepts from sources, types their relationships, constructs taxonomies, validates consistency, and iteratively refines until the ontology is coherent and complete.910## Manifest1112| Level | Count | Skills |13|-------|-------|--------|14| Strategy | 5 | domain-scoping, concept-extraction, relation-typing, taxonomy-validation, ontology-refinement |15| Tactic | 3 | concept-decomposition, hierarchy-construction, consistency-checking |16| SOP | 10 | seed-concept-search, source-gathering, concept-page-creation, alias-resolution, edge-batch-creation, hierarchy-visualization, gap-detection, merge-candidates, confidence-update, ontology-export |1718## Budget Table1920| Metric | Small | Medium | Large |21|--------|-------|--------|-------|22| Source pages ingested | 10 | 25 | 50 |23| Concept pages created | 15 | 40 | 80 |24| Edges created | 30 | 100 | 200 |25| Taxonomy depth (levels) | 2 | 3 | 4 |26| Validation passes | 1 | 2 | 3 |2728## Strategy Sequence (Reference, Not Prescription)29301. **domain-scoping** — define boundaries, identify seed concepts, classify topic size312. **concept-extraction** — mine sources for concepts, create pages, resolve aliases323. **relation-typing** — identify and type relationships between concepts334. **taxonomy-validation** — check hierarchy consistency, detect gaps and conflicts345. **ontology-refinement** — merge near-duplicates, fill gaps, update confidence scores3536CC may reorder, skip, or repeat strategies based on the domain's needs.3738## MCP Tools Used3940- `vault_search` — find existing concepts, detect duplicates41- `vault_add_edge` — create typed relationships42- `vault_query_graph` — explore concept neighborhoods43- `vault_graph_stats` — assess ontology coverage and connectivity44- `vault_lint` — validate structural integrity45- `vault_index` — maintain search index4647## Context-Management4849<HARD-GATE>50- Call `context-init` at campaign start51- Call `context-checkpoint` after each strategy completes52- Call `knowledge-compilation` (wiki-vault tactic) after each strategy53</HARD-GATE>5455## Guiding Principles5657- **Breadth before depth.** Map the concept landscape broadly before drilling into any sub-area.58- **Edges over pages.** A concept without relationships is useless. Prioritize connecting over creating.59- **Aliases are enemies.** The same concept with different names fragments the ontology. Resolve aggressively.60- **Confidence is honest.** Mark uncertain classifications explicitly. Low confidence is better than false certainty.61- **The ontology is never finished.** Each research session may reveal new concepts or invalidate old ones.6263<!-- BEGIN available-tables (generated) -->6465## Available Strategies6667Optional, no fixed order; the final leaf is always a sop.6869| Strategy | When to use |70| --- | --- |71| concept-extraction | Strategy for mining concepts from sources — systematic extraction, page creation, alias resolution. |72| domain-scoping | Strategy for defining ontology boundaries — identify seed concepts, classify topic size, establish scope constraints. |73| ontology-refinement | Strategy for iterative ontology improvement — merge duplicates, fill gaps, update confidence, prune dead branches. |74| relation-typing | Strategy for identifying and typing relationships between concepts — create edges with appropriate types and weights. |75| taxonomy-validation | Strategy for validating ontology consistency — check hierarchy, detect cycles, verify completeness. |7677## Available Tactics7879Optional, no fixed order; the final leaf is always a sop.8081| Tactic | When to use |82| --- | --- |83| concept-decomposition | Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages. |84| hierarchy-construction | Tactic for building is-a and part-of hierarchies — establish parent-child relationships, verify transitivity, detect cycles. |85| knowledge-compilation | Tactic for compiling research findings into vault pages — orchestrates page creation, updates, edge linking, and index maintenance. Minimum yield ≥3 page operations per invocation. |86| knowledge-structuring-consistency-checking | Tactic for verifying ontology consistency — detect contradictions, cycles, orphans, and type violations. |8788## Available SOPs8990Optional, no fixed order; the final leaf is always a sop.9192| SOP | When to use |93| --- | --- |94| context-checkpoint | Append research process and results to the current Phase's context file. Covers both process and results with genuine substance. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. |95| context-init | Create a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed. |9697<!-- END available-tables (generated) -->
yogsoth-ai