		# Repository Navigation Protocol (Open Knowledge Format)

		This repository utilizes the Open Knowledge Format (OKF) to optimize context retrieval, minimize token usage, and prevent duplicate files. You must interact with the codebase using the following rules:

		### 1. Progressive Navigation Rule
		Do not use raw terminal grep commands or blind full-text pattern matching as a first resort. Instead:
		- Start your search at the root `index.md`.
		- Read the one-sentence descriptions of the subdirectories.
		- Move down the directory tree level-by-level, reading the local `index.md` at each stage.
		- Only open the final target concept file once you have identified it via the index summaries.

		### 2. Metadata Filtering
		Before parsing the entire body of a document, look at its YAML frontmatter block. Use the `type` and `tags` fields to quickly determine if the document matches the user's intent without wasting tokens on the full text.

		### 3. Upkeep and Maintenance
		When creating or modifying files, you must maintain the OKF structure:
		- **Single Concept:** Ensure every file represents exactly one minimal topic (do not mix unrelated topics).
		- **Frontmatter:** Every new file must include a YAML frontmatter block containing at minimum a `type` field (along with optional `title`, `description`, and `tags`).
		- **Index Update:** Immediately update the parent directory's `index.md` file to include a markdown link to the new file alongside a clear, one-sentence summary.

