Knowledge Graph

AI OS has two related but distinct graph experiences. The Knowledge Graph route shows Graphify project-code maps; the Memory route’s Knowledge Explorer shows bounded note relationships. They do not share one graph payload.

Project Knowledge Graph

• Source provenance and safe labels.
• Project nodes, edges, communities, and important files.
• Extracted coverage versus inferred relationships.
• Search, filtering, selected-item details, and 2D or 3D exploration.
• A grounded Hermes panel seeded with bounded context from the active project.

The browser receives a bounded projection. Parsing, normalization, caps, and fallback selection happen in shared helpers before data reaches the visual components.

Fresh clones can render the reviewed AI OS seed graph without installing Graphify. To prepare the optional local Graphify dependency and supported agent skills, run:

bash scripts/setup-graphify-brain.sh

Graphify writes

Graphify is a local write path. It uses the current run’s local controls, validates input, confines paths, and returns structured results or a clear recovery state. The static demo can illustrate graph output but cannot run a Graphify write.

An operator can ingest a confined local directory or reviewed Git source when Graphify and local write readiness pass. Removing a graph deletes its graph artifacts and registry entry; it does not delete the source directory or repository.

Generated graph files are ignored by default. The committed seed registry and AI OS self-graph are deliberate reviewed exceptions. Maintainers can verify that ownership with:

bun run graph:policy:check

Memory Knowledge Explorer

Memory can discover supported local note vaults, project bounded note and topic relationships, search across safe fields, and move through related notes in the same vault. Private filesystem identities stay outside the visible graph.

For skill, saved-time, Memory, and Activity semantics, see Skills, Memory, and Activity.