---

name: semantic-anchoring description: Validate and enrich semantic references (ConceptIds) against the Knowledge Graph. Use when linking artifacts, specs, or code to ontology concepts, validating SHACL constraints, or discovering related concepts from DomainForge™. license: Complete terms in LICENSE.txt

Semantic Anchoring

Validate, enrich, and link content to the SEA-Forge™ Knowledge Graph using semantic references (ConceptIds).

For reference: DomainForge Handbook | SDS-009: Knowledge Graph Service

---

When to Use This Skill

Use semantic-anchoring when:

1. Linking to Concepts: Adding semanticRefs to CADSL artifacts, specs, or code
2. Validating References: Checking if ConceptIds exist in the Knowledge Graph
3. Discovering Concepts: Finding related concepts for suggestions
4. Enforcing Constraints: Validating SHACL shapes on artifact structures
5. Building Traceability: Connecting specs → code → artifacts semantically

---

ConceptId Format

ConceptIds follow this format:

Copy<namespace>:<ConceptName>

Examples:

• sea:BoundedContext - SEA-Forge core ontology
• sea:CognitiveArtifact - Cognitive Extension
• cmmn:Case - CMMN primitives
• domain:Customer - Domain-specific concepts

Reserved Namespaces:

---

Validation Workflow

Step 1: Extract ConceptIds

From CADSL artifact:

CopysemanticRefs:
  - conceptId: "sea:BoundedContext"
  - conceptId: "domain:Customer"

From code annotation:

Copy# @sea:Entity
class Customer:
    pass

Step 2: Query Knowledge Graph

Use SPARQL to validate:

CopyASK {
  <http://sea-forge.org/ontology#BoundedContext> a owl:Class .
}

Or use the Knowledge Graph Service API:

Copycurl -X GET "http://localhost:7200/repositories/sea/concepts/sea:BoundedContext"

Step 3: Report Results

Valid ConceptId:

Copy✅ sea:BoundedContext - Found in SEA Core Ontology
   URI: http://sea-forge.org/ontology#BoundedContext
   Type: owl:Class
   Related: [sea:Domain, sea:Entity, sea:Flow]

Invalid ConceptId:

Copy❌ sea:UnknownConcept - Not found in Knowledge Graph
   Suggestions:
   - sea:Concept (similarity: 0.85)
   - sea:Entity (similarity: 0.72)

---

SHACL Constraint Validation

Validate artifact structures against SHACL shapes:

Copysea:ChecklistShape a sh:NodeShape ;
  sh:targetClass sea:Checklist ;
  sh:property [
    sh:path sea:title ;
    sh:minCount 1 ;
    sh:datatype xsd:string ;
  ] ;
  sh:property [
    sh:path sea:semanticRefs ;
    sh:minCount 1 ;
    sh:message "Artifacts must have at least one semantic reference" ;
  ] .

Validation Command:

Copyjust validate-shacl artifact.yaml

---

Enrichment Suggestions

When creating new content, suggest semantic anchors:

Input

Copy# API Design Document

We're building a customer management API that handles orders and payments.

Output

CopysuggestedAnchors:
  - text: "customer management"
    concepts:
      - conceptId: "domain:Customer"
        confidence: 0.95
      - conceptId: "sea:BoundedContext"
        confidence: 0.75
        
  - text: "orders"
    concepts:
      - conceptId: "domain:Order"
        confidence: 0.92
      - conceptId: "sea:Aggregate"
        confidence: 0.70
        
  - text: "payments"
    concepts:
      - conceptId: "domain:Payment"
        confidence: 0.88

---

Integration Points

Cognitive Artifacts Builder

When generating CADSL artifacts, validate all semanticRefs:

Copy# Before generation
validation:
  - conceptId: "sea:Deployment"
    status: "valid"
  - conceptId: "sea:QualityGate"
    status: "valid"

Spec Pipeline

Validate ADR/PRD/SDS references to ontology:

Copy# In SDS header
semanticRefs:
  - conceptId: "sea:Service"
    validated: true
  - conceptId: "sea:API"
    validated: true

Case Management

Link cases to domain concepts:

Copycase:
  conceptId: "cmmn:Case"
  domainRef: "domain:ProjectDelivery"

---

Quality Guidelines

1. Prefer Specific Concepts

❌ Too Generic:

CopysemanticRefs:
  - conceptId: "sea:Thing"

✅ Specific:

CopysemanticRefs:
  - conceptId: "sea:BoundedContext"
  - conceptId: "domain:CustomerOnboarding"

2. Include Domain Context

Always include at least one domain-specific concept along with core ontology concepts:

CopysemanticRefs:
  - conceptId: "sea:Flow"        # Core ontology
  - conceptId: "domain:Checkout" # Domain specific

3. Validate Before Publishing

Never publish artifacts with unvalidated ConceptIds. Use:

Copyjust semantic-validate <artifact.yaml>

---

References

• DomainForge Handbook
• SDS-009: Knowledge Graph Service
• SEA Core Ontology
• Cognitive Architecture Handbook