blue_rose_graph

blue_rose_graph is an Obsidian-native ontology and knowledge-graph vault generated from glossary.md. It is meant to work simultaneously as:

• a readable glossary
• a typed graph
• a proto-ontology
• an agent-usable markdown knowledge base

The current generated vault contains 212 term notes, 13 category hubs, JSON graph exports, and an Obsidian layer for graph view settings, badges, and color-coded tags.

What This Repository Contains

This repository turns a grouped ontology glossary into a normalized note system with:

• one note per term in terms/
• one hub note per category in categories/
• one vault entry point in index.md
• machine-readable graph exports in exports/
• a generator in build_obsidian_vault.py

Each term note carries:

• stable identity fields such as id, uri, and label
• technical, plain-language, and machine-oriented definitions
• explicit hierarchy and associative links
• source grounding
• learning-path hints
• Obsidian-friendly markdown sections for direct reading

Live Obsidian Screenshots

These screenshots were captured from the running Obsidian app against this vault.

Vault landing view

Term note view

Graph views

Repository Layout

blue_rose_graph/
|- index.md
|- glossary.md
|- AGENT.md
|- README.md
|- build_obsidian_vault.py
|- categories/
|- terms/
|- exports/
|  |- graph-adjacency.json
|  `- graph-metrics.json
|- docs/
|  `- screenshots/
`- .obsidian/
   |- core-plugins.json
   |- graph.json
   `- snippets/knowledge-graph-badges.css

Core Data Model

The vault is generated around a consistent frontmatter schema. Every term note contains:

• identity: id, uri, label, aliases
• typing: kind, subtype, category
• classification: tags, domain, layer, function
• semantic core: definition_kernel, definitions
• provenance: sources
• graph structure: relationships, edges, graph
• learning support: learning
• export hints: rdf

The markdown body repeats the important parts for direct reading:

• summary
• labels
• tags
• technical definition
• layperson definition
• machine view
• graph context
• hierarchy
• synonyms
• dependencies
• learning path
• notes
• sources

Graph Topology

Current generated stats:

• 212 term notes
• 13 category hubs
• 1 connected component
• maximum node degree: 23
• average node degree: 4.67

Primary relation types currently used in the generated vault:

• child_of
• parent_of
• related_to
• contrasts_with

The graph is strongest today in:

• identity normalization
• hierarchy
• category clustering
• cross-linked note navigation

The graph is weaker today in:

• dependency typing
• synonym and equivalence typing
• dense relation semantics for low-degree nodes
• term-specific citation granularity

Representative Entry Points

Useful starting notes if you are navigating manually:

• Ontology
• Knowledge graph
• RDF graph
• OWL
• SKOS
• SPARQL
• SHACL
• Ontology artifact
• Property
• Defines class

Useful category hubs:

• Foundation
• Core RDF and Linked Data Terms
• OWL and Description Logic Terms
• Query, Validation, and Constraint Layers
• Alignment, Integration, and Modularity
• Backbone and Relation Vocabulary

Exports

The repository includes machine-readable graph exports:

• exports/graph-adjacency.json: adjacency-style graph structure
• exports/graph-metrics.json: simple node-level graph metrics

These are useful for:

• quick graph inspection
• ingestion into other tools
• programmatic QA
• future RDF, OWL, or static-site pipelines

Generation Workflow

The vault is regenerated from glossary.md using:

python build_obsidian_vault.py

The generator currently handles:

• parsing glossary-style source entries
• promoting backbone terms into first-class nodes
• canonical ID creation
• note generation
• category hub generation
• JSON export generation
• Obsidian styling support file generation

Obsidian Layer

The vault is designed to open directly in Obsidian.

Relevant files:

• index.md
• .obsidian/graph.json
• .obsidian/core-plugins.json
• .obsidian/snippets/knowledge-graph-badges.css

What the Obsidian layer adds:

• visible badge rows in notes and category hubs
• color-coded tags
• graph view defaults
• a cleaner landing experience for the vault
• a readable plain-language definition layer in every term note

Environment

The real .env file is intentionally ignored by git.

Use .env.example as the public-safe template:

Copy-Item .env.example .env

Then fill in local values as needed.

Do not commit live credentials.

Publishing

This repo is prepared for GitHub publication as blue_rose_graph.

Typical push flow after the remote exists:

git remote add origin https://github.com/<your-user>/blue_rose_graph.git
git push -u origin main

If you want a browsable public site rather than only a code repository, the next layer should be a static publishing pipeline such as Quartz, MkDocs, or a custom markdown-to-HTML build.

Agent And Automation Support

If another agent or script needs to work against this repo, start with:

• AGENT.md
• build_obsidian_vault.py
• exports/graph-adjacency.json
• exports/graph-metrics.json

AGENT.md documents how to navigate, edit, regenerate, validate, and document the vault safely.

Current Status

This repository is already strong as:

• a readable ontology vault
• a typed markdown graph
• a repo-hosted graph corpus
• a base layer for future export and enrichment

The main next improvements are:

• richer dependency edges
• fuller synonym and equivalence modeling
• denser source-specific grounding
• optional static web publishing