Track: Oxigraph as shared RDF/knowledge graph layer for Harrier, Robin, cf-orch #53

New issue

Open

opened 2026-07-05 08:50:54 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-05 08:50:54 -07:00

Owner

Source

https://github.com/oxigraph/oxigraph — Apache 2.0 / MIT dual license

Context

Oxigraph is an embedded Rust-core RDF graph database with SPARQL 1.1 query support
and a clean Python API via pyoxigraph. Immediate use in Kiwi (food ontology —
see kiwi#154). This ticket tracks three longer-horizon CF use cases where a
shared graph layer would be valuable.

Harrier (government forms — backlog ★ND)

Government benefit eligibility is a natural graph problem:

Benefits.gov, SSA, SNAP, VA programs have linked data / RDF representations
User profile (age, income, disability status, state) as RDF triples
Eligibility rules as SPARQL queries: "which programs does this user qualify for?"
Reasoning over rule graphs is more maintainable than nested if/else eligibility trees

Robin (Linux migration companion — concept)

System knowledge as a graph:

Windows app → Linux equivalent mapping ("Photoshop" → GIMP/Krita/Darktable)
Package relationships: app depends on runtime X which conflicts with Y
User's installed software, config preferences, file associations as triples
Proactive suggestions: "you just installed app X — you might also need Y"
Oxigraph in-memory, loaded from a curated Robin knowledge base TTL file.

cf-orch (agent capability registry)

Model agents as RDF resources with capability and resource triples:

SELECT ?agent WHERE {
  ?agent :supports :audio_task ;
         :has_resource :gpu ;
         :status :available .
}

SPARQL-powered task routing replaces bespoke matching logic. Debatable whether
this is over-engineering vs a clean abstraction — evaluate after Kiwi proves
the pattern.

Shared module

If all three adopt Oxigraph, a circuitforge_core.graph module makes sense:

Shared ontology loading utilities
SPARQL query helpers
Standard namespaces (food:, benefit:, app:, agent:)

Priority

Now: Kiwi (see kiwi#154)
Next: Harrier when it enters active development
Later: Robin, cf-orch — revisit at that stage

License

Apache 2.0 / MIT — clean for all CF tiers.

## Source https://github.com/oxigraph/oxigraph — Apache 2.0 / MIT dual license ## Context Oxigraph is an embedded Rust-core RDF graph database with SPARQL 1.1 query support and a clean Python API via `pyoxigraph`. Immediate use in Kiwi (food ontology — see kiwi#154). This ticket tracks three longer-horizon CF use cases where a shared graph layer would be valuable. ## Harrier (government forms — backlog ★ND) Government benefit eligibility is a natural graph problem: - Benefits.gov, SSA, SNAP, VA programs have linked data / RDF representations - User profile (age, income, disability status, state) as RDF triples - Eligibility rules as SPARQL queries: "which programs does this user qualify for?" - Reasoning over rule graphs is more maintainable than nested if/else eligibility trees ## Robin (Linux migration companion — concept) System knowledge as a graph: - Windows app → Linux equivalent mapping ("Photoshop" → GIMP/Krita/Darktable) - Package relationships: app depends on runtime X which conflicts with Y - User's installed software, config preferences, file associations as triples - Proactive suggestions: "you just installed app X — you might also need Y" Oxigraph in-memory, loaded from a curated Robin knowledge base TTL file. ## cf-orch (agent capability registry) Model agents as RDF resources with capability and resource triples: ```sparql SELECT ?agent WHERE { ?agent :supports :audio_task ; :has_resource :gpu ; :status :available . } ``` SPARQL-powered task routing replaces bespoke matching logic. Debatable whether this is over-engineering vs a clean abstraction — evaluate after Kiwi proves the pattern. ## Shared module If all three adopt Oxigraph, a `circuitforge_core.graph` module makes sense: - Shared ontology loading utilities - SPARQL query helpers - Standard namespaces (food:, benefit:, app:, agent:) ## Priority - **Now:** Kiwi (see kiwi#154) - **Next:** Harrier when it enters active development - **Later:** Robin, cf-orch — revisit at that stage ## License Apache 2.0 / MIT — clean for all CF tiers.