OKF graph, distillation & code links

Start with a small OKF node#

An OKF document uses YAML frontmatter and a Markdown body. Give it a stable ID, a title, and an authority level. Use experimental for an unreviewed draft; canonical is an authority label, not a correctness check.

---
id: example-policy
title: Example output policy
domain: engineering
authority: experimental
version: "1.0"
tags: [outputs, review]
links:
  - target: core/types.ts
    relation: defined_in
---

# Example output policy

- Generated deliverables should have descriptive filenames.
- Verify an output before marking the task complete.

Import the Markdown node through the Knowledge Base’s OKF controls. Replace the example code path with a real path in the workspace you intend to check.

Turn a document into a draft node#

1. In Knowledge Base, choose Auto-Distill.
2. Use Ingest File or Paste Raw Text, then supply the document or excerpt.
3. Optionally set the title and domain, then choose Start Distillation.
4. Inspect the saved node’s extracted rules, tags, links, and authority before relying on it.

Explore the Force Graph#

1. Switch the OKF view from Table to Force Graph.
2. Use the graph’s zoom and pan interactions to explore clusters.
3. Select a node to inspect its content and relationships.
4. Use the OKF search field to find nodes by title, tags, or domain.

Graph edges come from recorded relationships and wiki-style links. A displayed connection means the relationship was recorded; review the underlying node for its meaning.

Understand code-link verification#

The verifier resolves code-reference targets against a workspace root and reports existing and missing paths. Recognized relationships include implemented_by, tested_by, validates, defined_in, and code_reference.